SAP JIT03_VL10_PACKAGES_CREATE Function Module for NOTRANSL: MAB: Unterteilen Liefervorrat in minimale JIT-Päckchen
JIT03_VL10_PACKAGES_CREATE is a standard jit03 vl10 packages create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: MAB: Unterteilen Liefervorrat in minimale JIT-Päckchen 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 jit03 vl10 packages create FM, simply by entering the name JIT03_VL10_PACKAGES_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JIT03
Program Name: SAPLJIT03
Main Program: SAPLJIT03
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JIT03_VL10_PACKAGES_CREATE 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 'JIT03_VL10_PACKAGES_CREATE'"NOTRANSL: MAB: Unterteilen Liefervorrat in minimale JIT-Päckchen.
EXPORTING
* MAX_LINES_IV = 0 "
CHANGING
PACKAGE_CT = "Table with Packets of Items (Order Combination)
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJIT03_001 JIT: Sorting Header and Item Data
EXIT_SAPLJIT03_002 JIT: Defining Handling Units (Delivery)
EXIT_SAPLJIT03_003 JIT: Printing the Component List using Action Call
EXIT_SAPLJIT03_004 JIT: Print Picking List using Action Call
EXIT_SAPLJIT03_005 JIT: Delivery Scheduling
EXIT_SAPLJIT03_006 JIT: Check-Digit Determination
EXIT_SAPLJIT03_007 JIT: Components Group Material Determination
EXIT_SAPLJIT03_008 JIT: Carry Out Material Movements
EXIT_SAPLJIT03_009 JIT: Modification of Backflush Data
EXIT_SAPLJIT03_011 Exit for Inbound Processing Summarized JIT Call
EXIT_SAPLJIT03_012 JIT: Customer Exit for Replacement Logic Summarized JIT Call Inbound
EXIT_SAPLJIT03_013 SumJC: Set Control Parameters for EXIDV2 in HU
EXIT_SAPLJIT03_014 JIT: Modify Print Data for Transfer to Spool
EXIT_SAPLJIT03_015 JIT: Adjusting Data when Creating Delivery
IMPORTING Parameters details for JIT03_VL10_PACKAGES_CREATE
MAX_LINES_IV -
Data type: IOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for JIT03_VL10_PACKAGES_CREATE
PACKAGE_CT - Table with Packets of Items (Order Combination)
Data type: SHP_VL10_PACKAGE_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JIT03_VL10_PACKAGES_CREATE 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_package_ct | TYPE SHP_VL10_PACKAGE_T, " | |||
| lv_max_lines_iv | TYPE I. " 0 |
|   CALL FUNCTION 'JIT03_VL10_PACKAGES_CREATE' "NOTRANSL: MAB: Unterteilen Liefervorrat in minimale JIT-Päckchen |
| EXPORTING | ||
| MAX_LINES_IV | = lv_max_lines_iv | |
| CHANGING | ||
| PACKAGE_CT | = lv_package_ct | |
| . " JIT03_VL10_PACKAGES_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM JIT03_VL10_PACKAGES_CREATE
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