The JIT inbound functions of the JIT component in SAP ERP or SAP S/4HANA process JIS calls (production synchronous calls) such as those received per VDA 4986 or ANSI X.12 866. Although the SAP standard offers basic functions for Just-in-Sequence (JIS) processing, it has numerous gaps in the mapping of process peculiarities and OEM specifics that require costly additional project-specific programming.
The remedy here is the SPEEDI JIS solution, which integrates seamlessly into the JIT call-off control of the SAP JIT component (SAP JIT) and enhances it with numerous practical functionalities and solution modules without modification. Through smart configuration, SPEEDI JIS can be flexibly adapted to automotive OEM JIS processes or to individual JIS requirements, ideally without any programming at all. There are also standardized SPEEDI add-on modulesfor certain OEM specifics.
A special feature of SPEEDI JIS is the JIT area (OEM projects, component project, plant or hall or production line), which forms the organizational bracket and the central unit for controlling the JIS processes. For each JIT area, for example, the individual packaging levels are then defined (container, pallet, truck).
Special SPEEDIplug-ins are used to incorporate incoming JIS calls into SAP JIT. The determination and assignment of the SEQJIT IDocs to the respective JIT area, which is linked to the JIT customer in SAP JIT via business logic, as well as the checking and creation of the sequence call-off (preview call-off) is carried out via the corresponding SPEEDIJIS functions (routines). The latter, and thus the internal processing of the retrieval data, is the first of a whole series of JIT actions. To stop the incorporation of IDocs, to implement codes or to notify users, for example about the completion of a JIT action, general SPEEDIfunctions can be used for this purpose.
SPEEDI JIS considers the complete packing hierarchy
The fact that SPEEDI JIS takes into account the complete packing hierarchy at up to ten levels for each JIS project, from the components in the containers all the way up to the loading of pallets on the truck, proves to be an invaluable advantage. In this way, all loading sequences can be precisely mapped and the desired components can be produced, picked and loaded in the correct sequence. Each packing level can be assigned several packing rows, which determine the order of processing and whose structure, i.e. sequencing in containers, on pallets or the truck, is defined by loading rules.
The SPEEDIsolution also allows the configuration of split profiles that divide the JIS call-offs for the delivery system. Based on the split profile, a JIS action such as "Plan load carrier" automatically detects when a container is full and to start loading the next container. SPEEDI JIS also supports the creation and the deletion of SD transports.
SPEEDI JIS reports with numerous selection criteria
With the central SPEEDI JIS Monitoring, which supplements the SAP standard JIT Monitoring (JITM) with a whole range of additional selection options and integrates seamlessly into the SAP JIT application, the processing of JIS calls-offs can be conveniently controlled and seamlessly monitored.
With another SPEEDI, JIS report, JIT actions can be executed, optionally also on the basis of packaging units. This report offers significantly more setting and selection options than the SAP JIT Progress Entry (JITF), for example with regard to JIT area, sort variant, processing logic and processing mode, call-off data, packing level or requirement or dispatch time.
Strict adherence to the sequence order for each individual packaging level or pack row is ensured by configurable scan processes integrated into the JIT action control. When the containers are filled and the truck loaded, a scan dialog is used to compare the data with the previously defined packaging logic.
Would you like to learn more about the solution SPEEDI JIS ? We look forward to advising you. Please feel free to call or e-mail us.