SAP EXIT_SAPLKMA1_002 Function Module for Flow Logic PAI

Search SAP Function Modules

EXIT_SAPLKMA1_002 is a standard exit saplkma1 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Flow Logic PAI 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 exit saplkma1 002 FM, simply by entering the name EXIT_SAPLKMA1_002 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLKMA1_002 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 'EXIT_SAPLKMA1_002'"Flow Logic PAI
  EXPORTING
*  USER_CSKS_EX =  "Standard Fields of Master Record
*  USER_MODE =  "Mode: I=Insert; U=Update; S=Show; D=Delete

 IMPORTING
   USER_CSKS_CI =  "Customer-Specific Additional Fields
   USER_DATA_CHANGED =  "Flag: Additional Fields Were Changed
   USER_FIELD_F2 =  "Cursor Position for Evaluation: Double-Click

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
K_COSTCENTERS_CHANGE_MANAGEMNT
K_COSTCENTERS_DB_UPDATE
K_COSTCENTERS_DELETE
K_COSTCENTER_CHANGE Change Cost Center
K_COSTCENTER_CHANGE_DB_UPDATE
K_COSTCENTER_CHANGE_HIERARCHY
K_COSTCENTER_CHANGE_TEXT
K_COSTCENTER_CREATE Create Cost Center
K_COSTCENTER_CREATE_DB_UPDATE
K_COSTCENTER_DELETE_DB_UPDATE Delete Cost Center
K_COSTCENTER_REFRESH_BUFFERS
K_COSTCENTER_SHOW Display Cost Center
K_COSTCTR_BAPI_ACTMULTIPLE Activate Inactive Cost Centers
K_COSTCTR_BAPI_CHANGEMULTIPLE
K_COSTCTR_BAPI_CHECKMULTIPLE
K_COSTCTR_BAPI_CREATEMULTIPLE
K_COSTCTR_BAPI_DELETEMULTIPLE Delete One or More Cost Centers
K_COSTCTR_BAPI_GETDETAIL
K_COSTCTR_BAPI_GETLIST
K_COSTCTR_MODIFY_EVENT_CNTN
K_EO_CCTR_APPL_CREATE
K_EO_CCTR_BUF_CHANGE_RELATION
K_EO_CCTR_BUF_DEQUEUE
K_EO_CCTR_BUF_ENQUEUE
K_EO_CCTR_BUF_INITIALIZE
K_EO_CCTR_BUF_INVALIDATE
K_EO_CCTR_BUF_SAVE_TO_DB
K_EO_CCTR_COLPROC_CHANGE
K_EO_CCTR_DETSCR_CHANGE_DATE
K_EO_CCTR_DETSCR_CHANGE_MODE
K_EO_CCTR_DETSCR_CHANGE_OBJ
K_EO_CCTR_DETSCR_CREATE
K_EO_CCTR_DETSCR_DESTROY
K_EO_CCTR_DETSCR_EXIT_CMD
K_EO_CCTR_DETSCR_REFRESH
K_EO_CCTR_INACTIVE_EXISTS
K_EO_CCTR_INDPROC_CHANGE
K_EO_CCTR_INDPROC_CREATE
K_EO_CCTR_SELECT_SINGLE
K_KOSTL_SETTLE_RULE_SHOW
K_KOSTL_WHERE_USED_SHOW
K_KOSTL_WHERE_USED_TABLE_SHOW

IMPORTING Parameters details for EXIT_SAPLKMA1_002

USER_CSKS_EX - Standard Fields of Master Record

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

USER_MODE - Mode: I=Insert; U=Update; S=Show; D=Delete

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

EXPORTING Parameters details for EXIT_SAPLKMA1_002

USER_CSKS_CI - Customer-Specific Additional Fields

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

USER_DATA_CHANGED - Flag: Additional Fields Were Changed

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

USER_FIELD_F2 - Cursor Position for Evaluation: Double-Click

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

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

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