SAP BAPI_BUPA_BC_CHANGE Function Module for Change Account Buying Center
BAPI_BUPA_BC_CHANGE is a standard bapi bupa bc change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Account Buying Center processing and below is the pattern details for this FM, 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 bapi bupa bc change FM, simply by entering the name BAPI_BUPA_BC_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_BUPA_BC_BAPI
Program Name: SAPLCRM_BUPA_BC_BAPI
Main Program: SAPLCRM_BUPA_BC_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_BUPA_BC_CHANGE 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 'BAPI_BUPA_BC_CHANGE'"Change Account Buying Center.
EXPORTING
IS_KEY = "Account Buying Center Key Structure (BAPI)
IS_DATA = "Account Buying Center Data Structure (BAPI)
IS_DATAX = "Account Buying Center Update Structure (BAPI)
TABLES
RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_BUPA_BC_CHANGE
IS_KEY - Account Buying Center Key Structure (BAPI)
Data type: BAPIBUS1006BC_KEYOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATA - Account Buying Center Data Structure (BAPI)
Data type: BAPIBUS1006BC_DATAOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATAX - Account Buying Center Update Structure (BAPI)
Data type: BAPIBUS1006BC_DATAXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BUPA_BC_CHANGE
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_BUPA_BC_CHANGE 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_is_key | TYPE BAPIBUS1006BC_KEY, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_is_data | TYPE BAPIBUS1006BC_DATA, " | |||
| lv_is_datax | TYPE BAPIBUS1006BC_DATAX. " |
|   CALL FUNCTION 'BAPI_BUPA_BC_CHANGE' "Change Account Buying Center |
| EXPORTING | ||
| IS_KEY | = lv_is_key | |
| IS_DATA | = lv_is_data | |
| IS_DATAX | = lv_is_datax | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_BUPA_BC_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_BUPA_BC_CHANGE
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