SAP BAPI_BUS2165_CHANGE Function Module for BAPI Control Plan Version: Change









BAPI_BUS2165_CHANGE is a standard bapi bus2165 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 BAPI Control Plan Version: Change 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 bus2165 change FM, simply by entering the name BAPI_BUS2165_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DPR_BUS2165
Program Name: SAPLDPR_BUS2165
Main Program: SAPLDPR_BUS2165
Appliation area:
Release date: 02-Nov-2006
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_BUS2165_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_BUS2165_CHANGE'"BAPI Control Plan Version: Change
  EXPORTING
   CTRLPLAN_VERSION_GUID =  "GUID for Control Plan Version in BAPI Interface
*  IS_CTRLPLAN_H =  "BAPI CREATE/CHANGE: Flat Structure for Project Fields
*  IS_CTRLPLAN_H_UPD =  "BAPI CREATE/CHANGE: Mapping Structure for Project Fields
   IS_CTRLPLAN_V =  "BAPI CREATE/CHANGE: Fields of Control Plan Version
   IS_CTRLPLAN_V_UPD =  "BAPI CREATE/CHANGE: Update Structure for Control Plan Version
*  IS_EXTENSION_V_IN =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

 IMPORTING
   ES_EXTENSION_V_OUT =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

TABLES
*  RETURN =  "Return Parameter Table
.



IMPORTING Parameters details for BAPI_BUS2165_CHANGE

CTRLPLAN_VERSION_GUID - GUID for Control Plan Version in BAPI Interface

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

IS_CTRLPLAN_H - BAPI CREATE/CHANGE: Flat Structure for Project Fields

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

IS_CTRLPLAN_H_UPD - BAPI CREATE/CHANGE: Mapping Structure for Project Fields

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

IS_CTRLPLAN_V - BAPI CREATE/CHANGE: Fields of Control Plan Version

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

IS_CTRLPLAN_V_UPD - BAPI CREATE/CHANGE: Update Structure for Control Plan Version

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

IS_EXTENSION_V_IN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

EXPORTING Parameters details for BAPI_BUS2165_CHANGE

ES_EXTENSION_V_OUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

TABLES Parameters details for BAPI_BUS2165_CHANGE

RETURN - Return Parameter Table

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

Copy and paste ABAP code example for BAPI_BUS2165_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_es_extension_v_out  TYPE BAPIPAREX, "   
lv_ctrlplan_version_guid  TYPE BAPI_TS_GUID-CTRLPLAN_VERSION_GUID, "   
lv_is_ctrlplan_h  TYPE BAPI_TS_CTRLPLAN_H, "   
lv_is_ctrlplan_h_upd  TYPE BAPI_TS_CTRLPLAN_H_UPD, "   
lv_is_ctrlplan_v  TYPE BAPI_TS_CTRLPLAN_V, "   
lv_is_ctrlplan_v_upd  TYPE BAPI_TS_CTRLPLAN_V_UPD, "   
lv_is_extension_v_in  TYPE BAPIPAREX. "   

  CALL FUNCTION 'BAPI_BUS2165_CHANGE'  "BAPI Control Plan Version: Change
    EXPORTING
         CTRLPLAN_VERSION_GUID = lv_ctrlplan_version_guid
         IS_CTRLPLAN_H = lv_is_ctrlplan_h
         IS_CTRLPLAN_H_UPD = lv_is_ctrlplan_h_upd
         IS_CTRLPLAN_V = lv_is_ctrlplan_v
         IS_CTRLPLAN_V_UPD = lv_is_ctrlplan_v_upd
         IS_EXTENSION_V_IN = lv_is_extension_v_in
    IMPORTING
         ES_EXTENSION_V_OUT = lv_es_extension_v_out
    TABLES
         RETURN = lt_return
. " BAPI_BUS2165_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_BUS2165_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 CTRLPLAN_VERSION_GUID FROM BAPI_TS_GUID INTO @DATA(ld_ctrlplan_version_guid).
 
 
 
 
 
 


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!