Entering content frame!--a11y-->

Component documentation JIT Outbound 

Purpose

You use this component if you, as a system supplier of OEMs, receive and supply just-in-time calls inbound. You can use the JIT Outbound component to pass on received JIT calls inbound directly to your suppliers.

The processes and functions of the JIT Outbound component are very similar to those of the JIT Inbound component and were developed to complement this component.

JIT Inbound was developed around the requirements of the Automotive industry and supports the two following types of JIT call:

Forwarded sequenced JIT calls outbound

You, as system supplier, use the sequenced JIT calls outbound to call parts for a particular vehicle from your suppliers. The information for the relevant components from the inbound, sequenced JIT call is copied directly to the outbound, sequenced JIT call and is transferred to the suppliers. An example of an outbound, sequenced JIT call can be found

here.
Summarized JIT calls outbound

This summarized JIT call is either generated from the system’s automatic production supply or you can create it manually and transfer it to your suppliers.

 

JIT Outbound supports the business aims of the JIT process; for example it helps reduce lead times, optimize costs and avoids picking and storing in the process.

Implementation considerations

The way in which data is retained and managed in JIT Outbound allows you to deal with the usual large order volume in the Automotive industry.

The call structure and call control enables you to adjust JIT Outbound to suit your business process. The process is automated to a large extent.

The processing of JIT calls with Electronic Data Interchange (EDI) corresponds to the relevant norms and standards of VDA4916, EDIFACT, Odette and NC866.

 

Integration

  • You send JIT calls by EDI using an Intermediate Document (IDoc).
  • Depending on your business process, functions from other components are also used. These are either integrated or can be found via the Environment menu. This includes the following components:
  • Module

    Component (documentation)

    LO – Logistics - General

    LO – Material Master Data

    MM – Materials Management

    MM – Master Data (Vendor Master Records)

    MM – Scheduling Agreements

    MM – Source List (optional)

    MM – Logistics – Invoice Verification

    PP – Production Planning and Control

    PP – Control Cycles (Kanban)

    LE - Logistics Execution

    LE – Goods Receipt or Goods Receipt Automotive

    LE - Transport

     

    Features

    • A customer first sends you a JIT call inbound by EDI. From these received JIT calls, the system creates a three-level call structure for sequenced JIT calls. This structure consists of the call header, the components groups and the call components. You then directly convert the information in this call into an outbound JIT call which you send to your suppliers.
    • Using call control, you can reproduce your business process. The call control is based on actions which are either triggered by incoming JIT calls or manually online. An action changes the internal processing status of a call and can also trigger other functions.
    • You use JIT-monitoring to control the JIT calls internally. You can access this application either as a list or in the graphic JIT cockpit. With JIT-monitoring, you can monitor and control JIT calls by displaying detailed information, or by carrying out actions and special actions. You can also use batch processing to execute these actions.
    • The basic data and transaction data required for JIT Outbound has been kept to a minimum. This allows a high-performance processing of the usually large volume of quantities in a very small data base volume.
    • You can correct the status of a call manually in the case of technical or logistical problems.
    • Goods receipt posting is integrated in this component. You can carry out a backflush for several call components both aggregated and temporally separated from the process (separated backflush).
    • The creation of a delivery is also integrated in the JIT Outbound. You create a delivery when you create a summarized, outbound JIT call but only transfer the materials internally. You can group the call components from several delivery schedules into one delivery to create a transfer order which is used to transfer the materials.
    • You can send a delivery confirmation to your supplier. This delivery confirmation contains the production numbers of the supplier or of the OEM.
    • After you have completed the JIT calls, you can archive the JIT data and delete it from the database.
    • JIT Outbound is integrated in the Internet application Supplier Workplace. In this way you can provide a supplier with information about the materials to be delivered. By displaying JIT calls outbound in the Internet application, the supplier can find out about requirements at the OEM. The supplier has access to all relevant data, such as call component, delivery time, sequence and unloading point.
    •  

       

      Leaving content frame