JIT call ( Call structure, IDoc type )

  • Call structure
  • JIT call types
    • Call for assembly
    • Call for discrete materials 
    • Summarized JIT calls (pick up sheets)
    • Summarized Range Call 
    • Internal Calls (Buffer Storage Location) 
  • SEQJIT structure

Call structure

Three levels

  1. Call header ( Identification: JIT customer, external call number + sequence number )
  2. The components groups represent the material, or the assembly ( Control: Unloading point, Time of requirements, CGM )
  3. The call components are the materials that the JIT customer transmits to you in a JIT call. A call component contains a reference to the scheduling agreement item in a JIT scheduling agreement.

JIT call types

  • Calls for assemblies: The JIT customer transmits all call components for a vehicle. This is a departure from an order-related BOM.
    • Example: The customer transmits the components of four-door modules with one call. The system carries out a components group material determination and then the components group determination. It assigns each call component to a door module. The system uses the components groups for the internal control of the calls
  • Calls for discrete materials and summarized JIT calls: The JIT customer transmits discrete material numbers, that represent fully developed assemblies, modules, or systems. A BOM must exist in your system for the material.
    • Individual materials: 
      • The JIT customer transmits one or more quantities and dates for a call component in one call
      • Seq.: JIT customer transmits discrete materials, that represent fully developed assemblies or modules.
        • A material master record and a BOM in the system for all variants that the JIT customer calls.
        • Example: With one call, the customer transmits four call components, each representing a fully developed door module. The system carries out the components group determination and assigns exactly one call component to a components group.
    • Several materials (pick up sheet): The JIT customer transmits several materials for one call number and date in one call. The system saves each material as a call component and saves the reference number as an external number.
    • Ranges of production numbers: In a call, the JIT customer transmits a range of production numbers – a summarized range call – which is split into several identical calls.

Summarized Range Call 

The delivery date is the same for each individual call. Use this type of summarized JIT call if you want to avoid a series of identical calls. Instead, you can specify a range of production numbers. This range is then split into x calls each for the same quantity.

Internal Calls (Buffer Storage Location) 

Use this process when processing sequenced JIT calls

Produce component groups with internal calls and store them temporarily in a temporary storage location.  This means that if delivery problems occur for a concrete customer call, you can switch the components groups of the internal call with the components groups of the sequenced JIT call.

In this way, you can stop problems in production and increase your service level. On the other hand, you increase your warehouse stock and produce at your own risk.
  • You have created a Control profile for internal calls in Customizing for JIT Inbound.
  • The call type internal call corresponds to a sequenced JIT call with a fictitious external call number. 
  • The call components of an internal call refer to a scheduling agreement. 
  • You must therefore define special components group types for internal calls in the basic data for customers you want to create internal calls for. You assign a Control profile for internal calls to the components group types.
  • In Customizing in the call control you have defined a suitable action status network for the components group types of the internal calls and of the relevant sequenced JIT calls.
  • You have defined and assigned a components group material for the relevant components group types. You have created a production version for the components group. You have entered a receiving storage location in the production version of the internal call and in that of the sequenced JIT call.

SEQJIT structure

  • E1KSJCL : IDOC: Header Data JIT Calls (SeqJC, SumJC)   
    • 1.PARTN : Partner number 
    • 2.LIFNR : Vendor number at customer location 
    • 3.KNREF : Customer description of partner (plant, storage location) 
    • 4.PRODN : External Call Number 
    • 5.SEQNR : External Sequence Number 
    • 9.ABLAD : Unloading Point 
    • 10.FLDPO : Assembly location of parts group at customer site 
    • 13.EXSTI : Transmitted External Status Information 
    • 18.CHNGSEQ : Change sequence 
    • 19.REFNR : Reference Number of JIT Call 
    • 21.PDATUM : Planned Shipping Date 
    • 24.RDATUM : Planned Requirements Date 
    • 23.ABTYP : Call Type 
    • E1EDKR1 : Additional Reference Numbers / Texts for JIT Call Header 
    • E1EDK11 : IDoc: Header texts suppliers 
    • E1PSJCL : IDOC: Item Data JIT Calls (SeqJC, SumJC) 
      • 1.KDMAT : Material belonging to the customer 
      • 2.IDNLF : Material Number Used by Vendor 
      • 3.LIUMF : Components Groups Material (Delivery Scope) 
      • 5.VMENG : Call Quantity in Sales Unit of Measure 
      • 6.VRKME : Sales unit 
      • 7.ABLAD : Unloading Point 
      • 8.FLDPO : Assembly location of parts group at customer site 
      • 9.EDATUM : Date of External Status 
      • 13.PDATUM : Planned Shipping Date 
      • 15.RDATUM : Planned Requirements Date 
      • 17.GRPIN : Grouping and Sequencing Information Components Group 
      • E1EDL12 : IDOC: Configuration 
      • E1EDPR1 : Additional Reference Numbers / Texts for JIT Call Item 
      • E1EDPT3 : IDOC: Item Texts Supplier     
Comments:
  • das SEQJIT-IDOC mit dem Vorgangscode SJCL und dem Funktionsbaustein IDOC_INPUT_SEQJIT verarbeitet. Die Ermittlung fndet in der Verarbeitung über Funktionsbaustein JIT06_SEARCH_KUNNR statt. Dieser liest die Tabelle T661W oder besser bekannt als Transaktion OVAI aus
  • Die Transaktion OVA9 spielt bei der Erzeugung und Bearbeitung  von JIT-Abrufen keine Rolle und ist lediglich für die Verarbeitung von Liefer- bzw.  Feinabrufen relevant.






 


Comments