SAP K_KKR_HNODE_EDIT Function Module for
K_KKR_HNODE_EDIT is a standard k kkr hnode edit 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 k kkr hnode edit FM, simply by entering the name K_KKR_HNODE_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: KRHT
Program Name: SAPLKRHT
Main Program: SAPLKRHT
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_KKR_HNODE_EDIT 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 'K_KKR_HNODE_EDIT'".
EXPORTING
* ETYPE = ' ' "Edit category
HIART = "Hierarchy type
HIEID = "Hierarchy ID
VARHIEBG = "Unedited hierarchy code
* MULTI_KZ = "
* EDIT = "
IMPORTING
EDTHIEBG = "Edited hierarchy code
EDTSTUFE = "Level of the hierarchy code
EXCEPTIONS
HIER_TERM_IS_INITIAL = 1 HIER_TERM_TOO_LONG = 2 INVALID_HIEBG = 3 SUBTERM_IS_INITIAL = 4
IMPORTING Parameters details for K_KKR_HNODE_EDIT
ETYPE - Edit category
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
HIART - Hierarchy type
Data type: CKRCO-HIARTOptional: No
Call by Reference: No ( called with pass by value option)
HIEID - Hierarchy ID
Data type: CKRCO-HIEIDOptional: No
Call by Reference: No ( called with pass by value option)
VARHIEBG - Unedited hierarchy code
Data type: CKRCO-VARHIEBGOptional: No
Call by Reference: No ( called with pass by value option)
MULTI_KZ -
Data type: SY-BATCHOptional: Yes
Call by Reference: No ( called with pass by value option)
EDIT -
Data type: BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for K_KKR_HNODE_EDIT
EDTHIEBG - Edited hierarchy code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EDTSTUFE - Level of the hierarchy code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
HIER_TERM_IS_INITIAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HIER_TERM_TOO_LONG - Entered hierarchy code is 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 - Empty internal sub-hierarchy term
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for K_KKR_HNODE_EDIT 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_etype | TYPE STRING, " SPACE | |||
| lv_edthiebg | TYPE STRING, " | |||
| lv_hier_term_is_initial | TYPE STRING, " | |||
| lv_hiart | TYPE CKRCO-HIART, " | |||
| lv_edtstufe | TYPE CKRCO, " | |||
| lv_hier_term_too_long | TYPE CKRCO, " | |||
| lv_hieid | TYPE CKRCO-HIEID, " | |||
| lv_invalid_hiebg | TYPE CKRCO, " | |||
| lv_varhiebg | TYPE CKRCO-VARHIEBG, " | |||
| lv_subterm_is_initial | TYPE CKRCO, " | |||
| lv_multi_kz | TYPE SY-BATCH, " | |||
| lv_edit | TYPE BOOLE. " |
|   CALL FUNCTION 'K_KKR_HNODE_EDIT' " |
| EXPORTING | ||
| ETYPE | = lv_etype | |
| HIART | = lv_hiart | |
| HIEID | = lv_hieid | |
| VARHIEBG | = lv_varhiebg | |
| MULTI_KZ | = lv_multi_kz | |
| EDIT | = lv_edit | |
| IMPORTING | ||
| EDTHIEBG | = lv_edthiebg | |
| EDTSTUFE | = lv_edtstufe | |
| EXCEPTIONS | ||
| HIER_TERM_IS_INITIAL = 1 | ||
| HIER_TERM_TOO_LONG = 2 | ||
| INVALID_HIEBG = 3 | ||
| SUBTERM_IS_INITIAL = 4 | ||
| . " K_KKR_HNODE_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM K_KKR_HNODE_EDIT
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.| DATA(ld_etype) | = ' '. | |||
| "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_varhiebg). | ||||
| "SELECT single BATCH FROM SY INTO @DATA(ld_multi_kz). | ||||
Search for further information about these or an SAP related objects