SAP BBP_BD_INV_RESP_TO_BAPI_MAPS Function Module for









BBP_BD_INV_RESP_TO_BAPI_MAPS is a standard bbp bd inv resp to bapi maps 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 bd inv resp to bapi maps FM, simply by entering the name BBP_BD_INV_RESP_TO_BAPI_MAPS into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_BD_INV_RESP_TO_BAPI_MAPS 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_BD_INV_RESP_TO_BAPI_MAPS'"
EXPORTING
IS_HEADER = "
IT_ITEM = "
IT_PARTNER = "
* IT_LONGTEXT = "
* IT_ATTACH = "

IMPORTING
ES_HEADER = "
ES_BILL_TO_PARTY = "
ES_BILL_TO_PARTY_CONTACT = "
ES_INVOICING_PARTY = "
ES_INVOICING_PARTY_CONTACT = "
ET_ITEM = "
ET_TEXT = "
ET_ATTACH = "
.



IMPORTING Parameters details for BBP_BD_INV_RESP_TO_BAPI_MAPS

IS_HEADER -

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

IT_ITEM -

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

IT_PARTNER -

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

IT_LONGTEXT -

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

IT_ATTACH -

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

EXPORTING Parameters details for BBP_BD_INV_RESP_TO_BAPI_MAPS

ES_HEADER -

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

ES_BILL_TO_PARTY -

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

ES_BILL_TO_PARTY_CONTACT -

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

ES_INVOICING_PARTY -

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

ES_INVOICING_PARTY_CONTACT -

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

ET_ITEM -

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

ET_TEXT -

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

ET_ATTACH -

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

Copy and paste ABAP code example for BBP_BD_INV_RESP_TO_BAPI_MAPS 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 BAPI_INVRESPONSE_HEADER, "   
lv_is_header  TYPE BBPS_PDEXT_INV_HEADER_D, "   
lv_it_item  TYPE BBPT_PDEXT_INV_ITEM_D, "   
lv_es_bill_to_party  TYPE BAPI_BUP_S, "   
lv_it_partner  TYPE BBPT_PDEXT_PARTNER, "   
lv_es_bill_to_party_contact  TYPE BAPI_BUP_S, "   
lv_it_longtext  TYPE BBPT_PDEXT_LONGTEXT, "   
lv_es_invoicing_party  TYPE BAPI_BUP_S, "   
lv_it_attach  TYPE BBPT_PDEXT_ATTACH, "   
lv_es_invoicing_party_contact  TYPE BAPI_BUP_S, "   
lv_et_item  TYPE BAPI_INVRESPONSE_ITEM_T, "   
lv_et_text  TYPE BBPT_TEXT_I, "   
lv_et_attach  TYPE BAPI_ATT_BC_T. "   

  CALL FUNCTION 'BBP_BD_INV_RESP_TO_BAPI_MAPS'  "
    EXPORTING
         IS_HEADER = lv_is_header
         IT_ITEM = lv_it_item
         IT_PARTNER = lv_it_partner
         IT_LONGTEXT = lv_it_longtext
         IT_ATTACH = lv_it_attach
    IMPORTING
         ES_HEADER = lv_es_header
         ES_BILL_TO_PARTY = lv_es_bill_to_party
         ES_BILL_TO_PARTY_CONTACT = lv_es_bill_to_party_contact
         ES_INVOICING_PARTY = lv_es_invoicing_party
         ES_INVOICING_PARTY_CONTACT = lv_es_invoicing_party_contact
         ET_ITEM = lv_et_item
         ET_TEXT = lv_et_text
         ET_ATTACH = lv_et_attach
. " BBP_BD_INV_RESP_TO_BAPI_MAPS




ABAP code using 7.40 inline data declarations to call FM BBP_BD_INV_RESP_TO_BAPI_MAPS

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!