SAP BBP_SC_MAP_REQ_TO_PD Function Module for









BBP_SC_MAP_REQ_TO_PD is a standard bbp sc map req to pd 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 sc map req to pd FM, simply by entering the name BBP_SC_MAP_REQ_TO_PD into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_SC_MAP_REQ_TO_PD 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_SC_MAP_REQ_TO_PD'"
EXPORTING
IS_REQ_HEADER = "
* IS_REQ_HEADER_SRV = "

IMPORTING
ES_HEADER = "
ET_ATTACH = "

TABLES
IT_REQ_REFERENCE = "
* ET_ACCOUNT = "
* ET_PARTNER = "
* ET_LONGTEXT = "
* ET_LIMIT = "
* ET_ORGDATA = "
* ET_MESSAGES = "
* ET_ACTVAL = "
* ET_ITMLIM_REL = "
* ET_STATUS = "
IT_REQ_LINE = "
* IT_REQ_LINE_MAT = "
* IT_REQ_LINE_SRV = "
* IT_REQ_TEXT = "
* IT_REQ_ACCT = "
* IT_REQ_ATT = "
* IT_REQ_ADDRESS = "
* ET_ITEM = "
.



IMPORTING Parameters details for BBP_SC_MAP_REQ_TO_PD

IS_REQ_HEADER -

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

IS_REQ_HEADER_SRV -

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

EXPORTING Parameters details for BBP_SC_MAP_REQ_TO_PD

ES_HEADER -

Data type: BBP_PDS_SC_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)

TABLES Parameters details for BBP_SC_MAP_REQ_TO_PD

IT_REQ_REFERENCE -

Data type: REQREF
Optional: No
Call by Reference: Yes

ET_ACCOUNT -

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

ET_PARTNER -

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

ET_LONGTEXT -

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

ET_LIMIT -

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

ET_ORGDATA -

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

ET_MESSAGES -

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

ET_ACTVAL -

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

ET_ITMLIM_REL -

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

ET_STATUS -

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

IT_REQ_LINE -

Data type: REQLINE
Optional: No
Call by Reference: Yes

IT_REQ_LINE_MAT -

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

IT_REQ_LINE_SRV -

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

IT_REQ_TEXT -

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

IT_REQ_ACCT -

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

IT_REQ_ATT -

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

IT_REQ_ADDRESS -

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

ET_ITEM -

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

Copy and paste ABAP code example for BBP_SC_MAP_REQ_TO_PD 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_es_header  TYPE BBP_PDS_SC_HEADER_D, "   
lv_is_req_header  TYPE REQHEAD, "   
lt_it_req_reference  TYPE STANDARD TABLE OF REQREF, "   
lt_et_account  TYPE STANDARD TABLE OF BBP_PDS_ACC, "   
lt_et_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_et_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_et_limit  TYPE STANDARD TABLE OF BBP_PDS_LIMIT, "   
lt_et_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lt_et_actval  TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, "   
lt_et_itmlim_rel  TYPE STANDARD TABLE OF BBP_PDS_ILREL, "   
lt_et_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lt_it_req_line  TYPE STANDARD TABLE OF REQLINE, "   
lv_is_req_header_srv  TYPE REQHEADS, "   
lt_it_req_line_mat  TYPE STANDARD TABLE OF REQLINEMA, "   
lt_it_req_line_srv  TYPE STANDARD TABLE OF REQLINESR, "   
lt_it_req_text  TYPE STANDARD TABLE OF REQTEXT, "   
lt_it_req_acct  TYPE STANDARD TABLE OF REQACCT, "   
lt_it_req_att  TYPE STANDARD TABLE OF REQATT, "   
lt_it_req_address  TYPE STANDARD TABLE OF REQADDRESS, "   
lt_et_item  TYPE STANDARD TABLE OF BBP_PDS_SC_ITEM_D. "   

  CALL FUNCTION 'BBP_SC_MAP_REQ_TO_PD'  "
    EXPORTING
         IS_REQ_HEADER = lv_is_req_header
         IS_REQ_HEADER_SRV = lv_is_req_header_srv
    IMPORTING
         ES_HEADER = lv_es_header
         ET_ATTACH = lv_et_attach
    TABLES
         IT_REQ_REFERENCE = lt_it_req_reference
         ET_ACCOUNT = lt_et_account
         ET_PARTNER = lt_et_partner
         ET_LONGTEXT = lt_et_longtext
         ET_LIMIT = lt_et_limit
         ET_ORGDATA = lt_et_orgdata
         ET_MESSAGES = lt_et_messages
         ET_ACTVAL = lt_et_actval
         ET_ITMLIM_REL = lt_et_itmlim_rel
         ET_STATUS = lt_et_status
         IT_REQ_LINE = lt_it_req_line
         IT_REQ_LINE_MAT = lt_it_req_line_mat
         IT_REQ_LINE_SRV = lt_it_req_line_srv
         IT_REQ_TEXT = lt_it_req_text
         IT_REQ_ACCT = lt_it_req_acct
         IT_REQ_ATT = lt_it_req_att
         IT_REQ_ADDRESS = lt_it_req_address
         ET_ITEM = lt_et_item
. " BBP_SC_MAP_REQ_TO_PD




ABAP code using 7.40 inline data declarations to call FM BBP_SC_MAP_REQ_TO_PD

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



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!