SAP BAPI_KANBANCC_CHANGE Function Module for BAPI: Change Control Cycle

Search SAP Function Modules

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

Function Group: MPKV
Program Name: SAPLMPKV
Main Program: SAPLMPKV
Appliation area:
Release date: 13-Jan-2010
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_KANBANCC_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_KANBANCC_CHANGE'"BAPI: Change Control Cycle
  EXPORTING
*  TESTRUN =  "Switch to Simulation Mode for Write BAPIs
*  CONTROLCYCLE_NUMBER =  "Control Cycle No.
*  MATERIAL =  "Material Number
*  PLANT =  "Plant
*  SUPPLYAREA =  "Production Supply Area
   CONTROL_CYCLE_CHANGE =  "Change in Control Cycle (BAPI)
   CONTROL_CYCLE_CHANGEX =  "Transfer Structure for Change in Control Cycle (BAPI)
*  MATERIAL_EVG =  "BAPI Structure for Transfer of External Material No, Ver.,

TABLES
   RETURN =  "Return Parameter(s)
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
*  EXTENSIONOUT =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
*  CONTROLCYCLE_IN_TRIGGER_GROUP =  "BAPI: Control Cycle

.

IMPORTING Parameters details for BAPI_KANBANCC_CHANGE

TESTRUN - Switch to Simulation Mode for Write BAPIs

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

CONTROLCYCLE_NUMBER - Control Cycle No.

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

MATERIAL - Material Number

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

PLANT - Plant

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

SUPPLYAREA - Production Supply Area

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

CONTROL_CYCLE_CHANGE - Change in Control Cycle (BAPI)

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

CONTROL_CYCLE_CHANGEX - Transfer Structure for Change in Control Cycle (BAPI)

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

MATERIAL_EVG - BAPI Structure for Transfer of External Material No, Ver.,

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

TABLES Parameters details for BAPI_KANBANCC_CHANGE

RETURN - Return Parameter(s)

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

EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

CONTROLCYCLE_IN_TRIGGER_GROUP - BAPI: Control Cycle

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

Copy and paste ABAP code example for BAPI_KANBANCC_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.

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