SAP BBP_VENDOR_CHANGE_REMOTE Function Module for









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

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



Function BBP_VENDOR_CHANGE_REMOTE 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_VENDOR_CHANGE_REMOTE'"
  EXPORTING
   IV_BUPA_NO =  "
   IS_ADDRESS =  "
   IS_CENTRAL_ORGAN =  "
*  IS_BIDDER_STATUS =  "

 IMPORTING
   EV_PARTNER =  "

TABLES
   CT_TELEPHONE =  "
*  CT_FAX =  "
   CT_EMAIL =  "
*  CT_FTP_HTTP =  "
*  CT_PURCH_DATA =  "
*  CT_PCARD_INSTITUTES =  "
*  CT_BACKEND_MAPPING =  "
*  CT_BIDDER_QM_SYSTEMS =  "
*  ET_RETURN =  "
.



IMPORTING Parameters details for BBP_VENDOR_CHANGE_REMOTE

IV_BUPA_NO -

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

IS_ADDRESS -

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

IS_CENTRAL_ORGAN -

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

IS_BIDDER_STATUS -

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

EXPORTING Parameters details for BBP_VENDOR_CHANGE_REMOTE

EV_PARTNER -

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

TABLES Parameters details for BBP_VENDOR_CHANGE_REMOTE

CT_TELEPHONE -

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

CT_FAX -

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

CT_EMAIL -

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

CT_FTP_HTTP -

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

CT_PURCH_DATA -

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

CT_PCARD_INSTITUTES -

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

CT_BACKEND_MAPPING -

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

CT_BIDDER_QM_SYSTEMS -

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

ET_RETURN -

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

Copy and paste ABAP code example for BBP_VENDOR_CHANGE_REMOTE 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_ev_partner  TYPE BU_PARTNER, "   
lv_iv_bupa_no  TYPE BU_PARTNER, "   
lt_ct_telephone  TYPE STANDARD TABLE OF BAPIADTEL, "   
lt_ct_fax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_is_address  TYPE BBP_BUPA_ADDRESS_ORGAN, "   
lt_ct_email  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_central_organ  TYPE BBP_BUPA_CENTRAL_ORGAN, "   
lt_ct_ftp_http  TYPE STANDARD TABLE OF BAPIADURI, "   
lv_is_bidder_status  TYPE BBP_BID000, "   
lt_ct_purch_data  TYPE STANDARD TABLE OF BBP_BUPA_PURCH, "   
lt_ct_pcard_institutes  TYPE STANDARD TABLE OF BBP_VENPC, "   
lt_ct_backend_mapping  TYPE STANDARD TABLE OF BBP_VENMAP, "   
lt_ct_bidder_qm_systems  TYPE STANDARD TABLE OF BBP_BIDQMS, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BBP_VENDOR_CHANGE_REMOTE'  "
    EXPORTING
         IV_BUPA_NO = lv_iv_bupa_no
         IS_ADDRESS = lv_is_address
         IS_CENTRAL_ORGAN = lv_is_central_organ
         IS_BIDDER_STATUS = lv_is_bidder_status
    IMPORTING
         EV_PARTNER = lv_ev_partner
    TABLES
         CT_TELEPHONE = lt_ct_telephone
         CT_FAX = lt_ct_fax
         CT_EMAIL = lt_ct_email
         CT_FTP_HTTP = lt_ct_ftp_http
         CT_PURCH_DATA = lt_ct_purch_data
         CT_PCARD_INSTITUTES = lt_ct_pcard_institutes
         CT_BACKEND_MAPPING = lt_ct_backend_mapping
         CT_BIDDER_QM_SYSTEMS = lt_ct_bidder_qm_systems
         ET_RETURN = lt_et_return
. " BBP_VENDOR_CHANGE_REMOTE




ABAP code using 7.40 inline data declarations to call FM BBP_VENDOR_CHANGE_REMOTE

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!