SAP KKR_OBJECT_LIST_GET Function Module for
KKR_OBJECT_LIST_GET is a standard kkr object list get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 kkr object list get FM, simply by entering the name KKR_OBJECT_LIST_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: KKRB
Program Name: SAPLKKRB
Main Program: SAPLKKRB
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function KKR_OBJECT_LIST_GET 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 'KKR_OBJECT_LIST_GET'".
EXPORTING
HIART = "Hierarchy type
HIEID = "Hierarchy identification
NODE = "Hierarchy node
ROOT = "Start node of hierarchy to be edited
* QINFO = ' ' "In: Only display information on node
IMPORTING
NODE_INFO = "Information on node
TABLES
* OBJECT_TBL = "Object list (summary nodes and single objects)
EXCEPTIONS
NODE_NOT_EXIST = 1 ROOT_NOT_EXIST = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLKKRB_001 User Exit After Selection for Summarization (Objects and Hierarchy Codes)
IMPORTING Parameters details for KKR_OBJECT_LIST_GET
HIART - Hierarchy type
Data type: CKRCO-HIARTOptional: No
Call by Reference: No ( called with pass by value option)
HIEID - Hierarchy identification
Data type: CKRCO-HIEIDOptional: No
Call by Reference: No ( called with pass by value option)
NODE - Hierarchy node
Data type: CKRCO-VARHIEBGOptional: No
Call by Reference: No ( called with pass by value option)
ROOT - Start node of hierarchy to be edited
Data type: CKRCO-VARHIEBGOptional: No
Call by Reference: No ( called with pass by value option)
QINFO - In: Only display information on node
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for KKR_OBJECT_LIST_GET
NODE_INFO - Information on node
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for KKR_OBJECT_LIST_GET
OBJECT_TBL - Object list (summary nodes and single objects)
Data type: KKROBJLISTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NODE_NOT_EXIST - Hierarchy node does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ROOT_NOT_EXIST - Start node does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KKR_OBJECT_LIST_GET 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_hiart | TYPE CKRCO-HIART, " | |||
lv_node_info | TYPE CKRCO, " | |||
lt_object_tbl | TYPE STANDARD TABLE OF KKROBJLIST, " | |||
lv_node_not_exist | TYPE KKROBJLIST, " | |||
lv_hieid | TYPE CKRCO-HIEID, " | |||
lv_root_not_exist | TYPE CKRCO, " | |||
lv_node | TYPE CKRCO-VARHIEBG, " | |||
lv_root | TYPE CKRCO-VARHIEBG, " | |||
lv_qinfo | TYPE CKRCO. " SPACE |
  CALL FUNCTION 'KKR_OBJECT_LIST_GET' " |
EXPORTING | ||
HIART | = lv_hiart | |
HIEID | = lv_hieid | |
NODE | = lv_node | |
ROOT | = lv_root | |
QINFO | = lv_qinfo | |
IMPORTING | ||
NODE_INFO | = lv_node_info | |
TABLES | ||
OBJECT_TBL | = lt_object_tbl | |
EXCEPTIONS | ||
NODE_NOT_EXIST = 1 | ||
ROOT_NOT_EXIST = 2 | ||
. " KKR_OBJECT_LIST_GET |
ABAP code using 7.40 inline data declarations to call FM KKR_OBJECT_LIST_GET
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."SELECT single HIART FROM CKRCO INTO @DATA(ld_hiart). | ||||
"SELECT single HIEID FROM CKRCO INTO @DATA(ld_hieid). | ||||
"SELECT single VARHIEBG FROM CKRCO INTO @DATA(ld_node). | ||||
"SELECT single VARHIEBG FROM CKRCO INTO @DATA(ld_root). | ||||
DATA(ld_qinfo) | = ' '. | |||
Search for further information about these or an SAP related objects