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

Function BBP_PD_SC_TRANSFER_MULTI_AUC 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_SC_TRANSFER_MULTI_AUC'".
EXPORTING
IS_TRANSFER_ACTION = "
TABLES
IT_HEADER = "
* ET_REFLIST = "
* ET_HEADER = "
* ET_ITEM = "
ET_MESSAGES = "
IT_ITEM = "
IT_PARTNER = "
IT_ATTACH = "
IT_LONGTEXT = "
* IT_DOC_DESCR = "
IT_ORG = "
* IT_HCF = "
* IT_ICF = "
IMPORTING Parameters details for BBP_PD_SC_TRANSFER_MULTI_AUC
IS_TRANSFER_ACTION -
Data type: BBP_PDS_TRANSFER_ACTIONOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_PD_SC_TRANSFER_MULTI_AUC
IT_HEADER -
Data type: BBP_PDS_TRANSFER_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
ET_REFLIST -
Data type: BBP_PDS_REFLISTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_HEADER -
Data type: BBP_PDS_HEADEROptional: Yes
Call by Reference: Yes
ET_ITEM -
Data type: BBP_PDS_ITEMOptional: Yes
Call by Reference: Yes
ET_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: No
Call by Reference: No ( called with pass by value option)
IT_ITEM -
Data type: BBP_PDS_SC_ITEM_DOptional: No
Call by Reference: No ( called with pass by value option)
IT_PARTNER -
Data type: BBP_PDS_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IT_ATTACH -
Data type: BBPT_PDS_ATT_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: No
Call by Reference: No ( called with pass by value option)
IT_DOC_DESCR -
Data type: BBP_PDS_OBJ_DECRIPTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ORG -
Data type: BBP_PDS_ORGOptional: No
Call by Reference: No ( called with pass by value option)
IT_HCF -
Data type: BBP_PDS_HCF_SCOptional: Yes
Call by Reference: Yes
IT_ICF -
Data type: BBP_PDS_ICF_SCOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PD_SC_TRANSFER_MULTI_AUC 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_it_header | TYPE STANDARD TABLE OF BBP_PDS_TRANSFER_HEADER, " | |||
| lv_is_transfer_action | TYPE BBP_PDS_TRANSFER_ACTION, " | |||
| lt_et_reflist | TYPE STANDARD TABLE OF BBP_PDS_REFLIST, " | |||
| lt_et_header | TYPE STANDARD TABLE OF BBP_PDS_HEADER, " | |||
| lt_et_item | TYPE STANDARD TABLE OF BBP_PDS_ITEM, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lt_it_item | TYPE STANDARD TABLE OF BBP_PDS_SC_ITEM_D, " | |||
| lt_it_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lt_it_attach | TYPE STANDARD TABLE OF BBPT_PDS_ATT_T, " | |||
| lt_it_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lt_it_doc_descr | TYPE STANDARD TABLE OF BBP_PDS_OBJ_DECRIPTION, " | |||
| lt_it_org | TYPE STANDARD TABLE OF BBP_PDS_ORG, " | |||
| lt_it_hcf | TYPE STANDARD TABLE OF BBP_PDS_HCF_SC, " | |||
| lt_it_icf | TYPE STANDARD TABLE OF BBP_PDS_ICF_SC. " |
|   CALL FUNCTION 'BBP_PD_SC_TRANSFER_MULTI_AUC' " |
| EXPORTING | ||
| IS_TRANSFER_ACTION | = lv_is_transfer_action | |
| TABLES | ||
| IT_HEADER | = lt_it_header | |
| ET_REFLIST | = lt_et_reflist | |
| ET_HEADER | = lt_et_header | |
| ET_ITEM | = lt_et_item | |
| ET_MESSAGES | = lt_et_messages | |
| IT_ITEM | = lt_it_item | |
| IT_PARTNER | = lt_it_partner | |
| IT_ATTACH | = lt_it_attach | |
| IT_LONGTEXT | = lt_it_longtext | |
| IT_DOC_DESCR | = lt_it_doc_descr | |
| IT_ORG | = lt_it_org | |
| IT_HCF | = lt_it_hcf | |
| IT_ICF | = lt_it_icf | |
| . " BBP_PD_SC_TRANSFER_MULTI_AUC | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PD_SC_TRANSFER_MULTI_AUC
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