SAP BBP_CTR_UI_HIER_GET_PAI Function Module for Transfer data from screen to caller
BBP_CTR_UI_HIER_GET_PAI is a standard bbp ctr ui hier get pai SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer data from screen to caller processing and below is the pattern details for this FM, 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 ctr ui hier get pai FM, simply by entering the name BBP_CTR_UI_HIER_GET_PAI into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CTR_UI_HIER
Program Name: SAPLBBP_CTR_UI_HIER
Main Program: SAPLBBP_CTR_UI_HIER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CTR_UI_HIER_GET_PAI 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_CTR_UI_HIER_GET_PAI'"Transfer data from screen to caller.
IMPORTING
EV_ACTUAL_PARENT_GUID = "Globally Unique identifier
EV_ACTUAL_PARENT_ID = "Transaction Number
ET_MESSAGES = "Error Messages
EXPORTING Parameters details for BBP_CTR_UI_HIER_GET_PAI
EV_ACTUAL_PARENT_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
EV_ACTUAL_PARENT_ID - Transaction Number
Data type: CRMT_OBJECT_ID_DBOptional: No
Call by Reference: Yes
ET_MESSAGES - Error Messages
Data type: BBPT_PD_MESSAGESOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CTR_UI_HIER_GET_PAI 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_ev_actual_parent_guid | TYPE BBP_GUID, " | |||
| lv_ev_actual_parent_id | TYPE CRMT_OBJECT_ID_DB, " | |||
| lv_et_messages | TYPE BBPT_PD_MESSAGES. " |
|   CALL FUNCTION 'BBP_CTR_UI_HIER_GET_PAI' "Transfer data from screen to caller |
| IMPORTING | ||
| EV_ACTUAL_PARENT_GUID | = lv_ev_actual_parent_guid | |
| EV_ACTUAL_PARENT_ID | = lv_ev_actual_parent_id | |
| ET_MESSAGES | = lv_et_messages | |
| . " BBP_CTR_UI_HIER_GET_PAI | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CTR_UI_HIER_GET_PAI
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.Search for further information about these or an SAP related objects