SAP BBP_PDH_HIER_GET_NODES Function Module for
BBP_PDH_HIER_GET_NODES is a standard bbp pdh hier get nodes 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 bbp pdh hier get nodes FM, simply by entering the name BBP_PDH_HIER_GET_NODES into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDH_HIER
Program Name: SAPLBBP_PDH_HIER
Main Program: SAPLBBP_PDH_HIER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDH_HIER_GET_NODES 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 'BBP_PDH_HIER_GET_NODES'".
EXPORTING
* IV_GUID = "GUID of a CRM Order Object
* IV_OBJECT_ID = "Transaction Number
* IV_OBJECT_TYPE = "Business Trans. Cat.
* IV_READ_UPWARDS = ' ' "Checkbox
* IV_MAX_LEVELS_TO_READ_UPWARD = "Natural number
* IV_READ_DOWNWARDS = ' ' "Checkbox
* IV_MAX_LEVELS_TO_READ_DOWNWARD = "Natural number
IMPORTING
ET_HEADER_HIER = "Contract Hiearchies
TABLES
* ET_MESSAGES = "Error Message for Procurement Document Methods
IMPORTING Parameters details for BBP_PDH_HIER_GET_NODES
IV_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_ID - Transaction Number
Data type: CRMT_OBJECT_ID_DBOptional: Yes
Call by Reference: Yes
IV_OBJECT_TYPE - Business Trans. Cat.
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: Yes
Call by Reference: Yes
IV_READ_UPWARDS - Checkbox
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MAX_LEVELS_TO_READ_UPWARD - Natural number
Data type: BBP_HIER_MAX_LEVELSOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_DOWNWARDS - Checkbox
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MAX_LEVELS_TO_READ_DOWNWARD - Natural number
Data type: BBP_HIER_MAX_LEVELSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_PDH_HIER_GET_NODES
ET_HEADER_HIER - Contract Hiearchies
Data type: BBPT_PDH_HIER_TOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_PDH_HIER_GET_NODES
ET_MESSAGES - Error Message for Procurement Document Methods
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDH_HIER_GET_NODES 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_iv_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lv_et_header_hier | TYPE BBPT_PDH_HIER_T, " | |||
| lv_iv_object_id | TYPE CRMT_OBJECT_ID_DB, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_iv_read_upwards | TYPE XFELD, " SPACE | |||
| lv_iv_max_levels_to_read_upward | TYPE BBP_HIER_MAX_LEVELS, " | |||
| lv_iv_read_downwards | TYPE XFELD, " SPACE | |||
| lv_iv_max_levels_to_read_downward | TYPE BBP_HIER_MAX_LEVELS. " |
|   CALL FUNCTION 'BBP_PDH_HIER_GET_NODES' " |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_READ_UPWARDS | = lv_iv_read_upwards | |
| IV_MAX_LEVELS_TO_READ_UPWARD | = lv_iv_max_levels_to_read_upward | |
| IV_READ_DOWNWARDS | = lv_iv_read_downwards | |
| IV_MAX_LEVELS_TO_READ_DOWNWARD | = lv_iv_max_levels_to_read_downward | |
| IMPORTING | ||
| ET_HEADER_HIER | = lv_et_header_hier | |
| TABLES | ||
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_PDH_HIER_GET_NODES | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDH_HIER_GET_NODES
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 OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_type). | ||||
| DATA(ld_iv_read_upwards) | = ' '. | |||
| DATA(ld_iv_read_downwards) | = ' '. | |||
Search for further information about these or an SAP related objects