Outbound sequenced JIT calls

Outbound sequenced JIT calls (JIT Outbound to Sub-Supplier) means you receive an inbound sequenced JIT call from your customer (in our case from the automotive conveyor’s SAP SCM).
Specifies that it is a matter of a JIT outbound call to a sub-supplier. The sequenced JIT call therefore refers to an inbound sequenced JIT call.
This JIT call may resemble the following diagram:

Call components from the inbound sequenced JIT call can be directly passed on to a sub-supplier in an outbound sequenced JIT call. The BOM components can also be passed on to your sub-supplier.
You must maintain a JIT control cycle for both types of call components. You also have to set the BOM explosion indicator in the JIT basic data for call components that have to be exploded.
A control cycle consists of a material, a plant and the supply area. The system determines the supply area in three steps.
You must define this control cycle specifically for a material and a plant.
The components in a components group must always have the same JIT call profile.


  1. Background task program in SCM creates seqjit-idocs from APO orders and transfers them to ERP (NB: into ERP JITM e.g.).
  2. Background task program in ERP carrying out JITM transaction with the action „Create outb.JC from inb.JC“ (creates outb.seq/sum.JCs from these inb.seqjits).
  3. Now we are applying as usual our actions („Create delivery“ etc) in JITOM to newly imported jito-calls.

EWM wiring

  1. Background task program in SCM creates seqjit-idocs from APO orders and transfers them to ERP (identical as Daimler way).
  2. In opposite to the Daimler process – EWM way missed the part with converting Inb.JIT to Outb.JITO.
  3. Now we are applying as usual our actions („Create delivery in EWM_PRD“ etc) in JITM to newly imported jit-calls.

S2L (APO planning results – in other words: requirements – are transferred into ERP purchasing schedule agreements)

  1. Setting up S2L with CIF-conditions.
  2. S2L creates outbound contol-cycle based sum.JITO-calls, depending on APO-demands from SCM via CIF.
  3. According to jit control profile in a control cycle, we’ree applying „Create TO“ (WMS), „Create EWM delivery“ or „Create ERP delivery“ actions.

SCM > ERP > Vendor

  1. Create a purchasing scheduling agreement 550000XXXX.
  2. Sending DELFOR forecasts to supplier from this agreement
  3. Create Control cycle with this MM SA.
  4. Background task program in SCM creates seqjit-idocs from APO orders and transfers them to ERP (NB: creating Z-action is an Interlinked Action – CREA + OCRE)
  5. No we have 2-linked calls (external jitcall number in JITM can be seen as „Key“ in JITOM). Table JITOIT has vendor number from related Control Cycle.
  6. Linked direction call can be viewed JITM-Goto-Outbound or JITOM-Goto-Header
  7. NACE condition PA > MAED depending on outbound JIT-call profile (not Call control) sends release to vendors on JC creating. This function can also be done through Z-action „Send order to vendor“ in JITOM. IDoc field E1PSJCL-GRPIN contains component group number.
  8. Depending on the method of creating JC – using S2L or JIT1 – the IDoc field E1KSJCL-ABTYP will contain „D“ (Summarized JIT Call) or „S“ (Sequenced JIT Call)
  9. Supplier sends a response ASN and create inbound delivery (calling FM JITOUT01_INSERT_PABASN / MABASN_UPDATE_RELATION_MAB_ASN will links the delivery to the component group in PABASN table), using seq. E1EDL24-KANNR as customer call number/key.
  10. Based on the link PABASN=InbDel, GR on inbound delivery will update status of linked JIT-call

Delivery confirmations for JIT Outbound can be seen in tables DLCNOCO and DLCNOHD

Schreibe einen Kommentar

All fields are required. Your email address will not be published.