SAP EXIT_SAPLJK04_001 Function Module for Determination of Shipping Preparation Date as Earliest Possible Item Start
EXIT_SAPLJK04_001 is a standard exit sapljk04 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 Determination of Shipping Preparation Date as Earliest Possible Item Start 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 sapljk04 001 FM, simply by entering the name EXIT_SAPLJK04_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJK1
Program Name: SAPLXJK1
Main Program: SAPLXJK1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLJK04_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_SAPLJK04_001'"Determination of Shipping Preparation Date as Earliest Possible Item Start.
EXPORTING
VORLAUFDAT_IN = "Shipping Preparation Date
* IBEZIRK = ' ' "Carrier Route
IWERK = "Printing Works
IDRERZ = "Publication
IPVA = "Edition
ILIEFERART = "Delivery Type
IMPORTING
VORLAUFDAT_OUT = "Shipping Preparation Date
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISP_NEXT_POSIBLE_DIST_DATE_GET
ISP_NEXT_POSIBLE_PRSP_DATE_GET
IMPORTING Parameters details for EXIT_SAPLJK04_001
VORLAUFDAT_IN - Shipping Preparation Date
Data type: JKAPVB-VORLAUFDATOptional: No
Call by Reference: No ( called with pass by value option)
IBEZIRK - Carrier Route
Data type: JKPAZ-BEZIRKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IWERK - Printing Works
Data type: JKAP-DRUCKEREIOptional: No
Call by Reference: No ( called with pass by value option)
IDRERZ - Publication
Data type: JKAP-DRERZOptional: No
Call by Reference: No ( called with pass by value option)
IPVA - Edition
Data type: JKAP-PVAOptional: No
Call by Reference: No ( called with pass by value option)
ILIEFERART - Delivery Type
Data type: JKAP-LIEFERARTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLJK04_001
VORLAUFDAT_OUT - Shipping Preparation Date
Data type: JKAPVB-VORLAUFDATOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLJK04_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_vorlaufdat_in | TYPE JKAPVB-VORLAUFDAT, " | |||
| lv_vorlaufdat_out | TYPE JKAPVB-VORLAUFDAT, " | |||
| lv_ibezirk | TYPE JKPAZ-BEZIRK, " SPACE | |||
| lv_iwerk | TYPE JKAP-DRUCKEREI, " | |||
| lv_idrerz | TYPE JKAP-DRERZ, " | |||
| lv_ipva | TYPE JKAP-PVA, " | |||
| lv_ilieferart | TYPE JKAP-LIEFERART. " |
|   CALL FUNCTION 'EXIT_SAPLJK04_001' "Determination of Shipping Preparation Date as Earliest Possible Item Start |
| EXPORTING | ||
| VORLAUFDAT_IN | = lv_vorlaufdat_in | |
| IBEZIRK | = lv_ibezirk | |
| IWERK | = lv_iwerk | |
| IDRERZ | = lv_idrerz | |
| IPVA | = lv_ipva | |
| ILIEFERART | = lv_ilieferart | |
| IMPORTING | ||
| VORLAUFDAT_OUT | = lv_vorlaufdat_out | |
| . " EXIT_SAPLJK04_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJK04_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.| "SELECT single VORLAUFDAT FROM JKAPVB INTO @DATA(ld_vorlaufdat_in). | ||||
| "SELECT single VORLAUFDAT FROM JKAPVB INTO @DATA(ld_vorlaufdat_out). | ||||
| "SELECT single BEZIRK FROM JKPAZ INTO @DATA(ld_ibezirk). | ||||
| DATA(ld_ibezirk) | = ' '. | |||
| "SELECT single DRUCKEREI FROM JKAP INTO @DATA(ld_iwerk). | ||||
| "SELECT single DRERZ FROM JKAP INTO @DATA(ld_idrerz). | ||||
| "SELECT single PVA FROM JKAP INTO @DATA(ld_ipva). | ||||
| "SELECT single LIEFERART FROM JKAP INTO @DATA(ld_ilieferart). | ||||
Search for further information about these or an SAP related objects