SAP BBP_PD_AUC_GETDETAIL Function Module for









BBP_PD_AUC_GETDETAIL is a standard bbp pd auc 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 auc getdetail FM, simply by entering the name BBP_PD_AUC_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PD_AUC
Program Name: SAPLBBP_PD_AUC
Main Program: SAPLBBP_PD_AUC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_PD_AUC_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_AUC_GETDETAIL'"
EXPORTING
* I_GUID = "
* I_OBJECT_ID = "
* I_ATTACH_WITH_DOC = "
* IT_DYN_ATTR = "
* I_WITH_ITEMDATA = 'X' "
* I_ITEM_SORTED_BY_HIERARCHY = "
* I_READ_FROM_ARCHIVE = ' ' "

IMPORTING
E_HEADER = "
ET_ATTACH = "
ET_DYN_ATTR = "

TABLES
* E_ITEM = "
* E_FAC = "
* E_ACTIVITIES = "
* E_MESSAGES = "
* E_HCF = "
* E_ICF = "
* ET_EXCHRATE = "
* E_PARTNER = "
* E_LONGTEXT = "
* E_STATUS = "
* E_ORGDATA = "
* E_CHAT = "
* E_BID_HIST = "
* E_HEADER_REL = "
* E_ITMLIM_REL = "
.



IMPORTING Parameters details for BBP_PD_AUC_GETDETAIL

I_GUID -

Data type: CRMD_ORDERADM_H-GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OBJECT_ID -

Data type: CRMD_ORDERADM_H-OBJECT_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ATTACH_WITH_DOC -

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_DYN_ATTR -

Data type: BBPT_PDS_DYNATTRIBUTE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_WITH_ITEMDATA -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ITEM_SORTED_BY_HIERARCHY -

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_FROM_ARCHIVE -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BBP_PD_AUC_GETDETAIL

E_HEADER -

Data type: BBP_PDS_AUC_HEADER_D
Optional: No
Call by Reference: No ( called with pass by value option)

ET_ATTACH -

Data type: BBPT_PDS_ATT_T
Optional: No
Call by Reference: No ( called with pass by value option)

ET_DYN_ATTR -

Data type: BBPT_PDS_DYNATTRIBUTE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_PD_AUC_GETDETAIL

E_ITEM -

Data type: BBP_PDS_AUC_ITEM_D
Optional: Yes
Call by Reference: Yes

E_FAC -

Data type: BBP_PDS_FAC
Optional: Yes
Call by Reference: Yes

E_ACTIVITIES -

Data type: BBPS_LA_ACTIVITY
Optional: Yes
Call by Reference: Yes

E_MESSAGES -

Data type: BBP_PDS_MESSAGES
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_HCF -

Data type: BBP_PDS_HCF_AUC
Optional: Yes
Call by Reference: Yes

E_ICF -

Data type: BBP_PDS_ICF_AUC
Optional: Yes
Call by Reference: Yes

ET_EXCHRATE -

Data type: BBP_PDS_EXR
Optional: Yes
Call by Reference: Yes

E_PARTNER -

Data type: BBP_PDS_PARTNER
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_LONGTEXT -

Data type: BBP_PDS_LONGTEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_STATUS -

Data type: BBP_PDS_STATUS
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_ORGDATA -

Data type: BBP_PDS_ORG
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_CHAT -

Data type: BBPS_LA_BIZAPI_CHAT
Optional: Yes
Call by Reference: Yes

E_BID_HIST -

Data type: BBPS_LA_BIZAPI_BID
Optional: Yes
Call by Reference: Yes

E_HEADER_REL -

Data type: BBP_PDS_HREL
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_ITMLIM_REL -

Data type: BBP_PDS_ILREL
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_PD_AUC_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_AUC_ITEM_D, "   
lv_i_guid  TYPE CRMD_ORDERADM_H-GUID, "   
lv_e_header  TYPE BBP_PDS_AUC_HEADER_D, "   
lt_e_fac  TYPE STANDARD TABLE OF BBP_PDS_FAC, "   
lt_e_activities  TYPE STANDARD TABLE OF BBPS_LA_ACTIVITY, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lt_e_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_AUC, "   
lt_e_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_AUC, "   
lt_et_exchrate  TYPE STANDARD TABLE OF BBP_PDS_EXR, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lt_e_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lv_i_object_id  TYPE CRMD_ORDERADM_H-OBJECT_ID, "   
lt_e_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lv_et_dyn_attr  TYPE BBPT_PDS_DYNATTRIBUTE, "   
lv_i_attach_with_doc  TYPE XFELD, "   
lt_e_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lv_it_dyn_attr  TYPE BBPT_PDS_DYNATTRIBUTE, "   
lt_e_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lv_i_with_itemdata  TYPE XFELD, "   'X'
lt_e_chat  TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_CHAT, "   
lv_i_item_sorted_by_hierarchy  TYPE XFELD, "   
lt_e_bid_hist  TYPE STANDARD TABLE OF BBPS_LA_BIZAPI_BID, "   
lv_i_read_from_archive  TYPE XFELD, "   SPACE
lt_e_header_rel  TYPE STANDARD TABLE OF BBP_PDS_HREL, "   
lt_e_itmlim_rel  TYPE STANDARD TABLE OF BBP_PDS_ILREL. "   

  CALL FUNCTION 'BBP_PD_AUC_GETDETAIL'  "
    EXPORTING
         I_GUID = lv_i_guid
         I_OBJECT_ID = lv_i_object_id
         I_ATTACH_WITH_DOC = lv_i_attach_with_doc
         IT_DYN_ATTR = lv_it_dyn_attr
         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
         ET_DYN_ATTR = lv_et_dyn_attr
    TABLES
         E_ITEM = lt_e_item
         E_FAC = lt_e_fac
         E_ACTIVITIES = lt_e_activities
         E_MESSAGES = lt_e_messages
         E_HCF = lt_e_hcf
         E_ICF = lt_e_icf
         ET_EXCHRATE = lt_et_exchrate
         E_PARTNER = lt_e_partner
         E_LONGTEXT = lt_e_longtext
         E_STATUS = lt_e_status
         E_ORGDATA = lt_e_orgdata
         E_CHAT = lt_e_chat
         E_BID_HIST = lt_e_bid_hist
         E_HEADER_REL = lt_e_header_rel
         E_ITMLIM_REL = lt_e_itmlim_rel
. " BBP_PD_AUC_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM BBP_PD_AUC_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).
 
 
 
 
 
 
 
DATA(ld_i_with_itemdata) = 'X'.
 
 
 
 
DATA(ld_i_read_from_archive) = ' '.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!