SAP BBP_BACKENDS_UPDATE Function Module for









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

Function Group: BBP_BUPA_VR
Program Name: SAPLBBP_BUPA_VR
Main Program: SAPLBBP_BUPA_VR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BBP_BACKENDS_UPDATE 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_BACKENDS_UPDATE'"
  EXPORTING
*  NUMBER_OF_VENDORS =  "
*  KRAUS_TO_DUNS = ' ' "
*  NUMBER_OF_CREDITORS =  "
   REMOTE_SYSTEM =  "
   REMOTE_RELEASE =  "
   REMOTE_CLIENT =  "
   LOG_SYS =  "
*  WO_PURCH_ORG =  "
*  LOCAL_PURCH_ORG =  "
*  DEF_CURRENCY =  "

TABLES
*  EXT_ID_LIST =  "
*  EXT_CRED_LIST =  "
*  PURCHORG_LIST =  "
.



IMPORTING Parameters details for BBP_BACKENDS_UPDATE

NUMBER_OF_VENDORS -

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

KRAUS_TO_DUNS -

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

NUMBER_OF_CREDITORS -

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

REMOTE_SYSTEM -

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

REMOTE_RELEASE -

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

REMOTE_CLIENT -

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

LOG_SYS -

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

WO_PURCH_ORG -

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

LOCAL_PURCH_ORG -

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

DEF_CURRENCY -

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

TABLES Parameters details for BBP_BACKENDS_UPDATE

EXT_ID_LIST -

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

EXT_CRED_LIST -

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

PURCHORG_LIST -

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

Copy and paste ABAP code example for BBP_BACKENDS_UPDATE 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_ext_id_list  TYPE STANDARD TABLE OF BBP_LFA1_KEY, "   
lv_number_of_vendors  TYPE INT4, "   
lv_kraus_to_duns  TYPE XFELD, "   SPACE
lt_ext_cred_list  TYPE STANDARD TABLE OF BBP_LFA1_KEY, "   
lv_number_of_creditors  TYPE INT4, "   
lt_purchorg_list  TYPE STANDARD TABLE OF BBP_LFM1_KEY2, "   
lv_remote_system  TYPE RFCDEST, "   
lv_remote_release  TYPE SYSAPRL, "   
lv_remote_client  TYPE SYMANDT, "   
lv_log_sys  TYPE LOGSYS, "   
lv_wo_purch_org  TYPE XFELD, "   
lv_local_purch_org  TYPE OBJEKTID, "   
lv_def_currency  TYPE WAERS. "   

  CALL FUNCTION 'BBP_BACKENDS_UPDATE'  "
    EXPORTING
         NUMBER_OF_VENDORS = lv_number_of_vendors
         KRAUS_TO_DUNS = lv_kraus_to_duns
         NUMBER_OF_CREDITORS = lv_number_of_creditors
         REMOTE_SYSTEM = lv_remote_system
         REMOTE_RELEASE = lv_remote_release
         REMOTE_CLIENT = lv_remote_client
         LOG_SYS = lv_log_sys
         WO_PURCH_ORG = lv_wo_purch_org
         LOCAL_PURCH_ORG = lv_local_purch_org
         DEF_CURRENCY = lv_def_currency
    TABLES
         EXT_ID_LIST = lt_ext_id_list
         EXT_CRED_LIST = lt_ext_cred_list
         PURCHORG_LIST = lt_purchorg_list
. " BBP_BACKENDS_UPDATE




ABAP code using 7.40 inline data declarations to call FM BBP_BACKENDS_UPDATE

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_kraus_to_duns) = ' '.
 
 
 
 
 
 
 
 
 
 
 


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!