K_CKPH_GET_ROOT_PATH SAP Function module

K_CKPH_GET_ROOT_PATH is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name K_CKPH_GET_ROOT_PATH into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: KKPH
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM K_CKPH_GET_ROOT_PATH - K CKPH GET ROOT PATH

CALL FUNCTION 'K_CKPH_GET_ROOT_PATH' "
  EXPORTING
*   datbi = '99991231'          " ckph-datbi    Cost object valid until
    kstrg =                     " ckph-kstrg    Cost object/hierarchy node
*   bypassing_buffer = SPACE    " c
  TABLES
    ckph_path =                 " ckph          Hierarchy path ROOT --> KSTRG
  EXCEPTIONS
    NOT_FOUND = 1               "               Cost object/hierarchy node does not exist
    NO_ROOT = 2                 "
    SYSTEM_FAILURE = 3          "               Hierarchy contains cycle
    .  "  K_CKPH_GET_ROOT_PATH

ABAP code example for Function Module K_CKPH_GET_ROOT_PATH

The ABAP code below is a full code listing to execute function module K_CKPH_GET_ROOT_PATH including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_ckph_path  
 
 TYPE STANDARD TABLE OF CKPH,"TABLES PARAM
wa_ckph_path
 
 LIKE LINE OF it_ckph_path
.

 

SELECT single DATBI 
  FROM CKPH 
  INTO @DATA(ld_datbi).

 

SELECT single KSTRG 
  FROM CKPH 
  INTO @DATA(ld_kstrg).


DATA(ld_bypassing_buffer) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_ckph_path to it_ckph_path.
.

CALL FUNCTION 'K_CKPH_GET_ROOT_PATH'
  EXPORTING
*   datbi =                      ld_datbi
    kstrg =                      ld_kstrg
*   bypassing_buffer =           ld_bypassing_buffer
  TABLES
    ckph_path =                  it_ckph_path
  EXCEPTIONS
    NOT_FOUND =                  1
    NO_ROOT =                    2
    SYSTEM_FAILURE =             3
    .  "  K_CKPH_GET_ROOT_PATH

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_datbi
 
 TYPE CKPH-DATBI ,
it_ckph_path
 
 TYPE STANDARD TABLE OF CKPH ,
wa_ckph_path
 
 LIKE LINE OF it_ckph_path,
ld_kstrg
 
 TYPE CKPH-KSTRG ,
ld_bypassing_buffer
 
 TYPE C .



SELECT single DATBI 
  FROM CKPH 
  INTO ld_datbi.
 

"populate fields of struture and append to itab
append wa_ckph_path to it_ckph_path.

SELECT single KSTRG 
  FROM CKPH 
  INTO ld_kstrg.

ld_bypassing_buffer = 'Check type of data required'.