SAP K_PLAN_INTEGRATION_ACTIVATE Function Module for

Search SAP Function Modules

K_PLAN_INTEGRATION_ACTIVATE is a standard k plan integration activate 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 k plan integration activate FM, simply by entering the name K_PLAN_INTEGRATION_ACTIVATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: KPU2
Program Name: SAPLKPU2
Main Program: SAPLKPU2
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_PLAN_INTEGRATION_ACTIVATE 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 'K_PLAN_INTEGRATION_ACTIVATE'"
  EXPORTING
   I_KOKRS =  "
   I_VERSN =  "
   I_GJAHR =  "
   I_CONTROL =  "
*  I_CDEF =  "
*  I_USE_COIOB_BUFFER = ' ' "
*  I_OBJNR_STOP =  "
*  I_SCAN = ' ' "

 IMPORTING
   E_RESULT =  "

TABLES
*  T_MESG =  "
*  T_OBJNR_DEBUGGING =  "
*  T_SCAN =  "

EXCEPTIONS
   VERSION_NOT_DEFINED = 1    VERSION_LOCKED = 2    INTEGRATION_ALREADY_ACTIVE = 3    VERSION_BEING_EDITED = 4    DATASET_BLOCKED = 5 

.

IMPORTING Parameters details for K_PLAN_INTEGRATION_ACTIVATE

I_KOKRS -

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

I_VERSN -

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

I_GJAHR -

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

I_CONTROL -

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

I_CDEF -

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

I_USE_COIOB_BUFFER -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OBJNR_STOP -

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

I_SCAN -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for K_PLAN_INTEGRATION_ACTIVATE

E_RESULT -

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

TABLES Parameters details for K_PLAN_INTEGRATION_ACTIVATE

T_MESG -

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

T_OBJNR_DEBUGGING -

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

T_SCAN -

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

EXCEPTIONS details

VERSION_NOT_DEFINED -

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

VERSION_LOCKED -

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

INTEGRATION_ALREADY_ACTIVE -

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

VERSION_BEING_EDITED -

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

DATASET_BLOCKED -

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

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

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