SAP BBP_PD_CTR_ITEM_GETDETAIL Function Module for
BBP_PD_CTR_ITEM_GETDETAIL is a standard bbp pd ctr item getdetail 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 pd ctr item getdetail FM, simply by entering the name BBP_PD_CTR_ITEM_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PD_CTR
Program Name: SAPLBBP_PD_CTR
Main Program: SAPLBBP_PD_CTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PD_CTR_ITEM_GETDETAIL 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_PD_CTR_ITEM_GETDETAIL'".
EXPORTING
* I_GUID = "
* I_ATTACH_WITH_DOC = ' ' "
* I_DISP_CURRENCY = "
* I_DISP_DATE = "
* IV_HEADER_GUID = "
* IV_HEADER_SRC_GUID = "
* IV_VERSION_TYPE = "
IMPORTING
E_ITEM = "
ET_ATTACH = "
ET_CONDITIONS = "
TABLES
* E_ACCOUNT = "
* E_DIS = "
* E_ACTVAL = "
* E_ACC_ACTVAL = "
* E_ITM_REL = "
* E_MESSAGES = "
* E_PARTNER = "
* E_CONFIRM = "
* E_LONGTEXT = "
* E_LIMIT = "
* E_ORGDATA = "
* E_TAX = "
* E_ICF = "
* E_TOL = "
IMPORTING Parameters details for BBP_PD_CTR_ITEM_GETDETAIL
I_GUID -
Data type: CRMD_ORDERADM_I-GUIDOptional: Yes
Call by Reference: Yes
I_ATTACH_WITH_DOC -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_DISP_CURRENCY -
Data type: WAERSOptional: Yes
Call by Reference: Yes
I_DISP_DATE -
Data type: SYST-DATUMOptional: Yes
Call by Reference: Yes
IV_HEADER_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: Yes
Call by Reference: Yes
IV_HEADER_SRC_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: Yes
Call by Reference: Yes
IV_VERSION_TYPE -
Data type: BBP_VERSION_TYPEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_PD_CTR_ITEM_GETDETAIL
E_ITEM -
Data type: BBP_PDS_CTR_ITEM_DOptional: No
Call by Reference: Yes
ET_ATTACH -
Data type: BBPT_PDS_ATT_TOptional: No
Call by Reference: Yes
ET_CONDITIONS -
Data type: BBPT_PD_CND_DOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_PD_CTR_ITEM_GETDETAIL
E_ACCOUNT -
Data type: BBP_PDS_ACCOptional: Yes
Call by Reference: No ( called with pass by value option)
E_DIS -
Data type: BBP_PDS_DISOptional: Yes
Call by Reference: Yes
E_ACTVAL -
Data type: BBP_PDS_ACTVALOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ACC_ACTVAL -
Data type: BBP_PDS_ACTVALOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ITM_REL -
Data type: BBP_PDS_ILRELOptional: Yes
Call by Reference: No ( called with pass by value option)
E_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: No ( called with pass by value option)
E_PARTNER -
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
E_CONFIRM -
Data type: BBP_PDS_CONOptional: Yes
Call by Reference: No ( called with pass by value option)
E_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
E_LIMIT -
Data type: BBP_PDS_LIMITOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ORGDATA -
Data type: BBP_PDS_ORGOptional: Yes
Call by Reference: No ( called with pass by value option)
E_TAX -
Data type: BBP_PDS_TAXOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ICF -
Data type: BBP_PDS_ICF_CTROptional: Yes
Call by Reference: Yes
E_TOL -
Data type: BBP_PDS_TOLOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PD_CTR_ITEM_GETDETAIL 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_e_item | TYPE BBP_PDS_CTR_ITEM_D, " | |||
| lv_i_guid | TYPE CRMD_ORDERADM_I-GUID, " | |||
| lt_e_account | TYPE STANDARD TABLE OF BBP_PDS_ACC, " | |||
| lt_e_dis | TYPE STANDARD TABLE OF BBP_PDS_DIS, " | |||
| lt_e_actval | TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, " | |||
| lt_e_acc_actval | TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, " | |||
| lt_e_itm_rel | TYPE STANDARD TABLE OF BBP_PDS_ILREL, " | |||
| lt_e_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lv_et_attach | TYPE BBPT_PDS_ATT_T, " | |||
| lt_e_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lv_i_attach_with_doc | TYPE XFELD, " SPACE | |||
| lt_e_confirm | TYPE STANDARD TABLE OF BBP_PDS_CON, " | |||
| lv_et_conditions | TYPE BBPT_PD_CND_D, " | |||
| lv_i_disp_currency | TYPE WAERS, " | |||
| lt_e_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lv_i_disp_date | TYPE SYST-DATUM, " | |||
| lt_e_limit | TYPE STANDARD TABLE OF BBP_PDS_LIMIT, " | |||
| lv_iv_header_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lt_e_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG, " | |||
| lv_iv_header_src_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lt_e_tax | TYPE STANDARD TABLE OF BBP_PDS_TAX, " | |||
| lv_iv_version_type | TYPE BBP_VERSION_TYPE, " | |||
| lt_e_icf | TYPE STANDARD TABLE OF BBP_PDS_ICF_CTR, " | |||
| lt_e_tol | TYPE STANDARD TABLE OF BBP_PDS_TOL. " |
|   CALL FUNCTION 'BBP_PD_CTR_ITEM_GETDETAIL' " |
| EXPORTING | ||
| I_GUID | = lv_i_guid | |
| I_ATTACH_WITH_DOC | = lv_i_attach_with_doc | |
| I_DISP_CURRENCY | = lv_i_disp_currency | |
| I_DISP_DATE | = lv_i_disp_date | |
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IV_HEADER_SRC_GUID | = lv_iv_header_src_guid | |
| IV_VERSION_TYPE | = lv_iv_version_type | |
| IMPORTING | ||
| E_ITEM | = lv_e_item | |
| ET_ATTACH | = lv_et_attach | |
| ET_CONDITIONS | = lv_et_conditions | |
| TABLES | ||
| E_ACCOUNT | = lt_e_account | |
| E_DIS | = lt_e_dis | |
| E_ACTVAL | = lt_e_actval | |
| E_ACC_ACTVAL | = lt_e_acc_actval | |
| E_ITM_REL | = lt_e_itm_rel | |
| E_MESSAGES | = lt_e_messages | |
| E_PARTNER | = lt_e_partner | |
| E_CONFIRM | = lt_e_confirm | |
| E_LONGTEXT | = lt_e_longtext | |
| E_LIMIT | = lt_e_limit | |
| E_ORGDATA | = lt_e_orgdata | |
| E_TAX | = lt_e_tax | |
| E_ICF | = lt_e_icf | |
| E_TOL | = lt_e_tol | |
| . " BBP_PD_CTR_ITEM_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PD_CTR_ITEM_GETDETAIL
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 GUID FROM CRMD_ORDERADM_I INTO @DATA(ld_i_guid). | ||||
| DATA(ld_i_attach_with_doc) | = ' '. | |||
| "SELECT single DATUM FROM SYST INTO @DATA(ld_i_disp_date). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_header_guid). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_header_src_guid). | ||||
Search for further information about these or an SAP related objects