Sequenced JIT calls (seqJC)

Summarized JIT calls (sumJC):

You receive JIT calls by Electronic Data Interchange (EDI) using an Interchange Document (IDoc) created specially for this purpose.

JIT Inbound is integrated in the scheduling agreement processing in the SAP System. Depending on your business process, the functions of additional components can be used. These are either integrated, or can be reached in the menu under Environment . This includes the following components:

JIT Inbound is integrated in the scheduling agreement processing in the SAP System. First of all, a customer sends you forecast delivery schedules or JIT delivery schedules which you use to plan your material requirements. The actual JIT process then begins with a forecast signal, for example. This creates and tests a sequenced JIT call (seqJC) in your system.

The system creates a three-level call structure for each JIT call, which is received by Electronic Data Interchange (EDI). This structure consists of the call header, the components groups and the call components. This three-level structure allows you to reproduce sequenced JIT calls for assemblies, sequenced JIT calls for discrete materials and summarized JIT calls.

Using call control, you can reproduce your business process. The call control is based on actions which are either triggered by incoming calls or manually online. An action changes the internal processing status of a call and can also trigger other functions.

You control and monitor calls internally with the progress confirmation or with JIT-monitoring. You can access both applications either as a list or in the graphic JIT cockpit.

The progress confirmation allows you to manually trigger an action aggregated for several calls. For example, you can carry out the completion message from production for all calls that are in a packaging rack. The progress confirmation is also possible with barcode entry.

With JIT-monitoring, you can monitor and control calls by displaying detailed information, or by carrying out actions and special actions.

The basic data and movement data of JIT Inbound is extremely lean and is always retained in temporary storage during operation. This allows a high-performance processing of the usually large volume of quantities in a very small data base volume.

You have various options for dealing with technical or logistic problems manually and quickly. This includes the fast change or the status correction of a call, the signal monitor and the link to the workflow.

The repetitive manufacturing Backflush (PP-REM) is integrated in this component. You can carry out a backflush for several call components both aggregated and temporally separated from the process. The system backflushes the assembled BOM components.

The creation of a delivery is also integrated. You can group the call components of several scheduling agreements in one delivery. You can copy the external call numbers in the delivery which is made possible to your customer by a goods receipt posting with reference to this number.

The integration of handling units (HUs) enables you to automatically pack the JIT calls on creating the delivery.

You can also create and produce internal calls, for which there is initially no concrete customer requirement. After production you store the internal calls in a buffer storage location. On receipt of JIT calls from your customer you can take these directly from your buffer store.

You can receive and process a delivery confirmation from your customer. The system creates a billing document with reference to a delivery confirmation and you can match the customer’s specifications with the data in your system.

You can copy the movement data to the SAP Business Information Warehouse and evaluate it there.

After you have completed the calls, you can archive the JIT data and delete it from the database.

JIT Inbound 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 in the Internet application, the supplier, or sub-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.