SAP BBP_EXTREQ_INBOUND Function Module for









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

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



Function BBP_EXTREQ_INBOUND 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_EXTREQ_INBOUND'"
EXPORTING
I_HEADER = "
* I_HEADER_CUST = "

IMPORTING
E_HEADER = "

TABLES
* I_ITEMS = "
* I_ATTACH = "
* RETURN = "
* I_ADDON_FIELDS = "
* I_ITEMS_CUST = "
I_ACTION = "
* I_ACC = "
* I_ACC_CUST = "
* I_LIMIT = "
* I_TEXTS = "
* I_BUP = "
* I_ORG = "
.



IMPORTING Parameters details for BBP_EXTREQ_INBOUND

I_HEADER -

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

I_HEADER_CUST -

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

EXPORTING Parameters details for BBP_EXTREQ_INBOUND

E_HEADER -

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

TABLES Parameters details for BBP_EXTREQ_INBOUND

I_ITEMS -

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

I_ATTACH -

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

RETURN -

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

I_ADDON_FIELDS -

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

I_ITEMS_CUST -

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

I_ACTION -

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

I_ACC -

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

I_ACC_CUST -

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

I_LIMIT -

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

I_TEXTS -

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

I_BUP -

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

I_ORG -

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

Copy and paste ABAP code example for BBP_EXTREQ_INBOUND 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_i_items  TYPE STANDARD TABLE OF BAPI_SC_ITEM_C, "   
lv_e_header  TYPE BAPI_SC_HEADER_D, "   
lv_i_header  TYPE BAPI_SC_HEADER_C, "   
lt_i_attach  TYPE STANDARD TABLE OF BAPI_ATT_C, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_i_addon_fields  TYPE STANDARD TABLE OF BBPS_IF_CUSTOMER_FIELDS_PI, "   
lt_i_items_cust  TYPE STANDARD TABLE OF BAPI_SC_ITEM_CUST_C, "   
lv_i_header_cust  TYPE BAPI_SC_HEADER_CUST_C, "   
lt_i_action  TYPE STANDARD TABLE OF BBPS_EXTREQ_ACTION, "   
lt_i_acc  TYPE STANDARD TABLE OF BAPI_ACC_C, "   
lt_i_acc_cust  TYPE STANDARD TABLE OF BAPI_ACC_CUST_C, "   
lt_i_limit  TYPE STANDARD TABLE OF BAPI_LIMIT_C, "   
lt_i_texts  TYPE STANDARD TABLE OF BAPI_TEXT_I, "   
lt_i_bup  TYPE STANDARD TABLE OF BAPI_BUP_C, "   
lt_i_org  TYPE STANDARD TABLE OF BAPI_ORG_C. "   

  CALL FUNCTION 'BBP_EXTREQ_INBOUND'  "
    EXPORTING
         I_HEADER = lv_i_header
         I_HEADER_CUST = lv_i_header_cust
    IMPORTING
         E_HEADER = lv_e_header
    TABLES
         I_ITEMS = lt_i_items
         I_ATTACH = lt_i_attach
         RETURN = lt_return
         I_ADDON_FIELDS = lt_i_addon_fields
         I_ITEMS_CUST = lt_i_items_cust
         I_ACTION = lt_i_action
         I_ACC = lt_i_acc
         I_ACC_CUST = lt_i_acc_cust
         I_LIMIT = lt_i_limit
         I_TEXTS = lt_i_texts
         I_BUP = lt_i_bup
         I_ORG = lt_i_org
. " BBP_EXTREQ_INBOUND




ABAP code using 7.40 inline data declarations to call FM BBP_EXTREQ_INBOUND

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!