SAP HR_IDALV_CREATE_NODE_CATEG Function Module for Node category creation
HR_IDALV_CREATE_NODE_CATEG is a standard hr idalv create node categ SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Node category creation processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for hr idalv create node categ FM, simply by entering the name HR_IDALV_CREATE_NODE_CATEG into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPADRU_IDALV
Program Name: SAPLHRPADRU_IDALV
Main Program: SAPLHRPADRU_IDALV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_IDALV_CREATE_NODE_CATEG pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'HR_IDALV_CREATE_NODE_CATEG'"Node category creation.
EXPORTING
I_CATEG_ID = "Structured Application Log: Category ID
* I_DEFAULT = "
* IS_LAYOUT = "
* I_S_PRINT_OPTIONS = "
* I_TREE_SORT = "Application Log: Sort Messages and Chapters
* I_CLBK = "Application Log: Return routine definition
* I_ROWMARK = "Boolean Variable (X=True, -=False, Space=Unknown)
* IS_PUSHBUTTONS = "Structured Application Log: Pushbuttons for Node Category
* I_STRUCTURE_NAME = "Table Name
* I_WITH_MSG_FIELDS = "Boolean Variable (X=True, -=False, Space=Unknown)
* I_MSG_TEXT_POS = "
* I_ICON_LTEXT_POS = "
* IT_FIELDCAT = "
* IT_SORT = "
* I_SAVE = "
* IS_VARIANT = "Layout (External Use)
EXCEPTIONS
PROGRAM_ERROR = 1
IMPORTING Parameters details for HR_IDALV_CREATE_NODE_CATEG
I_CATEG_ID - Structured Application Log: Category ID
Data type: P33_BALS_CATEG_IDOptional: No
Call by Reference: Yes
I_DEFAULT -
Data type: COptional: Yes
Call by Reference: Yes
IS_LAYOUT -
Data type: SLIS_LAYOUT_ALVOptional: Yes
Call by Reference: Yes
I_S_PRINT_OPTIONS -
Data type: SLIS_PRINT_ALVOptional: Yes
Call by Reference: Yes
I_TREE_SORT - Application Log: Sort Messages and Chapters
Data type: BAL_T_SORTOptional: Yes
Call by Reference: Yes
I_CLBK - Application Log: Return routine definition
Data type: BAL_S_CLBKOptional: Yes
Call by Reference: Yes
I_ROWMARK - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
IS_PUSHBUTTONS - Structured Application Log: Pushbuttons for Node Category
Data type: T7RU_BALS_S_PUSHBUTTONSOptional: Yes
Call by Reference: Yes
I_STRUCTURE_NAME - Table Name
Data type: TABNAMEOptional: Yes
Call by Reference: Yes
I_WITH_MSG_FIELDS - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
I_MSG_TEXT_POS -
Data type: IOptional: Yes
Call by Reference: Yes
I_ICON_LTEXT_POS -
Data type: IOptional: Yes
Call by Reference: Yes
IT_FIELDCAT -
Data type: SLIS_T_FIELDCAT_ALVOptional: Yes
Call by Reference: Yes
IT_SORT -
Data type: SLIS_T_SORTINFO_ALVOptional: Yes
Call by Reference: Yes
I_SAVE -
Data type: COptional: Yes
Call by Reference: Yes
IS_VARIANT - Layout (External Use)
Data type: DISVARIANTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
PROGRAM_ERROR - Program Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_IDALV_CREATE_NODE_CATEG Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_categ_id | TYPE P33_BALS_CATEG_ID, " | |||
| lv_program_error | TYPE P33_BALS_CATEG_ID, " | |||
| lv_i_default | TYPE C, " | |||
| lv_is_layout | TYPE SLIS_LAYOUT_ALV, " | |||
| lv_i_s_print_options | TYPE SLIS_PRINT_ALV, " | |||
| lv_i_tree_sort | TYPE BAL_T_SORT, " | |||
| lv_i_clbk | TYPE BAL_S_CLBK, " | |||
| lv_i_rowmark | TYPE BOOLEAN, " | |||
| lv_is_pushbuttons | TYPE T7RU_BALS_S_PUSHBUTTONS, " | |||
| lv_i_structure_name | TYPE TABNAME, " | |||
| lv_i_with_msg_fields | TYPE BOOLEAN, " | |||
| lv_i_msg_text_pos | TYPE I, " | |||
| lv_i_icon_ltext_pos | TYPE I, " | |||
| lv_it_fieldcat | TYPE SLIS_T_FIELDCAT_ALV, " | |||
| lv_it_sort | TYPE SLIS_T_SORTINFO_ALV, " | |||
| lv_i_save | TYPE C, " | |||
| lv_is_variant | TYPE DISVARIANT. " |
|   CALL FUNCTION 'HR_IDALV_CREATE_NODE_CATEG' "Node category creation |
| EXPORTING | ||
| I_CATEG_ID | = lv_i_categ_id | |
| I_DEFAULT | = lv_i_default | |
| IS_LAYOUT | = lv_is_layout | |
| I_S_PRINT_OPTIONS | = lv_i_s_print_options | |
| I_TREE_SORT | = lv_i_tree_sort | |
| I_CLBK | = lv_i_clbk | |
| I_ROWMARK | = lv_i_rowmark | |
| IS_PUSHBUTTONS | = lv_is_pushbuttons | |
| I_STRUCTURE_NAME | = lv_i_structure_name | |
| I_WITH_MSG_FIELDS | = lv_i_with_msg_fields | |
| I_MSG_TEXT_POS | = lv_i_msg_text_pos | |
| I_ICON_LTEXT_POS | = lv_i_icon_ltext_pos | |
| IT_FIELDCAT | = lv_it_fieldcat | |
| IT_SORT | = lv_it_sort | |
| I_SAVE | = lv_i_save | |
| IS_VARIANT | = lv_is_variant | |
| EXCEPTIONS | ||
| PROGRAM_ERROR = 1 | ||
| . " HR_IDALV_CREATE_NODE_CATEG | ||
ABAP code using 7.40 inline data declarations to call FM HR_IDALV_CREATE_NODE_CATEG
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects