BUHI_GET_PATH SAP Function module

BUHI_GET_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 BUHI_GET_PATH into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BUHI_GET_PATH - BUHI GET PATH

CALL FUNCTION 'BUHI_GET_PATH' "
  EXPORTING
    iv_partner_guid =           " bu_partner_guid  Business Partner GUID
    iv_hierarchy_type =         " bu_hierarchy_type
*   iv_valid_time =             " timestamp     UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
*   iv_reset_buffer =           " bu_boolean    Boolean Type in BP, Do Not Use in Interfaces!
  IMPORTING
    et_hierarchy_paths =        " bus_hierarchy_path_t_t
    et_tree =                   " bu_tree_search_term_t
  EXCEPTIONS
    PATH_CAN_NOT_BE_DETERMINED = 1  "
    PARTNER_NOT_FOUND = 2       "
    .  "  BUHI_GET_PATH

ABAP code example for Function Module BUHI_GET_PATH

The ABAP code below is a full code listing to execute function module BUHI_GET_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:
ld_et_hierarchy_paths  
 
 TYPE BUS_HIERARCHY_PATH_T_T
,
ld_et_tree  
 
 TYPE BU_TREE_SEARCH_TERM_T
.


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

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

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

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

CALL FUNCTION 'BUHI_GET_PATH'
  EXPORTING
    iv_partner_guid =            ld_iv_partner_guid
    iv_hierarchy_type =          ld_iv_hierarchy_type
*   iv_valid_time =              ld_iv_valid_time
*   iv_reset_buffer =            ld_iv_reset_buffer
  IMPORTING
    et_hierarchy_paths =         ld_et_hierarchy_paths
    et_tree =                    ld_et_tree
  EXCEPTIONS
    PATH_CAN_NOT_BE_DETERMINED =    1
    PARTNER_NOT_FOUND =          2
    .  "  BUHI_GET_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
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_et_hierarchy_paths
 
 TYPE BUS_HIERARCHY_PATH_T_T ,
ld_iv_partner_guid
 
 TYPE BU_PARTNER_GUID ,
ld_et_tree
 
 TYPE BU_TREE_SEARCH_TERM_T ,
ld_iv_hierarchy_type
 
 TYPE BU_HIERARCHY_TYPE ,
ld_iv_valid_time
 
 TYPE TIMESTAMP ,
ld_iv_reset_buffer
 
 TYPE BU_BOOLEAN .


ld_iv_partner_guid = 'Check type of data required'.
ld_iv_hierarchy_type = 'Check type of data required'.
ld_iv_valid_time = 'Check type of data required'.
ld_iv_reset_buffer = 'Check type of data required'.