SAP KKR_HNODE_GET_H Function Module for









KKR_HNODE_GET_H is a standard kkr hnode get h 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 hnode get h FM, simply by entering the name KKR_HNODE_GET_H into the relevant SAP transaction such as SE37 or SE38.

Function Group: KKRSOO
Program Name: SAPLKKRSOO
Main Program: SAPLKKRSOO
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function KKR_HNODE_GET_H 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_HNODE_GET_H'"
EXPORTING
I_HIART = "
I_HIEID = "
I_KOKRS = "

IMPORTING
P_FIELD_INFO_TBL = "

EXCEPTIONS
HIER_TERM_IS_INITIAL = 1 HIER_TERM_TOO_LONG = 2 INVALID_HIEBG = 3 SUBTERM_IS_INITIAL = 4 HIERARCHY_NOT_DEFINED = 5 HIERARCHY_IS_EMPTY = 6 LENGTH_OF_HIERARCHY_TOO_LONG = 7 TOO_MANY_HIERARCHY_FIELDS = 8 OTHER_ERRORS = 9
.



IMPORTING Parameters details for KKR_HNODE_GET_H

I_HIART -

Data type: CKRCO-HIART
Optional: No
Call by Reference: No ( called with pass by value option)

I_HIEID -

Data type: CKRCO-HIEID
Optional: No
Call by Reference: No ( called with pass by value option)

I_KOKRS -

Data type: TKA01-KOKRS
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for KKR_HNODE_GET_H

P_FIELD_INFO_TBL -

Data type: KKRJ_T_FIELD_INFO
Optional: No
Call by Reference: Yes

EXCEPTIONS details

HIER_TERM_IS_INITIAL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

HIER_TERM_TOO_LONG -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_HIEBG -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

SUBTERM_IS_INITIAL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

HIERARCHY_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

HIERARCHY_IS_EMPTY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

LENGTH_OF_HIERARCHY_TOO_LONG -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOO_MANY_HIERARCHY_FIELDS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OTHER_ERRORS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for KKR_HNODE_GET_H 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_hiart  TYPE CKRCO-HIART, "   
lv_p_field_info_tbl  TYPE KKRJ_T_FIELD_INFO, "   
lv_hier_term_is_initial  TYPE KKRJ_T_FIELD_INFO, "   
lv_i_hieid  TYPE CKRCO-HIEID, "   
lv_hier_term_too_long  TYPE CKRCO, "   
lv_i_kokrs  TYPE TKA01-KOKRS, "   
lv_invalid_hiebg  TYPE TKA01, "   
lv_subterm_is_initial  TYPE TKA01, "   
lv_hierarchy_not_defined  TYPE TKA01, "   
lv_hierarchy_is_empty  TYPE TKA01, "   
lv_length_of_hierarchy_too_long  TYPE TKA01, "   
lv_too_many_hierarchy_fields  TYPE TKA01, "   
lv_other_errors  TYPE TKA01. "   

  CALL FUNCTION 'KKR_HNODE_GET_H'  "
    EXPORTING
         I_HIART = lv_i_hiart
         I_HIEID = lv_i_hieid
         I_KOKRS = lv_i_kokrs
    IMPORTING
         P_FIELD_INFO_TBL = lv_p_field_info_tbl
    EXCEPTIONS
        HIER_TERM_IS_INITIAL = 1
        HIER_TERM_TOO_LONG = 2
        INVALID_HIEBG = 3
        SUBTERM_IS_INITIAL = 4
        HIERARCHY_NOT_DEFINED = 5
        HIERARCHY_IS_EMPTY = 6
        LENGTH_OF_HIERARCHY_TOO_LONG = 7
        TOO_MANY_HIERARCHY_FIELDS = 8
        OTHER_ERRORS = 9
. " KKR_HNODE_GET_H




ABAP code using 7.40 inline data declarations to call FM KKR_HNODE_GET_H

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_i_hiart).
 
 
 
"SELECT single HIEID FROM CKRCO INTO @DATA(ld_i_hieid).
 
 
"SELECT single KOKRS FROM TKA01 INTO @DATA(ld_i_kokrs).
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!