SAP EXIT_SAPLJKMC_001 Function Module for IS-M / MDIS: User Exit for Correction Order Header Data - OBSOLETE
EXIT_SAPLJKMC_001 is a standard exit sapljkmc 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M / MDIS: User Exit for Correction Order Header Data - OBSOLETE 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 sapljkmc 001 FM, simply by entering the name EXIT_SAPLJKMC_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJ-2
Program Name: SAPLXJ-2
Main Program: SAPLXJ-2
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLJKMC_001 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_SAPLJKMC_001'"IS-M / MDIS: User Exit for Correction Order Header Data - OBSOLETE.
EXPORTING
I_XMCJKAK = "All Fields from Document Header
I_CONTROL = "General Update Control
IMPORTING
E_XMCJKAKUSR = "User-Specific Data Determined
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISP_MC_STATISTICS_CORR_ORDER
ISP_MC_STATISTICS_C_O_LOGGING
ISP_MC_STATISTICS_C_O_UPD_DI
ISP_MC_STATISTICS_C_O_UPD_V1
ISP_MC_STATISTICS_C_O_UPD_V2
ISP_MC_STATISTICS_SALES_ORDER
ISP_MC_STATISTICS_S_O_LOGGING
ISP_MC_STATISTICS_S_O_UPD_DI
ISP_MC_STATISTICS_S_O_UPD_V1
ISP_MC_STATISTICS_S_O_UPD_V2
IMPORTING Parameters details for EXIT_SAPLJKMC_001
I_XMCJKAK - All Fields from Document Header
Data type: MCJKAKBOptional: No
Call by Reference: No ( called with pass by value option)
I_CONTROL - General Update Control
Data type: MCCONTROLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLJKMC_001
E_XMCJKAKUSR - User-Specific Data Determined
Data type: MCJKAKUSROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLJKMC_001 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: | ||||
| lv_i_xmcjkak | TYPE MCJKAKB, " | |||
| lv_e_xmcjkakusr | TYPE MCJKAKUSR, " | |||
| lv_i_control | TYPE MCCONTROL. " |
|   CALL FUNCTION 'EXIT_SAPLJKMC_001' "IS-M / MDIS: User Exit for Correction Order Header Data - OBSOLETE |
| EXPORTING | ||
| I_XMCJKAK | = lv_i_xmcjkak | |
| I_CONTROL | = lv_i_control | |
| IMPORTING | ||
| E_XMCJKAKUSR | = lv_e_xmcjkakusr | |
| . " EXIT_SAPLJKMC_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJKMC_001
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