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

Function BBP_PD_INV_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_INV_GETDETAIL'".
EXPORTING
* I_GUID = "
* I_OBJECT_ID = "
* I_REF_DOC_NO = "
* I_PARTNER_NO = "
* I_ATTACH_WITH_DOC = ' ' "
* I_WITH_ITEMDATA = 'X' "
* I_ITEM_SORTED_BY_HIERARCHY = 'X' "
* I_READ_FROM_ARCHIVE = ' ' "
IMPORTING
E_HEADER = "
ET_ATTACH = "
TABLES
* E_ITEM = "
* E_ICF = "
* E_HEADER_REL = "
* E_ITMLIM_REL = "
* E_OVE_REL = "
* ET_HUB_HREL = "
* ET_HUB_IREL = "
* ET_EXCHRATE = "
* E_VERSION = "
* E_STATUS = "
* E_MESSAGES = "
* E_ACCOUNT = "
* E_HISTORY_ARCH = "
* E_PARTNER = "
* E_LONGTEXT = "
* E_FREIGHT = "
* E_MSGI = "
* E_TAX = "
* E_ORGDATA = "
* E_HCF = "
IMPORTING Parameters details for BBP_PD_INV_GETDETAIL
I_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJECT_ID -
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REF_DOC_NO -
Data type: BBP_PDHGP-REF_DOC_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNER_NO -
Data type: CRMD_PARTNER-PARTNER_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ATTACH_WITH_DOC -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_WITH_ITEMDATA -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ITEM_SORTED_BY_HIERARCHY -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_READ_FROM_ARCHIVE -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_PD_INV_GETDETAIL
E_HEADER -
Data type: BBP_PDS_INV_HEADER_DOptional: No
Call by Reference: No ( called with pass by value option)
ET_ATTACH -
Data type: BBPT_PDS_ATT_TOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_PD_INV_GETDETAIL
E_ITEM -
Data type: BBP_PDS_INV_ITEM_DOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ICF -
Data type: BBP_PDS_ICF_INVOptional: Yes
Call by Reference: Yes
E_HEADER_REL -
Data type: BBP_PDS_HRELOptional: Yes
Call by Reference: Yes
E_ITMLIM_REL -
Data type: BBP_PDS_ILRELOptional: Yes
Call by Reference: Yes
E_OVE_REL -
Data type: BBP_PDS_OVE_RELOptional: Yes
Call by Reference: Yes
ET_HUB_HREL -
Data type: BBP_PDS_IVHUB_HRELOptional: Yes
Call by Reference: Yes
ET_HUB_IREL -
Data type: BBP_IV_ITEM_RELOptional: Yes
Call by Reference: Yes
ET_EXCHRATE -
Data type: BBP_PDS_EXROptional: Yes
Call by Reference: Yes
E_VERSION -
Data type: BBP_PDS_VERSION_LIST_INTERNALOptional: Yes
Call by Reference: Yes
E_STATUS -
Data type: BBP_PDS_STATUSOptional: Yes
Call by Reference: Yes
E_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ACCOUNT -
Data type: BBP_PDS_ACCOptional: Yes
Call by Reference: Yes
E_HISTORY_ARCH -
Data type: BBP_PDS_HISTORY_ARCHOptional: Yes
Call by Reference: Yes
E_PARTNER -
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: Yes
E_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
E_FREIGHT -
Data type: BBP_PDS_FREIGHTOptional: Yes
Call by Reference: Yes
E_MSGI -
Data type: BBP_PDS_MSGIOptional: Yes
Call by Reference: Yes
E_TAX -
Data type: BBP_PDS_TAXOptional: Yes
Call by Reference: Yes
E_ORGDATA -
Data type: BBP_PDS_ORGOptional: Yes
Call by Reference: Yes
E_HCF -
Data type: BBP_PDS_HCF_INVOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PD_INV_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: | ||||
| lt_e_item | TYPE STANDARD TABLE OF BBP_PDS_INV_ITEM_D, " | |||
| lv_i_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_e_header | TYPE BBP_PDS_INV_HEADER_D, " | |||
| lt_e_icf | TYPE STANDARD TABLE OF BBP_PDS_ICF_INV, " | |||
| lt_e_header_rel | TYPE STANDARD TABLE OF BBP_PDS_HREL, " | |||
| lt_e_itmlim_rel | TYPE STANDARD TABLE OF BBP_PDS_ILREL, " | |||
| lt_e_ove_rel | TYPE STANDARD TABLE OF BBP_PDS_OVE_REL, " | |||
| lt_et_hub_hrel | TYPE STANDARD TABLE OF BBP_PDS_IVHUB_HREL, " | |||
| lt_et_hub_irel | TYPE STANDARD TABLE OF BBP_IV_ITEM_REL, " | |||
| lt_et_exchrate | TYPE STANDARD TABLE OF BBP_PDS_EXR, " | |||
| lt_e_version | TYPE STANDARD TABLE OF BBP_PDS_VERSION_LIST_INTERNAL, " | |||
| lt_e_status | TYPE STANDARD TABLE OF BBP_PDS_STATUS, " | |||
| lt_e_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lv_et_attach | TYPE BBPT_PDS_ATT_T, " | |||
| lt_e_account | TYPE STANDARD TABLE OF BBP_PDS_ACC, " | |||
| lv_i_object_id | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lt_e_history_arch | TYPE STANDARD TABLE OF BBP_PDS_HISTORY_ARCH, " | |||
| lt_e_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lv_i_ref_doc_no | TYPE BBP_PDHGP-REF_DOC_NO, " | |||
| lt_e_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lv_i_partner_no | TYPE CRMD_PARTNER-PARTNER_NO, " | |||
| lt_e_freight | TYPE STANDARD TABLE OF BBP_PDS_FREIGHT, " | |||
| lv_i_attach_with_doc | TYPE XFELD, " SPACE | |||
| lt_e_msgi | TYPE STANDARD TABLE OF BBP_PDS_MSGI, " | |||
| lv_i_with_itemdata | TYPE XFELD, " 'X' | |||
| lt_e_tax | TYPE STANDARD TABLE OF BBP_PDS_TAX, " | |||
| lv_i_item_sorted_by_hierarchy | TYPE XFELD, " 'X' | |||
| lt_e_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG, " | |||
| lv_i_read_from_archive | TYPE XFELD, " SPACE | |||
| lt_e_hcf | TYPE STANDARD TABLE OF BBP_PDS_HCF_INV. " |
|   CALL FUNCTION 'BBP_PD_INV_GETDETAIL' " |
| EXPORTING | ||
| I_GUID | = lv_i_guid | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_REF_DOC_NO | = lv_i_ref_doc_no | |
| I_PARTNER_NO | = lv_i_partner_no | |
| I_ATTACH_WITH_DOC | = lv_i_attach_with_doc | |
| I_WITH_ITEMDATA | = lv_i_with_itemdata | |
| I_ITEM_SORTED_BY_HIERARCHY | = lv_i_item_sorted_by_hierarchy | |
| I_READ_FROM_ARCHIVE | = lv_i_read_from_archive | |
| IMPORTING | ||
| E_HEADER | = lv_e_header | |
| ET_ATTACH | = lv_et_attach | |
| TABLES | ||
| E_ITEM | = lt_e_item | |
| E_ICF | = lt_e_icf | |
| E_HEADER_REL | = lt_e_header_rel | |
| E_ITMLIM_REL | = lt_e_itmlim_rel | |
| E_OVE_REL | = lt_e_ove_rel | |
| ET_HUB_HREL | = lt_et_hub_hrel | |
| ET_HUB_IREL | = lt_et_hub_irel | |
| ET_EXCHRATE | = lt_et_exchrate | |
| E_VERSION | = lt_e_version | |
| E_STATUS | = lt_e_status | |
| E_MESSAGES | = lt_e_messages | |
| E_ACCOUNT | = lt_e_account | |
| E_HISTORY_ARCH | = lt_e_history_arch | |
| E_PARTNER | = lt_e_partner | |
| E_LONGTEXT | = lt_e_longtext | |
| E_FREIGHT | = lt_e_freight | |
| E_MSGI | = lt_e_msgi | |
| E_TAX | = lt_e_tax | |
| E_ORGDATA | = lt_e_orgdata | |
| E_HCF | = lt_e_hcf | |
| . " BBP_PD_INV_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PD_INV_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_H INTO @DATA(ld_i_guid). | ||||
| "SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_i_object_id). | ||||
| "SELECT single REF_DOC_NO FROM BBP_PDHGP INTO @DATA(ld_i_ref_doc_no). | ||||
| "SELECT single PARTNER_NO FROM CRMD_PARTNER INTO @DATA(ld_i_partner_no). | ||||
| DATA(ld_i_attach_with_doc) | = ' '. | |||
| DATA(ld_i_with_itemdata) | = 'X'. | |||
| DATA(ld_i_item_sorted_by_hierarchy) | = 'X'. | |||
| DATA(ld_i_read_from_archive) | = ' '. | |||
Search for further information about these or an SAP related objects