SAP BBP_RFC_EXTREQU_UPDATE_IN Function Module for









BBP_RFC_EXTREQU_UPDATE_IN is a standard bbp rfc extrequ update in 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 rfc extrequ update in FM, simply by entering the name BBP_RFC_EXTREQU_UPDATE_IN into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_RFC_EXTREQU_UPDATE_IN 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_RFC_EXTREQU_UPDATE_IN'"
  EXPORTING
   IS_HEADER =  "
*  IT_BUP =  "
*  IT_ORGDATA =  "
*  IT_ATTACH =  "
*  IT_ADDON_FIELDS =  "
*  IS_HEADER_CUST =  "
*  IV_TRFC_CALL = ' ' "
   IT_ITEMS =  "
*  IT_ITEMS_CUST =  "
*  IT_ACC =  "
*  IT_ACC_CUST =  "
*  IT_LIMIT =  "
*  IT_TEXTS =  "

 IMPORTING
   ES_HEADER =  "
   ET_RETURN =  "
.



IMPORTING Parameters details for BBP_RFC_EXTREQU_UPDATE_IN

IS_HEADER -

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

IT_BUP -

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

IT_ORGDATA -

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

IT_ATTACH -

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

IT_ADDON_FIELDS -

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

IS_HEADER_CUST -

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

IV_TRFC_CALL -

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

IT_ITEMS -

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

IT_ITEMS_CUST -

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

IT_ACC -

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

IT_ACC_CUST -

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

IT_LIMIT -

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

IT_TEXTS -

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

EXPORTING Parameters details for BBP_RFC_EXTREQU_UPDATE_IN

ES_HEADER -

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

ET_RETURN -

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

Copy and paste ABAP code example for BBP_RFC_EXTREQU_UPDATE_IN 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_SC_HEADER_D, "   
lv_is_header  TYPE BBPS_EXTREQ_HEADER, "   
lv_it_bup  TYPE BAPIT_BUP_C, "   
lv_it_orgdata  TYPE BAPIT_ORG_C, "   
lv_it_attach  TYPE BAPIT_ATT_C, "   
lv_it_addon_fields  TYPE BBPT_IF_CUSTOMER_FIELDS_PI, "   
lv_et_return  TYPE BAPIRET2_T, "   
lv_is_header_cust  TYPE BAPI_SC_HEADER_CUST_C, "   
lv_iv_trfc_call  TYPE XFELD, "   SPACE
lv_it_items  TYPE BBPT_EXTREQ_ITEM, "   
lv_it_items_cust  TYPE BAPIT_SC_ITEM_CUST_C, "   
lv_it_acc  TYPE BAPIT_ACC, "   
lv_it_acc_cust  TYPE BAPIT_ACC_CUST_C, "   
lv_it_limit  TYPE BAPIT_LIMIT_C, "   
lv_it_texts  TYPE BAPIT_TEXT_I. "   

  CALL FUNCTION 'BBP_RFC_EXTREQU_UPDATE_IN'  "
    EXPORTING
         IS_HEADER = lv_is_header
         IT_BUP = lv_it_bup
         IT_ORGDATA = lv_it_orgdata
         IT_ATTACH = lv_it_attach
         IT_ADDON_FIELDS = lv_it_addon_fields
         IS_HEADER_CUST = lv_is_header_cust
         IV_TRFC_CALL = lv_iv_trfc_call
         IT_ITEMS = lv_it_items
         IT_ITEMS_CUST = lv_it_items_cust
         IT_ACC = lv_it_acc
         IT_ACC_CUST = lv_it_acc_cust
         IT_LIMIT = lv_it_limit
         IT_TEXTS = lv_it_texts
    IMPORTING
         ES_HEADER = lv_es_header
         ET_RETURN = lv_et_return
. " BBP_RFC_EXTREQU_UPDATE_IN




ABAP code using 7.40 inline data declarations to call FM BBP_RFC_EXTREQU_UPDATE_IN

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.

 
 
 
 
 
 
 
 
DATA(ld_iv_trfc_call) = ' '.
 
 
 
 
 
 
 


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!