SAP BAPI_BUPA_BBP0020_CHANGE Function Module for Change Bidder Characteristic









BAPI_BUPA_BBP0020_CHANGE is a standard bapi bupa bbp0020 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 Bidder Characteristic 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 bbp0020 change FM, simply by entering the name BAPI_BUPA_BBP0020_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_BUPA_BBP0020_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_BBP0020_CHANGE'"Change Bidder Characteristic
EXPORTING
BUSINESSPARTNER = "Business Partner Number
IV_CHARACTERISTIC = "General Bidder Characteristic
IV_VALID_TO_OLD = "Valid-To Date
IV_VALID_TO_NEW = "Valid-To Date
IV_VALID_FROM_NEW = "Valid From

TABLES
RETURN = "Return Parameter
.



IMPORTING Parameters details for BAPI_BUPA_BBP0020_CHANGE

BUSINESSPARTNER - Business Partner Number

Data type: BAPIBUS1006_HEAD-BPARTNER
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CHARACTERISTIC - General Bidder Characteristic

Data type: BAPIBUS1006220_CHARACTERISTIC-CHARACTERISTIC
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALID_TO_OLD - Valid-To Date

Data type: BAPIBUS1006220_CHARACTERISTIC-VALID_TO
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALID_TO_NEW - Valid-To Date

Data type: BAPIBUS1006220_CHARACTERISTIC-VALID_TO
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALID_FROM_NEW - Valid From

Data type: BAPIBUS1006220_CHARACTERISTIC-VALID_FROM
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_BUPA_BBP0020_CHANGE

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_BUPA_BBP0020_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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_businesspartner  TYPE BAPIBUS1006_HEAD-BPARTNER, "   
lv_iv_characteristic  TYPE BAPIBUS1006220_CHARACTERISTIC-CHARACTERISTIC, "   
lv_iv_valid_to_old  TYPE BAPIBUS1006220_CHARACTERISTIC-VALID_TO, "   
lv_iv_valid_to_new  TYPE BAPIBUS1006220_CHARACTERISTIC-VALID_TO, "   
lv_iv_valid_from_new  TYPE BAPIBUS1006220_CHARACTERISTIC-VALID_FROM. "   

  CALL FUNCTION 'BAPI_BUPA_BBP0020_CHANGE'  "Change Bidder Characteristic
    EXPORTING
         BUSINESSPARTNER = lv_businesspartner
         IV_CHARACTERISTIC = lv_iv_characteristic
         IV_VALID_TO_OLD = lv_iv_valid_to_old
         IV_VALID_TO_NEW = lv_iv_valid_to_new
         IV_VALID_FROM_NEW = lv_iv_valid_from_new
    TABLES
         RETURN = lt_return
. " BAPI_BUPA_BBP0020_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_BUPA_BBP0020_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.

 
"SELECT single BPARTNER FROM BAPIBUS1006_HEAD INTO @DATA(ld_businesspartner).
 
"SELECT single CHARACTERISTIC FROM BAPIBUS1006220_CHARACTERISTIC INTO @DATA(ld_iv_characteristic).
 
"SELECT single VALID_TO FROM BAPIBUS1006220_CHARACTERISTIC INTO @DATA(ld_iv_valid_to_old).
 
"SELECT single VALID_TO FROM BAPIBUS1006220_CHARACTERISTIC INTO @DATA(ld_iv_valid_to_new).
 
"SELECT single VALID_FROM FROM BAPIBUS1006220_CHARACTERISTIC INTO @DATA(ld_iv_valid_from_new).
 


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!