SAP - JIT CALLS - Inbound (SeqJC, SumJC)

12/12/2022
JIT Inbound (SeqJC, SumJC)

Generated on: 2022-12-12 07:56:44 GMT+0000
SAP ERP Support Package Versions | 6.0 SP31
PUBLIC
Original content: https://help.sap.com/docs/SAP_ERP_SPV/1ca7f6aba1c940e7b97ec51bd2841bf2?locale=en-

US&state=PRODUCTION&version=6.00.31
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal 1
12/12/2022
JIT Inbound (SeqJC, SumJC)
Purpose
You can use this component if you, as a supplier, receive and supply just-in-time calls. JIT Inbound was developed around the
requirements of the Automotive industry and supports the two following types of JIT call:
Sequenced JIT calls (seqJC)
This type of call is for the receipt of JIT calls, which you supply with fully con gured components, both with reference to an order
and in sequence. The sequenced JIT call supports the entire business process from the receipt of the forecast signal right up
until the creation of the delivery and if necessary, the delivery con rmation.
Summarized JIT calls (sumJC):
This type of call is for the receipt of JIT calls, whose items represent a pair of date and quantity. The items do not have any
reference to the nished product and are not delivered in sequence. The reference number of the call controls all subsequent
processes, such as the delivery. In practice, the reference number is also called the Delivery Order Number (DON).
JIT Inbound 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 Inbound 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 Inbound to suit your business process. The process is automated to
a large extent.
The processing of JIT calls with EDI corresponds to the relevant norms and standards of VDA4916, EDIFACT, Odette and NC866.
Integration
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:
Module Component (documentation)
LO – Logistics - General LO – Material Master Data
SD – Sales and Distribution SD – Basic Functions (customer master records)
SD – Scheduling Agreements for Component Suppliers (forecast

delivery schedule, JIT delivery schedule)
SD - Sales (scheduling agreements)
SD - Billing
12/12/2022
PP – Production Planning and Control PP – Repetitive Manufacturing (Back ush)
LE - Logistics Execution LE - Shipping (outbound delivery)
LE - Transportation
Features
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 con rmation or with JIT-monitoring. You can access both
applications either as a list or in the graphic JIT cockpit.
The progress con rmation 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 con rmation 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 work ow.
The repetitive manufacturing Back ush (PP-REM) is integrated in this component. You can carry out a back ush for
several call components both aggregated and temporally separated from the process. The system back ushes 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.
For summarized JIT calls, you can create a list of operations to be shipped, which you can then process collectively.
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 con rmation from your customer. The system creates a billing document with
reference to a delivery con rmation and you can match the customer’s speci cations with the data in your system.
12/12/2022
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 nd out about requirements at the OEM. The supplier has access to all relevant data, such as call
component, delivery time, sequence and unloading point.
Constraints
With sequenced JIT calls the materials called are often assembled using component lists. Apart from printing the components
list, JIT Inbound does not support shop oor control. However you can use BAPIs to connect a sub-system and transfer the JIT
data.
Transactions: JIT Inbound

Function Transaction
Inbound JIT Calls
Create JIT Call JIT1
Change JIT Call JIT2
Display JIT Call JIT3
Simulate JIT Call JIT4
XML Upload JITXML
Controlling Inbound JIT Calls
Inbound JIT Monitoring JITM/JITMX
Enter Progress Con rmation in a List JITF/JITFX
Signal Monitor JITJ
Inbound JIT Cockpit JITG
IDoc Monitor for Incoming JIT Calls EMJIT
Status Correction JITE
Action Log JITLOG
Barcode Entry JIT6
Bar Code Entry with Standard Value JIT7
Components Requirements List JITA
Requirements Match JITH
Delivery Con rmations: Match and Reprocess Manually DLCN
Comparison of JIT Calls with Delivery Con rmations DLC2
Change/Display Documentation Data JITZ
12/12/2022
Function Transaction
Emergency
Inbound JIT Monitoring JITM
Fast Change JIT5
Status Correction JITE
Microsoft Excel Download JITX
Emergency Creation of Summarized Range Call JITEMRA
Basic Data
Maintain Control Data JITV
Maintain Production Information JITL
Maintain Sort Variant OJIT5
Reorganize the Basic Data JITR
Internet Access Data OJIT14
Subsequent Functions
Reprocess Goods Movements JITB
Delivering Operations to be Shipped JITK
Environment
Overview of JIT Calls JITI
Display Action Network JITQ
Archiving JITY
Customizing
JIT Inbound OJITI
JIT Outbound OJITO
Call Structure and Call Types

Use
The call structure describes the header and the arrangement of the data that can be transmitted with a call. Depending on the
OEM and the materials called, there are in practice two different data structures in the JIT calls.
Calls for assemblies

12/12/2022
This call structure is suitable for sequence JIT calls for components groups with many variants. The JIT customer transmits all
call components for a vehicle. You assemble these call components for several components groups (such as door modules) and
deliver them. This is a departure from an order-related BOM for which often neither you, nor the JIT customer, has a unique
material number. The JIT customer awaits the inbound delivery of the assemblies. The call components transmitted are shown
in the delivery note and the billing document.
Calls for discrete materials and summarized JIT calls
The call structure is suitable for summarized JIT calls and for sequenced JIT calls with a limited number of variants. The JIT
customer transmits discrete material numbers, that represent fully developed assemblies, modules or systems. All variants of
the parts called have their own material master record. A BOM must exist in your system for the material. The transmitted call
components are shown in the delivery note and the following invoice of the delivery.
For JIT Inbound there is a three-level call structure, which covers both data structures.
Integration
When creating a sequenced JIT call, the system arranges the data transmitted in the call structure using the components group
determination . You de ne the components group determination in Customizing for JIT Inbound.
Features
The call structure consists of the three following levels:
The call header identi es the call.
The components groups represent the material, or the assembly, that you deliver. They provide the internal control and
management of the JIT calls in the system and contain the delivery dates and the components group material. After a
call has been received, the system assigns each call component transmitted to a call component, using the components
group determination.
The call components are the materials that the JIT customer transmits to you in a JIT call. You receive a reference to the
material master record in your system, the supplier reference number of the customer material, the quantity and the
unit of measure. In addition, the call component contains a reference to the scheduling agreement item in a JIT
scheduling agreement.
The following diagram shows the three-level call structure and the information contained in it.
12/12/2022
Sequenced JIT Calls for Assemblies
Purpose
You can use this process if your JIT customer transmits you call components, which you can then assemble to components
groups and deliver in sequence. Neither you nor the JIT customer has to have a unique material number for the assemblies. You
deliver the assemblies, but in the delivery note and in the invoice you observe the call components transmitted in the sequence
JIT call again.
With sequenced JIT calls for assemblies:
The call header represents the relationship between the JIT customer and the nished product. It includes the external
call number and the sequence number of the nished product as well as the description and plant of the JIT customer. In
addition, the call header can contain a special speci cation of the nished product.
A components group represents the assembly that you create from the call components transmitted and that you
deliver .
The call components are the materials transmitted, that represent components of an assembly and that are displayed
in the delivery, the billing document, and if necessary, the delivery con rmation.
Prerequisites
You have created the necessary master data .
In the JIT basic data you have de ned the JIT customers, the destinations and the components group types.
Process ow
You de ne the assignment of the call components to the components groups in Customizing for JIT Inbound, using a pro le for
the components group determination. The assignment of sequenced JIT calls is generally complex. Therefore, you can
determine components group materials using a customer exit. The system then determines the components group material
before the components group. Here you must ensure that each call component can be assigned to a components group.
12/12/2022
Result
The arrangement of the incoming calls in the call structure is a prerequisite for any further JIT call processing. You de ne the
internal control of the calls in the call control .
Example
The customer transmits the components of four door modules with one call. First of all, the system carries out a components
group material determination and then the components group determination. In this way it assigns each call component to a
door module. The system uses the components groups for the internal control of the calls. The system transfers the call
components in the delivery and billing document.
Sequenced JIT Calls for Discrete Materials
Use
You use this process, if your JIT customer transmits discrete materials, that represent fully developed assemblies or modules.
For each discrete material there is a material master record in your system. You produce discrete materials and deliver them in
sequence. The discrete materials are shown in the delivery note and the following invoice. This type of processing is useful with
a limited number of variants, as you have to create a material master record for each variant.
With sequenced JIT calls for discrete materials:
the call header represents the relationship between the JIT customer and the nished product. It includes the external
call number and the sequence number of the nished product as well as the description and plant of the JIT customer. In
addition, the call header can contain a special speci cation of the nished product.
the components groups and the call components can be grouped together logically. You produce the call components
transmitted and show them in the delivery, the billing document and if necessary, in the delivery con rmation. Because
the components group controls the call within your plant, you assign the call components to a components group. You
can also adopt the material of the call component as components group material.
Prerequisites
You have created the necessary master data . You have created a material master record and a BOM in your system for
all variants that the JIT customer calls.
In the JIT basic data you have de ned the JIT customers, the destinations and the components group types.
12/12/2022
Process ow
the components group determination. Seeing as the assignment for the sequenced JIT calls is not usually very complex, the
pro le is often sufficient for an assignment. You can also realize a components group material determination using a customer
exit. The system then carries out this components group material determination before the components group determination.
Here you must ensure that each call component can be assigned to exactly one components group.
Result
The arrangement of the incoming calls in the call structure is a prerequisite for any further processing of the JIT calls. You de ne
the internal control of the calls using a call control .
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.
Summarized JIT Calls
Use
You use this process, if your JIT customer transmits JIT calls for non-vehicle-related materials. The call components are often
produced in advance and the calls can be supplied directly after being received.The call components are shown in the delivery
note and the following invoice. For each call component there is a material master record in your system. In practice, this call
type is also known as a call with Delivery Order Number (DON).
You can realize the following scenarios with the call structure of the JIT Inbound:
Individual materials
The JIT customer transmits one or more quantities and dates for a call component in one call. The system saves the
reference number of the call as an external call number in the call header.
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
12/12/2022
In a call, the JIT customer transmits a range of production numbers – a summarized range call – which is split into
several identical calls.
The summarized JIT calls can be arranged as follows in the call structure:
The call header represents the relationship to the JIT customer and can contain several reference numbers. The
reference numbers can be stored in the external call number and in the additional information 1 to 3.
 Note
You can receive calls from your JIT customer, that modify an existing call. Here, it is necessary that the reference
number, that you store as an external call number in the call structure, clearly identi es the call.
The components groups and the call components can be grouped together logically. You produce the call components
transmitted and show them in the delivery, the billing document and if necessary, in the delivery con rmation. Because
the components group controls the call within your plant, you assign the call components to a components group. You
can also adopt the material of the call component as components group material. In the Grouping information eld of
the components group you can enter additional call numbers, which cannot be identifying.
Prerequisites
You have created the necessary master data . You have created a material master record and a BOM in your system for
all materials that the JIT customer calls.
In the JIT Basic data you have de ned the JIT customers, the destinations and the components group types.
Process ow
the components group determination. Seeing as the assignment for the sequenced JIT calls is not usually very complex, the
pro le is often sufficient for an assignment. You can also realize a components group material determination using a customer
exit. The system then determines the components group material before the components group.
Here you must ensure that each call component can be assigned to exactly one components group.
Result
The arrangement of the incoming calls in the call structure is a prerequisite for any further JIT call processing. You de ne the
internal control of the calls using a call control . For the summarized JIT call process, the call control can be very simple, as
summarized JIT calls are generally supplied immediately on receipt.
You can display a delivery list and deliver the summarized JIT calls from there.
You can receive a credit memo for the external call numbers of the summarized JIT calls. The system assigns the credit
memo to the delivery using the external call number.
Example
The customer transmits three materials with one call. The reference number of the call is stored as an external call number and
is saved in the call header together with the time of requirements. The system carries out the components group determination
and assigns exactly one call component to a components group.
12/12/2022
Additional Reference Data
Use
You use this function to save additional reference data for an inbound JIT call or an outbound JIT call on call header level,
components group level, call components level or on all three levels.You can de ne this additional data customer-speci cally, in
other words you can change your elds without making any modi cations. An example of additional data is a packing instruction
or an additional identi cation.
 Note
For performance reasons you should keep the number of additional elds to a minimum.
Integration
You can enter additional reference data either when you create a JIT call or when you receive an IDoc.
Prerequisites
In Customizing for JIT Inbound you have de ned additional reference data under De ne Control Pro le De ne Additional JIT
Reference Numbers. In this activity you also de ne on what level of the call the additional data is displayed.
Features
If you de ne additional reference data this data appears in JIT monitoring or IDoc inbound for example. Up to three
additional elds with reference data are displayed in JIT monitoring and JIT call inbound. You can view additional elds by
double-clicking the Additional Fields indicator in JIT monitoring. The additional data is displayed in a dialog box.
When you create a JIT call the elds are displayed automatically. You can then enter the relevant information.
You can de ne whether the additional reference data is only inbound-relevant, only outbound-relevant or relevant for
both (see IMG activity De ne Additional JIT reference numbers ).
Call Control
12/12/2022
Use
With call control you represent JIT call processing in your system. Call control is extremely exible, as you can de ne a different
type of control for each components group, as required. The control is based on actions that you can carry out depending on the
processing status of a components group. After the system has carried out the action, it assigns a new processing status to the
components group.
For sequenced JIT calls you generally de ne a complex call control, so that you can follow progress in your plant more
closely.
For summarized JIT calls you will most likely de ne a simpler call control, as these are often supplied directly after being
received.
Integration
You de ne the call control determination in Customizing for JIT Inbound.
For a call control to be active you assign it to a components group in the JIT basic data.
Features
The call control consists of the following components:
Internal processing status
The internal processing status describes the progress (status) of a JIT call in your plant, related to the components group (such
as: Components group delivered).
External status
The external status corresponds to the production progress of the nished product in the JIT customer’s plant. If the nished
product comes into your customer’s assembly, an assembly signal is sent. This assembly signal corresponds to the external
status Production release . The external status is also saved in the components group.
Action
The action has a logistical or technical function. You can de ne in which internal processing status an action is permitted and
which internal processing status the components group should obtain after the action is carried out. Actions can be triggered by
an incoming JIT call by EDI and an external status change.
a user dialog in the system, such as a Production Complete con rmation.
The following diagram shows how the components interact.
12/12/2022
Internal Processing Status
Use
The internal processing status is a part of call control. It describes the progress (status) of a JIT call in your plant, related to the
components group. Examples for an internal processing status are ʻCall created’, ʻReleased for production’ or ʻComponents
group delivered’.
Integration
You enter the possible internal processing statuses in Customizing for JIT Inbound.
Features
You de ne an internal processing status for each status that a JIT call in your system is to adopt.
In the call control you de ne an action-status network. This network de nes which actions are permitted in a speci c
internal processing status. Thus, several actions can be permitted for an internal processing status. However, the new
internal processing status must be unique.
The system saves the internal processing status in the components group.
Example
The example shows how the actions convert a components group from your current processing status into a new one.
12/12/2022
External Status
Use
The external status is a part of call control. For a JIT call you also receive information from your JIT customer about the
production progress of a nished product in your production. The system saves this information as an external status per
components group. This external status often represents reorder points of a vehicle in the production line of the JIT customer,
such as an assembly signal.
For each permitted external status change, the system triggers an action, which transfers the current internal processing
status of the components group to a new internal processing status.
Integration
You de ne the external status in Customizing for JIT Inbound.
The external statuses do not depend on the customer and a standard is determined across the system. As not all JIT
customers transmit their status information in the same form, you can enter a customer-dependent correspondence for
the external status, in a conversion table in the JIT basic data.
You can de ne in Customizing for JIT Inbound, which actions should be carried out for the various changes in external
status.
Features
You can de ne any external statuses, that are customer-independent and uniform in your system.
The system converts the customer-dependent external status information according to the conversion table in the
external status.
In call control you can de ne which action is to be carried out for each external-status change.
Example
This example shows how you can convert the external status information, that your customer transmits, to the external status
in your system.
12/12/2022
Actions
Use
The action is a part of call control. It has a logistical or technical effect on a components group. This may be the printing of a
components list or the creation of a delivery, for example. You can de ne the internal processing status of the components
group for which an action is permitted and the internal processing status the components group is to receive once the action
has been carried out. Actions can be triggered by:
An incoming JIT call by EDI and an external status change.
A user dialog in the system, such as a progress con rmation.
Integration
You de ne the possible actions in Customizing for JIT Inbound. You can use the standard actions provided or de ne your
own actions. If the actions you have de ned yourself:
Simply cause a change in the internal processing status, you can enter them in Customizing in the table.
Trigger a function as well as changing the internal processing status, you can use a customer exit.
You de ne the possible actions in Customizing for JIT Outbound. Internal actions can only be triggered when you receive
a call by EDI or with internal system activities and not in a user dialog.
You can also interlink actions in Customizing. The system then carries out two or more actions together.
Features
The system provides the following actions as standard:
Actions Function Description
Actions for Creating and Changing
CREA Create JIT call The system creates the call in the system
and arranges it in the call structure. This
action is usually triggered by a forecast
signal from the OEM.
MODI Change JIT call (total) The system changes the total call.
The action MODI is contained in action PIN.

See also: Action PIN.
12/12/2022
MODH Change call (call header and components With the external status change, for
group) example, the system changes only the call
header and the components groups.
MODG Change call (components group) The system only changes the components
group of the call.
JIT2 Change a call using transaction JIT2 The system carries out this action if you
have changed a call with the transaction
Change JIT call (JIT2).
MODC Change a JIT call component You use this action to change individual
components of a JIT call. Only the
component to be changed is sent and
changed. This may be the case if your
customer increases the quantity of a
component.
If the system cannot nd the component in

question then another component is added
to the call similar to action INSC.
INSC Add call component You use this action to add a component to
an existing JIT call. The system sends only
the new individual call component and adds
it to the JIT call.
DELC Delete a call component You use this action to delete a component
from an existing JIT call.
DLET Delete components group The system deletes the components group,
if it is no longer transmitted for a repeated
call. If you do not de ne the action, the
components group is retained in the call.
CGAP Add components group (SumJC) The system adds a components group to a
summarized JIT call that already exists
with the same identi cation in the
summarized JIT call.Both components
groups differ only in quantity and date.
Actions for Production and the Completion Message
PIN Transfer to production The system transfers a components group

to production. This action is usually
triggered by an assembly signal from the
OEM. If no call exists for this components
group, the system creates a new call.
If the components group type changes, the

components group is deleted and a new one
created. In this case, you must have
maintained action DLET for the status
change to initial in Customizing.
Note that the action PIN contains the action

MODI.
PCOM Print component list The system prints a list of call components,
which you can enter in the production as an
accompanying note.
PINP Release for production and print component Interlinked action with sub-actions PIN and
list PCOM.
12/12/2022
CGRP Generate and assign grouping term Assigns grouping information to a
components group and to a grouping index.
POUT Completion message from production The system assigns the status to the
components group, but does not carry out
any goods movement.
PICK Print pick list The system prints a pick list, which you can
display, for example, on a packing rack.
POUP Create completion message, and print pick Interlinked action with sub-actions POUT
list and PICK.
Actions for the Back ush and Goods Movement
BFLU Carry out back ush The system carries out the repetitive
manufacturing back ush or a stock transfer.
BFLP Carry out back ush in the background The system carries out the repetitive
manufacturing back ush in the background.
BFDL Create back ush and delivery Interlinked action with sub-actions BFLU
and DELI.
Actions for the Delivery
DELI Create Delivery The system creates a delivery, to which it

adds the call components of the component
groups selected.
DELU Add components groups to the delivery The system adds the components groups
of an existing (open) delivery.
DELD Remove components groups from the The system removes the components
delivery groups from the delivery.
DLSP Send Delivery from External Service The system sends a delivery from an
Provider to Manufacturer external service provider to a manufacturer.
VL10 Create SumJC delivery from VL10 For summarized JIT calls, you can generate
a delivery list. The system selects all calls
for the delivery list, whose internal status
permits this action (the action calls the
sub-action DELS).
DELS Create delivery from VL10 / without lock Sub-action of action VL10 You can replace
this action by one of your own, if you want
to created your own delivery list.
GOIS Post Goods Issue You can use this action to post the goods
issue for a JIT delivery.
GOCC Reverse goods issue You can use this action to reverse the goods
issue for a JIT delivery.
Actions for closing the calls.
STAT Update JIT calls in BW The system only updates the

calls/components groups in the Business
Information Warehouse, whose internal
processing status permits this action.
FINI Close components group The system sets the status as closed for
this call/components group.
ARCH Release JIT calls for archiving In archiving, the system selects only those
12/12/2022
JIT calls/components groups, whose
internal processing status permits this
action .
REOR Reorganize JIT calls The system deletes the call from the
database.
Actions for special occurrences
CANC Cancel components group The system sets the components group to
the internal processing status Canceled .
SCRA Reprint component list (scrap back ush) The system prints the component list with
highest priority, so that the components
group can be reproduced immediately.
REPR Reprint component list The system prints the component list for a
components group, if this has been
damaged, for example, in production.
NIO Missing parts message (status change) With this action you can set a scrap
components group to a park status, if you
do not want to produce immediately.
WFLW Trigger work ow event The system triggers a work ow event.
Actions for internal calls and buffer store
WIN Store components group The system stores a components group

from the issue storage location of the
components group materials in the puffer
storage location.
SWCG Exchange components group (internal call) The system exchanges the component
groups of two calls. Using this action, you
can deliver the JIT calls using buffer stores.
PSWC Print components group exchange You can carry out this action after
exchanging the components groups. The
system prints a list of the call components
to be removed from storage, which you can
forward to the employee in storage.
WOUT Remove components group from storage The system transfers a components group
from the buffer storage location to the
receiving storage location of the
components group material.
CRHU Create a handling unit from a components The system creates a handling unit from a
group components group before you store it in the
buffer storage location.
DEHU Pack and delete handling unit The system unpacks a components group
from the handling unit and deletes the HU,
for example after you have removed it from
the buffer storage location.
HUPP Generate an HU in production The system generates an HU from

production. You can delete it using the
action DEHU.
Actions for the Delivery Con rmation
MTCH Set delivery con rmation to ʻmatched’ The system matches the quantities with the
components group.
12/12/2022
UDMT Reset delivery con rmation match The system resets the quantity match of
the components group.
Interlinked Actions
Use
This function enables you to link several actions to an interlinked action. You can trigger these interlinked actions with an
inbound EDI message, or a user dialog and in this way you can carry out several actions linked together.
Integration
You de ne interlinked actions in Customizing with the IMG activity Determine JIT Call Control and Actions .
Features
You can join several actions to an interlinked action and carry out these actions linked together.
You can determine the sequence in which the system executes the actions.
You cannot nest interlinked actions. This means that a sub-action cannot be an interlinked action.
 Note
Note the business dependencies of the sub-actions. Only the rst sub-action should modify the JIT call, all others should be
read-only actions, such as PCOM (print component list). Otherwise there would be problems with the update, if a sub-action
is carried out before the previous one has been completed. In particular, actions that cause material movement cannot be
interlinked. The action BFLU cannot be a sub-action of an interlinked action. SAP is not responsible, if you interlink actions
that are to be updated.
If an interlinked action consists of two sub-actions, the new internal processing status is already set after the rst sub-action
has been carried out. If there should be a termination when the second action is carried out, the components group is still
given the new processing status. In this case you can make a status correction and then carry out the second sub-action
again.
Action Log
Use
In more complex processes, for example if you work with external service providers, it can be useful to have an overview of the
history of a JIT call. The action log gives you an overview of the individual actions and their results for each JIT call. The system
logs successful and unsuccessful actions allowing you to recognize and analyze critical situations early on.If an error occurs for a
call you can use this function to look for that error.
Integration
The action log further enhances functions such as status correction and JIT Monitoring Inbound .
Prerequisites
12/12/2022
To work with action logging you must have set the Logging Active indicator in call control. You do this in Customizing for JIT
Inbound by choosing Call Control De ne Call Control.
Features
You access the action log from the SAP Easy Access Menu by choosing Logistics Logistics Execution JIT Inbound or
JIT Outbound Environment Display Action Log (Transaction JITLOG).
You can also call up the action log for a call from JIT Monitoring Inbound or Outbound.
On the initial screen for displaying action logs you can de ne a time period for which you want to view action logs. You
can also choose whether you want the system to display logs for a certain action, a certain user or a certain transaction
code.
Using the action log function you can view the individual actions that have been carried out for a call. On the left you see
the logs that correspond to your selection, displayed in a hierarchical structure.
For each action that has been carried out for a JIT call, a log entry is created containing data such as user name, action,
execution time and previous internal status. Entries that were created when status correction was carried out are
displayed. This allows you to track which users have made changes and the new status of the call.
The traffic lights ( , and ) that are displayed for each action indicate the status of the action in question and
allow you to recognize and avoid critical situations in good time. On the right, in the list of messages, you can see how
many messages there are per status.
If you position the cursor on a components group and choose Display Components Group the system displays a
dialog box giving your detailed information about the JIT call to which this components group belongs.
To see technical information about a message, select a message and choose . The system displays technical
information such as the message typeor the message class of the selected message.
For the list of messages you can use the standard functions for the SAP List Viewer .
When JIT calls are archived the logs relating to them are deleted.
You can delete logs using transaction JITLOGDEL. Before this transaction is carried out the system checks whether you
have authorization for this transaction.
Before JIT archiving you can save the logs with archiving of the application log. Enter JIT as the object and Action as the
subobject.
Activities
1. Choose Logistics Logistics Execution JIT Inbound or JIT Outbound Environment Display Action Log
(Transaction JITLOG).
2. Enter the period for which you want to view the action log. If necessary limit your selection criteria further and choose
.
The Log Display screen is displayed and you see the log for your selection.
Result
The action log gives you an overview of the actions that have been carried out for a call. You can also see which user has carried
out a certain action. From the traffic lights you can see the status of a call, allowing you to react to critical situations in good
time if necessary.
12/12/2022
Example of Call Control

The following example displays a possible call control for JIT Inbound, which can be used for sequenced JIT calls. The external
status and the signals from the user dialog trigger actions that carry out functions and change the internal processing status of
the components group.
Master Data in the SAP System
Purpose
You use this process, to test or create the master data in the SAP system, a prerequisite for working with the sequenced JIT
call.
Process ow
1. In the system, you create the customers (sold-to party) from whom you want to receive sequenced JIT calls.
2. You create a material master record for the components groups and components, in the system.
3. You create BOMs for the materials.
4. You create a scheduling agreement with forecast delivery schedules for the call components.
Result
You have created the necessary master data. Continue creating the JIT basic data .
Process Customer Master Record
Use
12/12/2022
With this procedure you can maintain the necessary entries in the master records of the business partners that you want to
supply with JIT calls.
You can create customer master records for business partners in the following partner roles:
Sold-to party
Goods recipient
Payer
Invoice recipient
For the JIT process you require at least one master record with the partner roles sold-to party and goods recipient. If you want
to supply several plants of a sold-to party with JIT calls, you can create additional customer master records with the partner
role goods recipient and then create this in the sold-to party customer master record as a partner role.
Procedure
1. Choose Logistics Sales and Distribution Master Data Business partners Customer Change Complete.
This takes you to the dialog eld Change Customer: Initial Screen .
1. Enter the customer and the data of the sales area.
2. Choose .
This takes you to the dialog eld Change Customer: General Data .
1. Enter data as required.
1. Choose the tab page Unloading point and enter an unloading point.
2. Choose Sales area data.
3. Choose the tab page Shipping and select the indicator Order combination .
4. Choose the tab page Partner roles and if necessary, enter a partner name. If you want to enter other goods recipients,
make an entry in the table.
5. Choose to save your entries.
Result
You have made the necessary entries in the customer master record. Then you can de ne a JIT customer in the basic
data. For further information see the documentation SD Basic Functions and Master Data in Sales and Distribution
under Customers and Business Partners .
A customer’s unloading point is often not speci c enough for the JIT process. Therefore you can enter an additional
assembly location to de ne the destination more speci cally.
Process Call Components
Use
12/12/2022
This procedure describes the settings in the material master data for the call components, that are relevant for JIT Inbound.
Procedure
1. Choose Logistics Production Master Data Material Master Material .
2. Choose a processing type and the organizational units and enter the necessary data in the tab pages speci ed below.
3. If you want to derive the components group material from the con gurable material of the call component in the
components group determination ,you must enter the con gurable material in the tab page Basic data2 in the eld
Cross-plant CM.
4. In the tab page Sales: sales org. 1 you can enter the same values in the elds Division and Material group , such as 01 and
KAUF, for all call components.
5. In the tab page Sales: sales org. 2 , enter the value NORM (normal item) in the eld Gen. item cat. grp.
6. In the tab page Sales:general/plant enter uniform values in the elds Trans.group , Loading group , and Avail. check ,
such as 0001, 0001 and 02 (individual requirements).
7. Enter the following values in the materials planning tab pages.
For correct values in materials planning and the back ush, enter the value PD (MRP) in the eld MRP type .
In the eld MRP lot size enter the value EX (exact lot size calculation).
1. If you work with repetitive manufacturing, enter the following values in the MRP tab pages:
For call components select the indicator Repetitive manufacturing and enter a pro le in the eld REM pro le.
Create a production version and select the repetitive manufacturing indicator in the detailed view.
1. If you work with the forecast, enter any forecast model in the tab page Forecast , such as forecast model K.
2. In the tab page Accounting 1 in the eld Price control, enter the value S (standard price) and in the eld Standard price ,
enter the price of the material.
Activities
For more information, see the documentation LO – Managing the Material Master Data under Material Master Records
Create BOMs
Use
You usually require a BOM for the call components that you produce yourself. Then you can:
carry out a repetitive manufacturing back ush
plan material requirements for the BOM components
display the BOM components in the component requirements list
display the BOM components in the component list of the graphic progress con rmation.
Prerequisites
12/12/2022
You have created a material master record for the call components.
Procedure
1. Choose Logistics Production Master Data Bills of Material Bill of Material Material BOM Chang e
This takes you to the screen Change Material BOM: Initial Screen .
1. Enter the material concerned and the plant. For the usage of the bill of material enter the value 1 (production-relevant
BOM)
2. Choose .
This takes you to the item overview.
1. Enter the items. For item type you can use storage material , for example.
2. Save your entries.
Result
You have created the BOM. For more information, see the documentation PP – Bills of Material .
Creating JIT Scheduling Agreements
Use
As the JIT process is integrated with the scheduling agreement process, you require a JIT scheduling agreement or JIT
scheduling agreement item for each call component. The JIT scheduling agreement also ensures that the system transfers the
call components to the internal JIT material table.
This procedure describes the entries required in a scheduling agreement for the JIT process.
Prerequisites
You have de ned the relevant JIT customer in the JIT basic data.
You have created material master records for the call components.
If you want to combine several call components in a delivery or in a billing document, you must enter the same values for all JIT
scheduling agreements in the elds speci ed. The most important thing is that the values match at item level.
Procedure
Choose Logistics → Sales and Distribution → Sales → Scheduling Agreement → Create
This takes you to the screen Create Scheduling Agreement: Initial Screen .
12/12/2022
Enter JIT Scheduling Agreement as the scheduling agreement type, or JIT Scheduling Agreement (LQ) if you want to work with
delivery con rmation .
Enter the organizational data.
Choose .
This takes you to the item overview.
Enter the call components in the item overview.
Choose the Sales tab page.
Enter JIT delivery in the Delivery lock eld.
Choose the Procurement tab page.
In the items, enter the plant and check the requirements type proposed by the system. The requirements type determines the
planning strategy. If necessary change the requirements type to 011 .Note that you cannot change the requirements type after
the rst goods delivery.
Choose Goto → Header → Shipping and enter your customer’s unloading point in the Unloading Point eld.
Choose the Billing Document tab page and enter the incoterms and terms of payment.
You can combine different scheduling agreements in a billing document if the criteria are ful lled. For example, a purchase order
number must be entered in the header of the scheduling agreements, which is valid for all items. The combination also depends
on the copy control.
Choose .
Now create forecast delivery schedules for all scheduling agreement items, allowing a sufficient time frame (several months).
To do this select a delivery item, choose Forecast delivery schedule and enter the necessary data.
Save your entries.
Result
The system automatically transfers the call components to an internal JIT material table.
For more information, see SD Scheduling Agreements for Component Suppliers .
Components Group Material
Use
The components group represents the assembly, the module or the system that you assemble from the call components
transmitted and that you deliver . You can assign a components group material to each components group. This forms a logical
unit for the data, which is the same for all call components.
12/12/2022
With sequenced JIT calls for assemblies the components group material represents all of the relevant call components
and groups the common properties.
With sequenced JIT calls for discrete materials and with summarized JIT calls the components group material is
generally a con gurable material and the call components are the relevant con gured materials. You can also enter the
call component directly as a components group material.
Integration
Within the JIT process the components group material and its production version has merely a controlling character. The
system does not carry out stock posting or other functions of Production (PP) or Sales (SD) at the components group material
level.
Features
The components group material has the following signi cance in the JIT process:
The system determines the production line from the production version of the components group material, if you enter
in the production line in JIT monitoring or in the progress con rmation.
In sequenced JIT calls, the system determines the packing instructions from the components group material, if you want
to create a delivery handling units (HU).
The system determines the storage locations from the production version of the components group materials, if you
trigger stock transfer with the action BFLU (carry out back ush). See also De ning the Production Info .
The system determines the issue storage location from the production version of the components group material, when
storing components groups of an internal call in a buffer. When removing components from the buffer storage location,
the system also determines the issue storage location from the production version of the components group material.
This is used for information, such as in JIT monitoring.
Basic Data in JIT Inbound
Purpose
You use this process, to test or create the basic data in the SAP system, a prerequisite for receiving and processing JIT calls.
The basic data is taken from the SAP System. The system keeps this data constantly in temporary storage, which is recreated
daily. This type of data management prevents frequent access to the database and allows optimal performance. This means
that JIT Inbound is also able to handle the large order volumes common in the automotive industry.
Process ow
1. You de ne the customers, from whom you want to receive JIT calls.
2. You de ne the lead times of the JIT customer for the simple delivery scheduling.
3. You de ne the conversion of the external status information in your own external status description for each customer.
4. You de ne the destinations of the JIT customer. These are the unloading points and the assembly locations to which you
deliver the components groups.
5. You de ne the components groups that you deliver to the destinations of the JIT customer.
6. Using the production info, you determine which call components you want to back ush or transfer.
12/12/2022
7. After you have changed the basic data, the system automatically reorganizes the temporary storage. In this
reorganization the system deletes the temporary storage and then recreates it. However, if you change a material
master record or a customer master record, you have to reorganize the temporary storage manually.
8. If you want to use the Internet functions of JIT Inbound, you can maintain the Internet access data.
Result
You have created the basic data, the prerequisite for working with JIT calls.
De ning the JIT Customer
Use
You use this function to determine the sold-to parties in the SAP system that you want to supply with JIT calls.
The JIT customer consists of sold-to party and partner description. The sold-to party is the customer for whom there is a
corresponding customer master record in the SAP system and the partner description is the name that the customer transmits
with a call. If you supply several plants or storage locations for one customer, you can control these individually. To do this, you
must create several JIT customers with the same sold-to party but with different partner descriptions (goods recipients). For
each goods recipient you must create a customer master record and then assign it to the sold-to party as a partner role. You
enter the partner description of the goods recipient at the JIT customer.
Integration
The de nition of the JIT customer guarantees efficient data retention and processing, because the total quantity of customers
in the system is reduced to a smaller quantity of JIT customers.
Prerequisites
You have already created a customer master record in the system for the JIT customer (see also: Process Customer
Master Record ).
You have de ned the control pro le for the delivery in Customizing for JIT Inbound.
If you work with summarized JIT calls, you have de ned the control pro le for summarized JIT calls in Customizing for JIT
Inbound.
Features
Sold-to party
You can enter one of the business partners entered in the system, as sold-to party.
Partner description
You can also enter a partner description with the partner role goods recipient and in this way set up a combination of
customer and plant or customer’s storage location. When you receive a JIT call with EDI, the customer generally
transmits the sold-to party and the partner description. If the sold-to party is unambiguous, then this alone is sufficient.
You can enter the time zone of your customer’s plant.
You can enter a usage for the materials delivered to this customer.
12/12/2022
You can enter a control pro le for the components group determination. You de ne the control pro le in Customizing for
JIT Inbound. This pro le enables you to control with which priority the system deals with the individual criteria of the
components group determination. The criteria are, for example, the unloading point or the assembly location of the
components group material.
You can activate the signal monitor for this JIT customer. If you do not select the indicator Signal monitor active , the
signal monitor does not record the data for this customer.
You enter a call type and a maintenance mode as a default value for the dialog transactions.
If you want to supply the JIT customer with summarized JIT calls, you have to enter a control pro le for summarized JIT
calls.
You can enter a control pro le for the creation of the delivery.
As an alternative to transaction JITV (see below) you can also maintain JIT customer data in transaction JITC . In this
transaction you can select a customer and edit this customer’s data. In comparison with transaction JITV the advantage
of this transaction is that two users can maintain two different data records for JIT customers at the same time. When
you work with transaction JITV all customer data is locked.
Activities
1. Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Customer (Transaction JITV).
This takes you to the screen Maintain JIT Customer.
2. Create entries for your customers.
 Note
After you have de ned the JIT customer, you can create JIT scheduling agreements for the customer (see also Create
JIT Scheduling Agreements ).
De ning the Lead Times
Use
With this function you can realize simple delivery scheduling for JIT calls, in which the system determines a planned delivery
date for components groups based on a lead time shift.
The transport times for a speci c customer are generally relatively constant in the JIT process. You can:
Add an empirical value to the time of an external status
Subtract an empirical value from the customer’s planned time of requirements.
The system saves this result as a planned shipping time with the components groups. You can then enter the planned shipping
time or the planned shipping date as a selection criteria in JIT monitoring.
 Example
You can subtract four hours from the customer’s requirements date and plan this time as the shipping time.
Features
12/12/2022
You can use the lead time, to implement a simple delivery scheduling procedure of the calls. The system calculates the
base time selected and adds or subtracts the time shift. The system saves this result as a planned shipping time with the
components groups.
You can enter the lead time per JIT customer or per components group type.
You can enter the requirements date or the time of an external status as the base time. If no special external status has
been maintained, the system automatically takes the value saved for “empty” . If no value is saved here, no calculation is
carried out.
You can enter the time that the system adds or subtracts to the date chosen as the base time, to the second.
You can also take the factory calendar and the shift sequence of your plant into account in the lead time.
If your customers are in a different time zone or a different country, which has different public holidays, you can also take
your customer’s factory calendar into account in the lead time. To taken the customer’s factory calendar and the pickup
times of the unloading point into account, two conditions must be met:
The eld Basis Time must be lled with the value External Status.
The eld Additional Time with Goods Rec'g Times of Unloading Point must contain a value.
The system adds the difference in time from the customer calendar to the external status time. To do this it uses
the calendar for the unloading point that contains the customer’s requirements time.
You can also implement project-speci c delivery scheduling using a customer exit.
Activities
1. Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Customer (Transaction JITV).
2. Under Maintain lead times enter the lead times per components group type or per customer.
De ning the External Status Information
Use
With this function you can convert the status information that your customer transmits to you, into an standard internal
description.
The production progress describes the external status information at the customer. However, different customers often
transmit different descriptions for the same business process. You convert the external status information into an external
status, that is unique within your system.
 Example
A customer transmits a JIT call with the external status information Assembly signal . This information signi es the
production release for the components groups of the call. Therefore you convert the external status information Assembly
signal into the external status Production release .
12/12/2022
Prerequisites
You know which external status information your customer transmits.
You have de ned your external status in Customizing for JIT Inbound.
Features
The system converts the external status information according to the conversion table in the external status, so that you have
a uniform description within your system. In the JIT Inbound dialogs only enter the description of the external status.
Activities
1. Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Control Data.
2. Under Conversion external status information enter the conversion for all customers and all status information
transmitted.
De ning the Destinations
Use
With this function you de ne the locations for inbound delivery at your JIT customer. The inbound delivery locations are made up
of the unloading point and possibly also the assembly location. This data is saved in the JIT basic data.
If you want to make the component groups available directly at a production line, the unloading point from the customer master
record is often not exact enough. Therefore you can enter an additional assembly location in the JIT basic data to de ne the
destination more speci cally.
Prerequisites
You have de ned the JIT customer in the basic data.
You have de ned the unloading points in the customer master record.
Features
The system saves the destination in the components group when processing JIT calls.
The unloading point is a central object for controlling sales and distribution. For example, you create scheduling
agreements in the system, with reference to an unloading point. In this way you can control the inbound delivery of the
same materials to your customer’s various unloading points.
You can also enter an assembly location in the customer’s plant. This is often a production line. You can then print the
assembly location on a picking paper, for example. You can also control the components group determination with the
assembly location.
In practice the manufacturer’s assembly locations may regularly change. To keep maintenance of this data to a minimum
you can enter the current data for the assembly location and unloading point during operation. The data from
Customizing ( JIT Inbound De ne Control Pro les De ne Components Group Determination) is then
overwritten. In this case, it is advisable that you do not maintain assembly location and unloading point in the
destination.
12/12/2022
You can enter additional text for each destination. This can be helpful if one of your JIT customers has an additional
description for an unloading point, for example. You can enter this description for a destination. This data is then
available when you print forms.
Activities
Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Customer and enter the destinations
per JIT customer.
De ning the Components Group Types
Use
With this function you de ne the components group types for the JIT processing call structure . The components groups
represent an assembly, a module or a system that you actually deliver to your JIT customer. You control the JIT call process in
your system.
Integration
The system requires the type of a components group, above all to assign all call components to the components groups on
receipt of a JIT call, according to the components group determination .
Prerequisites
You have de ned the destinations for the components group types.
If necessary, you have created a material master record for the components group material (see also: Components
Group Material ).
You have de ned the call control for the components group types in Customizing for JIT Inbound.
Features
The components group types are customer-dependent and contain the following data:
The destination, which consists of the unloading point and the assembly location.
The material number of the components group material (optional).
The call control , with which you determine the sequence of the external status, the actions and the internal processing
statuses.
The plant of the components group material.
The production version of the components group material that you can enter (optional). By entering the production
version, you can produce components groups on different production lines, which are otherwise identical.
The control pro le for internal calls , which you can optionally enter, if you want to produce JIT calls in a buffer storage
location.
A description of the components group types. You can add additional text to this description.
Activities
12/12/2022
1. Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Control Data.
2. Under Maintain Components Group Types enter the necessary components groups.
De ning the Production Info
Use
With this function you can de ne for each plant how the system handles the call components in the back ush.
If you create a call component in in-house production, you can choose the repetitive manufacturing back ush. In this
back ush, the system posts the goods receipt for the call components and the back ush of the BOM components.
If you procure or produce a call component from a sub-supplier, you can transfer it from the production storage location
to the shipping storage location.
You can maintain entries with and without plant. As a default the system uses the entry with plant, if this is available.
Integration
Depending on your call control you can trigger the back ush with the actions BFLU (carry out back ush), BFLP (carry out
back ush in the background) and BFDL (create back ush and delivery).
Prerequisites
You have created a material master record in the system for the call component.
You have created a JIT scheduling agreement in the system for the call component.
Features
The system automatically transfers the materials, for which a JIT scheduling agreement exists, into the table. You can set the
following goods movements for the materials:
Repetitive manufacturing back ush
If you produce the call components yourself and a BOM exists in the system, you can post both the goods receipt of the
call component as well as the goods issue of the components assembled in it (back ush). All functions of the repetitive
manufacturing back ush are available, (see Back ush ).
Stock transfer posting
The system determines the storage locations using the following logic:
If there is a components group material for the components group to which the call component is assigned, the
system determines the storage locations from the production version of the components group material.
If there is no components group material, or a production version has not been created for a components group
material, the system determines the production storage location from the material master of the call
component, as the issue storage location. It determines the shipping storage location from the call component’s
scheduling agreement as the receiving storage location.
You can also set that the system does not post goods movement or that you can realize your own goods movement
using a customer exit.
12/12/2022
As well as the goods movement you can also determine, with an indicator, whether the system should explode the BOM for a
material in the following cases:
When printing the component list for production (action PCOM )
When displaying the component list in the graphic progress con rmation (JIT cockpit).
When selecting the materials, that are delivered from the sub-supplier (Internet scenario)
Activities
1. Choose Logistics Logistics Execution JIT-Inbound Basic Data Maintain Production Information (Transaction
JITL).
This takes you to the screen Maintain Production Information – Plant-speci c.
2. Enter a plant. (If you want to maintain the same production information for all plants, set the indicator All Plants .
3. Choose .
4. Enter the call components and the type of goods movement.
5. If you want to explode the BOM of the call components in the cases named above, select the indicator Explosion . In
addition, you can make settings for entering documentation.
6. Choose .
Reorganizing the Basic Data
Use
The system retains the necessary master data and the JIT basic data in temporary storage, which allows you very fast access. It
updates this temporary storage once daily. If you make changes to master data or JIT basic data during a day, you must trigger
the update manually with this function. Otherwise the system continues with the old data until the automatic update.
You should reorganize the basic data if you have changed a material master record, a customer master record or a BOM.
If you change the JIT basic data or a JIT scheduling agreement, the system usually reorganizes the data automatically.
However, if you use several application servers, you should also reorganize manually.
Features
Recreating the basic data in the temporary storage.
The system determines whether the temporary storage contains old basic data. If this is the case, it deletes the old data and
recreates the temporary storage.
Reorganizing the JIT material master data.
The system determines all JIT materials, which have a reason for rejection in the scheduling agreement. If there are no more JIT
calls available for these materials, it displays them in a list. You can then select the materials and delete them from the JIT
material table. In this way you do not have to ll the JIT material table with unnecessary data.
Transfer from new scheduling agreement items to existing calls.
12/12/2022
If you enter a reason for rejection in a scheduling agreement, for which there are existing JIT calls that have not yet been
delivered, you can use this function to assign the calls to a new scheduling agreement. The system determines all scheduling
agreements with:
a reason for rejection
the same JIT customer
the same customer material
the same unloading point.
Then it proposes the JIT materials that can be transferred. You can then select JIT materials and start the transfer.
Activities
Choose Logistics Logistics Execution JIT-Inbound Basic Data Reorganize JIT Basic Data , to start the
reorganization.
Structure of the JIT Inbound
Purpose
This process describes an example for a total business process in JIT Inbound. The process is orientated towards the usually
complex sequenced JIT calls for assemblies or discrete materials, that require exact internal control. As a rule, summarized JIT
calls have a simpler process.
Prerequisites
You have de ned a call control in Customizing.
You have created the necessary master data in the system.
You have de ned the JIT basic data .
Process ow
1. Transfer of requirements
2. Before receiving the JIT calls, you receive the forecast delivery schedules or JIT delivery schedules from your JIT
customer. You use these to create requirements and they can be evaluated in the scheduling agreement processing. In
requirements planning you generate independent and dependent requirements and for each component transferred, if a
BOM exists.
3. Creating JIT Calls
4. As a rule, the forecast signal is received several hours before the requirements date. This signal begins the components
group determination, which assigns the components called to a components group in the SAP System. The components
group determination can be very complex, particularly with a call structure for assemblies, as the JIT customer only
transmits a collection of all materials required for a nished product.
5. Production
1. You receive the assembly signal that triggers the transfer to production. The system prints a component list for each
components group called, and for each production line.
12/12/2022
1. Production Completion
After the production and staging of the components group in a transport rack, you can enter a production completion message.
The production completion message triggers the picking papers to be printed.
1. Back ush
2. You determine the components groups that are to be included in a transport and you trigger an aggregated back ush for
all components contained in it.
3. Delivery
1. You create a delivery note that contains a scheduling agreement item with the cumulated quantity per component called
(material number).
2. On the basis of the delivery note, the system enters the goods issues, updates the cumulative delivered quantity and
processes the relevant forecast delivery schedules.
3. Using the delivery as a basis, the system creates the billing document. You can also create the billing document on the
basis of a day’s collective delivery note or a delivery con rmation.
1. Updating the Statistics .
You update the statistics in the SAP Business Information Warehouse, which allows you a period-oriented evaluation of
production and sales.
1. Completing JIT Calls
When your JIT customer has con rmed and paid for a delivery, you can complete the relevant JIT calls.
1. Archiving or Reorganizing JIT calls
The high volume of JIT calls, common in the automotive industry, means that you will soon have a large amount of data in the
system. You can archive the completed JIT calls or simply delete them from the system.
Result
You have completed the whole process. The system also provides control and monitoring , which allow you to access the
process.
Example
The following graphic displays a JIT call process:
12/12/2022
Transfer of Requirements
Use
Before receiving the actual JIT calls, your JIT customer sends you the forecast delivery schedules or JIT delivery schedules as a
requirements forecast. These refer to scheduling agreements that exist in your system. In the automotive industry, the forecast
delivery schedules can have a horizon of 10 months and the JIT delivery schedules a horizon of 10 days.
You carry out requirements planning on the basis of these delivery schedules. In this way the system creates independent
requirements for each material transferred. If the materials transferred are based on BOMs, the system also creates
dependent requirements. Here it creates planned orders that are not directly relevant to production, but help to create
requirements. If you obtain materials from other suppliers, the system forwards the requirements in the form of forecast
delivery schedules and updates the corresponding scheduling agreements.
Integration
JIT Inbound uses the usual functions of the component SD – Sales and Distribution with scheduling agreements, forecast
delivery schedules and/or JIT delivery schedules.
You carry out requirements planning with the usual functions of the component PP – Material Requirements Planning .
When you forward forecast delivery schedules to your supplier, the system uses the function of the component MM -
Purchasing .
Prerequisites
You have created the necessary master data in your system for each call component.
Features
When the system receives a forecast delivery schedule or JIT delivery schedule, it creates schedule lines in the
scheduling agreement.
12/12/2022
The system indicates the planned orders created in requirements planning as not relevant to production and forwards
forecast delivery schedules to your supplier.
Activities
For more information on scheduling agreements, forecast delivery schedules and JIT delivery schedules, see the documentation
SD – Scheduling Agreements for Component Suppliers .
Creating and Changing JIT Calls
Use
The actual process of JIT Inbound begins when your customer rst transmits the JIT call and the call is created in your system.
The system receives the IDoc and carries out the components group determination to arrange the call in the call structure.
With sequenced JIT calls, the JIT customer transmits the call several times with varying external statuses (such as forecast,
production release) and if necessary, with a different sequence number. The system recognizes from the external call number,
that the call has already been transmitted and modi es the call.
Integration
Description Actions
Create call CREA
Change call MODI
Change call header and components groups of the call MODH
Change components groups of the call MODG
Process JIT calls manually JIT2
Delete components group DLET
Prerequisites
In your process control you have allowed the action for changing the current internal processing status.
To create the JIT call, the action CREA must be allowed for an initial internal processing status.
Features
An incoming JIT call from the customer via EDI triggers the creation of a JIT call in the SAP system. First of all a
corresponding IDoc is created by the EDI sub-system, which is then converted to your own call structure .
In Customizing for JIT Inbound under De ne Message Types you can de ne with which message typeindividual messages
are displayed, during IDoc processing. You cannot issue messages that, as a default, are issued as warning messages as
error messages. See also IDoc Monitor for Inbound JIT Calls .
You can use action CREA for the rst transmission of a call. It is usually triggered by the OEM with the external status
Forecast .
You can use actions MODI , MODH and MODG to change the JIT call in later transmissions.
12/12/2022
If the call is only transmitted with the changed external status, for example, you can change only the components
groups with the action MODG .
If the sequence number is also changed, you can change the call header and the components groups with action
MODH .
You can change the total call with action MODI. This action also requires the highest performance.
If you have processed a call manually in the menu ( JIT call Change ), the system carries out internal action JIT2 .
You can use the action DLET to delete the components groups that are no longer transmitted for a repeated call. If you
do not carry out the action, the components group remains unchanged in the call structure.
 Note
With sequenced JIT calls it is important that you allow action DLET in call control, as well as actions MODI , MODH or
MODG . With this type of call, the JIT customer does not usually expect a components group delivery, if the
components group is no longer transmitted when a transmission is repeated.
Activities
Creating and changing JIT calls is usually an automatic process that is triggered by inbound JIT calls via EDI, with different
external statuses. You can also process JIT calls manually .
Repeat Orders
Use
You can use this function if you receive a repeat order for a components group that has already been delivered. This can be the
case if a components group is damaged during transport or installation.
Prerequisites
In Customizing for JIT Inbound you have de ned the external status Repeat order and an appropriate status action network for
the corresponding JIT customer
Features
The JIT customer does not transmit the total scope of the original JIT call, but only the call components that he/she
wants to order again.
The system recognizes the repeat order by the external call number and the external status information transmitted. It
creates a new JIT call and indicates it as a repeat order.
The system treats repeat orders with the highest priority.
Components Group Determination
Use
The system carries out this function automatically, each time a JIT call is received. In this way it assigns each call component
transmitted to a components group type. The components group type then takes over the internal control of the call
12/12/2022
components.
With sequenced JIT calls for assemblies, the system assigns several call components to the same components group type. With
the other call types the call components and the components group type form a logical unit and the system therefore assigns a
different components group type to each call component.
Features
In the components group determination the system compares whether the characteristics of the call components match a
components group type. As soon as it can assign a call component, it continues with the next one. In the pro le for the
components group determination you can de ne with which priority the system should consider the various characteristics. The
system determines the relevant characteristics of the call components as follows:
JIT customer
The JIT customer is made up of the sold-to party and the partner description and can therefore be taken from the IDoc.
Unloading point and assembly location
The unloading point and, if necessary the assembly location, are also transmitted with the JIT call. The system can also take
these characteristics of the call components from the IDoc.
If you choose the value D Not relevant for determination – copy to JIT call for the assembly location and the unloading point in
the IMG act ivity De ne Components Group Determination then the IDoc values are copied to the JIT call after components
group determination has taken place. If you do not choose this value then the settings for the unloading point and assembly
location that you have maintained in the components group type are always displayed after components group determination.
It makes sense to use the setting D Not relevant for determination – copy to JIT call if you work with unloading points that are
constantly changing with a small number of components group types (without concrete unloading point or concrete assembly
location).
Components group material
The JIT customer generally transmits the components group material with a call. There are several ways in which you can de ne
the components group material of the call component before the components group determination.
You can realize an individual components group material determination using a customer exit. This is particularly recommended
for sequenced JIT calls for assemblies, due to the large number of variants.If you use the process for discrete materials, you can
transfer the material of the call components as a components group material.If you use the process for discrete materials and
exactly one components group material can be assigned to a call component, you can transfer the con gurable material of the
call component as a components group material. To do this you must have entered the con gurable material in the material
master of the call component in the tab page Basic data 2 in the eld Cross plant conf.mat.
Production version
You can also assign the production version using a customer exit. The production version allows you to assign two otherwise
equal call components to different components group types, to produce them on different production lines, for example.
Activities
You determine the components group determination in Customizing for JIT Inbound. If you want to carry out a more complex
components group material determination before the components group determination, you can do so in a customer exit.
Production
12/12/2022
Use
You require this function in order to release a components group for production and if necessary, to print a components list, that
accompanies the components group through production. The system generally carries out the production release, if your JIT
customer has transmitted a JIT call with the external status Production release . The production release is usually the signal
from the JIT customer, after he/she no longer changes the JIT call, including the sequence number.
Integration
In the process control you can transfer to production using the following actions.
Description Action
Transfer to production PIN
Print the component list PCOM
Transfer to production and print the component list (PIN+PCOM) PINP
Reprint the component list REPR
Generate and assign grouping info CGRP
Prerequisites
In your process control you have permitted the appropriate action for changing the current internal processing status.
If you want to print a component list, you have determined a print control in Customizing for JIT Inbound. If you want an
individual print formatting, you can create this in a customer exit.
If you also want to print the BOM components in the call components, you have selected the indicator Trigger in the basic data
in the production info.
Features
With action PIN you can release the components group for production. The action simply changes the internal processing
status of a call and does not trigger any other functions.
With action PCOM you can print the components list. Here the system formats all relevant data and makes it available in
an internal data structure. You de ne the action print formatting in the print control in Customizing for JIT Inbound. You
can, for example, use a SAPScript form or create your own individual layout using a customer exit. You can also print a
barcode on the component list, that you enter with a scanner in the production completion message.
With the interlinked action PINP you can both transfer to production and print the component list.
If errors occur when printing the component list, or you lose the paper in production, you can reprint the component list
using action REPR .
With action CGRP you can generate a grouping term and assign it to a components group, if you use the rack process,
for example.
Production Completion Message and Picking
Use
12/12/2022
You use this function to document the progress of a components group in production. As the lead times are often very short in
the JIT process, it is often sufficient to enter a completion message at the end of production. The completion message is made
by the employee at the last station of the production line. He/she has various options for selecting and sorting the components
groups. In this way he/she can enter the components groups of a packing rack together.
In the lean JIT process, a large picking process is usually avoided. However, you can print a pick list and then attach it to a
packaging rack, for example.
 Note
The completion message simply causes a change in status for the components groups concerned. You trigger the goods
movements and inventory postings by entering a back ush .
Integration
In the process control you can realize the production completion message using the following actions.
Description Action
Completion message from production POUT
Print a pick list PICK
Completion message and print pick list (POUT + PICK) POUP
Report scrap of components group SCRA
Report missing part NIO
Prerequisites
In your process control you have permitted the appropriate action for the current internal processing status of the
components group.
If you want to print a pick list, you have determined a print control in Customizing for JIT Inbound.
Features
You usually carry out the completion message with the progress con rmation . Here you can carry out the completion
message aggregated for a number of components groups. You can enter the number of components groups per
message entry in the initial screen. The system proposes the next components groups to be entered. If, for example, a
components group is shown as lacking quality and has to be reproduced, you can deselect this components group and
thus it will not be marked as completed.
With action PICK you can trigger the print of a pick list in the completion message. In this way you can, for example, print
a label for each packaging rack. You can de ne a print control in Customizing for the print formatting and if necessary,
create your own format using a customer exit.
With the interlinked action POUP you can carry out the completion message and the pick list print together.
With action SCRA you can report a components group as scrap. The system then prints the components list of the
components group again with increased priority and the components group can be reproduced. In the back ush the
system does not automatically include the scrap parts. You can repeat the posting manually.
12/12/2022
With action NIO you can set a components group to park status, if it requires rework, for example. If the components
group is then reworked, you can then complete it.
In this example, a completion message is planned after production. If you have longer lead times, you can also enter
messages at later de ned work stations in the production. To do so, you have to de ne a process control in Customizing
for JIT Inbound. For each work station at which you want to enter a message, you require an internal processing status.
You also require your own actions that transfer the components groups to the internal processing statuses.
With the completion message, you can also assign the grouping term manually. In the JIT process the number of the
packaging rack is often assigned as the grouping information and the sequence within the packaging rack as the
grouping index.
Activities
You create a completion message, by entering a progress con rmation for example, with the action Completion message from
production (POUT ).
If you have printed a barcode on the component list, during transfer to production, you can also carry out the progress
con rmation with the barcode entry .
Back ush
Use
You use this function to post the goods movements for the call components. You can select any amount of components groups
and:
post the goods receipt of the call components and the back ush of the assembled BOM components, aggregated
post a stock transfer from the production storage location to the shipping storage location aggregated, if you obtain the
call components from a supplier, for example.
Integration
The system carries out the back ush with the functions from make-to-stock repetitive manufacturing. For more
information see the documentation for PP – Repetitive Manufacturing under Back ushing .
In the process control you can carry out the back ush using the following actions:
Description Action
Carry out back ush BFLU
Carry out back ush in the background BFLP
Carry out back ush and create delivery (BFLU + DELI) BFDL
Prerequisites
You have set the necessary master data for the make-to-stock repetitive manufacturing .
In your call control you have planned the appropriate action for the current internal processing status of the components
group.
12/12/2022
You have entered the production info in the basic data for each call component. In the production info, you determine
whether you want to back ush or transfer a call component.
Features
You can carry out the action for a quantity of components groups. The system carries out the repetitive manufacturing
back ush or the stock transfer for all call components.
If you transfer the call components, the system determines the storage locations according to the following:
If there is a components group material for the components group to which the call component is assigned, the system
determines the storage locations from the production version of the components group material.
If there is no components group material, or a production version has not been created for a components group
material, the system determines the production storage location from the material master of the call component, as the
issue storage location. It determines the shipping storage location from the call component’s scheduling agreement as
the receiving storage location.
With action BFLP you can carry out the back ush and the goods movements in the background. The entry template is
then immediately released and you can continue.
With the interlinked action BFDL you can also simultaneously create a delivery.
You can also implement a goods movement using a customer exit. In this case enter the goods movement in the
production info using a customer exit.
If you carry out an action for the back ush, the system lists the call components of all components groups and groups
the quantities. It then gradually reduces this list, by updating one call component after the other (asynchronous update).
If a call component cannot be updated, it remains in the list with an error message. You can reprocess the list and then
manually repeat the posting.
Activities
You carry out a back ush, by entering a con rmation message , for example, with the action BFLU.
If you want to reprocess possible errors in the back ush, choose Logistics Logistics Execution JIT-Inbound Basic
Data Follow-on Functions Reprocess Goods Movement.
JIT Processing with Handling Units

Use
In general you can implement JIT processing together with Handling Unit Management (HUM). JIT processing supports the
following four functionalities in relation to HUM:
Generate a handling unit for a stock transfer
You create a handling unit (HU) to be picked or put away in Warehouse Management. To do this you use the action CRHU
or DEHU.
Automatic generation of an HU during JIT delivery creation
You use this functionality if you want to pack a JIT call at the same time as you create the delivery. If you want to pack a
sequenced JIT call you use the action DELI to create the delivery. If you want to pack a summarized JIT call you use the
transaction JITK ( Delivery Operations to be Shipped ). The HU is then created automatically.
12/12/2022
Retrospective assignment of an existing HU to a JIT call
In this functionality a HU that has already been built (with reference to a JIT delivery schedule) is assigned to a
summarized JIT call. You make this assignment in transaction VL10HU . For more information see Create Outbound
Delivery for Handling Units and Assign HUs to Existing Deliveries .
Generation of a deliverable HU for a JIT call
To create a deliverable HU for a JIT call you use the action HUPP. You can delete an HU that has been generated in this
way using the action DEHU.
For more information on JIT processing with HUs and the individual processes see SAP Note 591388 .
For information on Handling Unit Management in general see packaging logistics .
Delivery
Use
With this function you can create a delivery for JIT calls, that you use as a basis for all processes necessary in shipping.
You can create a delivery for sequenced JIT calls or summarized JIT calls that you have selected in JIT monitoring.
In the delivery creation, you can add components groups to a delivery or remove components groups from a delivery.
You can create a delivery list for summarized JIT calls and then deliver them from this list.
Integration
The other shipping functions are not contained within the JIT Inbound environment. You can use the following components:
With the component SD - Message Control you can trigger the creation of the shipping documents and the shipping
noti cation.
With the component SD - Shipping you can post the goods movement from the shipping storage location and process
the delivery.
With the component SD – Transport you can create a transport.
With the component SD – Billing you can create a billing document.
For further information on invoicing and shipping, see the documentation in the module SD Sales and Distribution
Processing.
Features
The following functions are linked with the delivery creation:
The system updates the cumulative delivered quantity for each scheduling agreement item.
The system completes the relevant forecast delivery schedules or JIT delivery schedules.
If you have set packing in the delivery, the system automatically creates handling units.
If you have set the transfer of the external call numbers, the system automatically transmits the external call numbers
of the calls at header or item level in the IDoc in the delivery message.
12/12/2022
Create Delivery
Use
With this function you can create a delivery for any number of calls or components groups. In the delivery, the system does not
show the components groups, but the call components with the cumulated quantity above all components groups. If you deliver
assemblies, you can show the call components with the cumulated quantity in the delivery.
Integration
In the call control you can carry out the delivery using the following actions:
Description Action
Create delivery DELI
Create back ush and delivery BFDL
Prerequisites
In your call control you have planned the appropriate action for the current internal processing status of the components
groups.
On creating the delivery, you have made the entries necessary for the order combination (see also create JIT scheduling
agreements ).
In Customizing for JIT Inbound you have created a control pro le for the delivery and assigned it to the corresponding JIT
customer in the basic data. In this pro le you can also set that you want to transfer the external call numbers in the IDoc
of the shipping noti cation or that you want to generate HUs when creating the delivery.
In JIT Inbound, picking is not used as a rule, when shipping. However, in Customizing for JIT Inbound you can set, in the
Control pro le for the delivery , that you want to carry out picking.
Features
The system creates a delivery, in which it shows the call components cumulated of several components groups, using the order
combination. You can combine call components, that have the same JIT customer and the same unloading points.
Activities
You can create a delivery, by entering a progress con rmation for example, with the action Generate delivery (DELI).
For further information on invoicing and shipping, see the documentation in the module SD Sales and Distribution .
Displaying and Changing Deliveries
Use
You can use this function to display or change existing deliveries. You can also delete individual items from an existing delivery.
12/12/2022
You can also change and display deliveries using the standard transactions VL02N and VL03N . Actions DELD and DELR also
update the JIT data. Another advantage of the actions is that they are executed in the background they can be integrated in
your action control.
Integration
In the call control you can change deliveries using the following actions:
Description Action
Remove components groups from the delivery DELD
Delete delivery items using VL02N DELR
Prerequisites
In your JIT control you have planned the appropriate actions for the current internal processing status of the components
groups.
Features
To display a delivery, go to the delivery of a components group from JIT Monitoring . In the delivery choose Display JIT
calls . The system displays all the JIT calls for this delivery.
You can also select individual items in a delivery and display the appropriate JIT calls.
You can display the JIT calls for every billing document created (transactions VF02 and VF03 ) as long as these billing
documents were created for JIT calls.
If you are in change mode for a delivery, you can delete individual components groups from this delivery using action
DELD Remove components groups from delivery . To be able to do this, however, the goods issue must not yet have been
posted for this delivery.
Using action DELR you can delete complete deliveries or individual items from a delivery. Then the affected JIT calls are
no longer assigned to a delivery. You can then redeliver these calls.
Gradual Delivery Creation
Use
With this function you can add components groups to a delivery that already exists in the system, or remove components
groups from the delivery.
Integration
In the call control you can carry out the gradual delivery creation using the following actions:
Description Action
Add components groups to the delivery DELU
Remove components groups to the delivery DELD
12/12/2022
Prerequisites
According to the call control, the actions are permitted for the current internal processing status of the components
group.
The prerequisites for creating the delivery have been ful lled.
There is already a delivery for the same customer and the same unloading point in the system. Goods issue has not yet
been posted for this delivery.
You do not work with packing on creating the delivery. This function is technically not possible with the gradual delivery
creation.
Features
With action DELU you can add a components group that you have selected in JIT monitoring or in the progress
con rmation, to a delivery. The system searches a delivery with the same JIT customer and the same unloading point. In
the control pro le for the delivery, you can set, whether:
no goods issue can have been posted for this delivery
no goods issue can have been posted and no transport can have been created for this delivery.
If the system nds one or more deliveries it proposes them in a list.
With action DELD you can remove a components group that you have selected in JIT monitoring or in the progress
con rmation, from a delivery.
Packing on Creating the Delivery
Use
With this function you can automatically create handling units (HUs), when you create the delivery:
with sequenced JIT calls the system packs on the basis of the components groups and transfers all relevant call
components in the HU.
with summarized JIT calls the system packs on the basis of the call components and transfers these directly to the HU.
Integration
For more information see the documentation for the Packing and Loading in Shipping .
Prerequisites
In Customizing for JIT Inbound in the control pro le for the delivery, you have chosen the HU creation according to
packing instructions or customer exit and entered a packing dialog pro le. You have assigned the control pro le to the
corresponding JIT customer in the basic data.
You have created the packaging material.
If you want to create the HUs according to the packing instruction, you have
created the packing instruction for the components group material, for sequenced JIT calls.
12/12/2022
created the packing instruction for the material of the call component, for sequenced JIT calls.
created a packing instruction determination record for the shipping packing instruction, referring to the material and the
goods recipient, for example.
If you want to create HUs with a customer exit, you have de ned the logic in the corresponding enhancement.
If you deliver summarized JIT calls, the delivery must contain only one sort. This means the delivery may not include
several different materials.
Features
You can automatically pack sequenced JIT calls with the action DELI . In this case the system carries out the packing
instruction determination on the basis of the components group material.
You can supply summarized JIT calls from the list of operations to be shipped and automatically pack them in HUs. In this
case the system carries out the packing instruction determination on the basis of the call components.
You can also implement your own logic for packing using a customer exit.
Delivery List for Summarized JIT Calls
Use
You can use this function for delivering summarized JIT calls. You can display the summarized JIT calls due for delivery, in a list
and create the delivery from this list. In this way, you have a good overview of the labor required and you can change the delivery
quantity manually.
Integration
The list of operations to be shipped is a function of the component Logistics Execution – Shipping. For further information see
Collective Processing of Documents due for Delivery .
Features
You can display a list of summarized JIT calls due for delivery and from here, create a delivery in the background.
You can display the summarized JIT calls in the list, combined with other orders. The system colors the summarized JIT
calls in yellow.
You can create a user role for the list and assign it to your user.
The system only selects the calls (components groups) for the list, that are permitted in call control for the delivery.
In the delivery list, the traffic lights (red and yellow) inform you of the temporal priority of the shipping.
You can change the delivery quantity in the list manually, and thus deliver partial quantities.
In addition, you can select handling units (HUs) in the list of operations to be shipped, if you have already packed the call
components in production. You can then create the delivery on the basis of the HU.
You can pack the call components in the delivery in Handling Units.
Access Delivery List

12/12/2022
Use
With this function you can access the delivery list for processing documents to be shipped, from JIT Inbound.
Integration
In the call control you can call up the delivery list using the following actions:
Description Action
Create SumJC delivery from VL10 VL10
Create delivery from VL10 / without lock DELS
Prerequisites
In Customizing for JIT Inbound you have created a control pro le for the delivery and a control pro le for summarized JIT
calls and assigned them to the corresponding JIT customer in the basic data.
If your JIT customer does not transmit a planned dispatch time with the summarized JIT call, you have entered the lead
times for the simple delivery scheduling.
So that you can display the summarized JIT calls in this list, the action VL10 must be permitted for the current internal
processing status of the components groups.
Features
Action VL10 is an interlinked action , that contains action DELS , as a sub-action. If you create the delivery list, the system
selects all components groups for which action VL10 is permitted in call control. The actual functions are contained in the sub-
action DELS . This action is called up by the system nested. In this way you can interlink the action DELS with a self-de ned
action and you can print pick lists, for example.
Activities
Choose Logistics Logistics Execution JIT-Inbound Follow-on Functions Delivery Work list.
This takes you to the initial screen of the list and from here you can set the user role.
Set User Role for Summarized JIT Call

Use
With this function you can con gure the list of documents to be shipped, according to your requirements. For example, you can
group the call components under a common external call number or as a schedule line under the source document (scheduling
agreement). In addition, you can select handling units (HUs) if you have already packed the call components in production.
In the user role you also have to set that you want to select summarized JIT calls when accessing the list.
Integration
In SAP Standard there are already three user roles that are suitable for summarized JIT calls:
12/12/2022
User role JIT1 , which displays each call component in the list as an item under the original document.
User role JIT2 , which displays each call component in the list as an item under the external call number and the original
document.
User role VLHU for packaging logistics, which selects HUs that have already been realized and displays them under the
original document item and the delivery item. If you want to use this role, you must select the indicator Summarized JIT
calls in the role.
You can use these user roles or adjust them to your requirements. If you want to create your own user role, you can do so in
Customizing for Sales and Distribution under Logistics Execution Shipping Worklists Con gure List Pro le.
If you want to assign a user role to a user, see Establishing User Roles .
Features
The following settings are relevant for summarized JIT calls in the user role:
In the area Data Selection choose the indicator With Summarized JIT Calls , so that the system displays the
summarized JIT calls in the list. You can combine this indicator other indicators, such as With Sales Orders .
If you want to group call components of the summarized JIT call under the external call number and the number of the
scheduling agreement, you can choose the entry Customer Call Number and Original Document in the eld Header Item
Assignment . If you want to group call components under the number of the scheduling agreement, you can choose the
entry Original Document .
In the area With Handling Units you can choose the indicator Shipping: Deliver HUs if you want to display the HUs in the
delivery.
For more information on JIT Processing with Handling Units see SAP Note 591388 .
Delivering Partial Quantities
Use
With this function you can change the delivery quantity in the list of documents to be shipped. This means that you can deliver
partial quantities of a call, if the quantity called is not available.
Prerequisites
In Customizing for JIT Inbound in the control pro le you have set the Quantity change or the Quantity change with
partial quantity splitting .
You have assigned this control pro le to the corresponding JIT customer in the basic data.
Features
With this function you can change the delivery quantity manually in the list of documents to be shipped. Depending on the
settings in the control pro le for the summarized JIT call, the system proceeds as follows:
Quantity change permitted
You can change the quantity and the system automatically transfers the new quantity to the item of the relevant summarized
JIT call. This means that the system assumes that your customer includes the remaining quantity with a following summarized
12/12/2022
JIT call.
Quantity change permitted with partial quantity splitting
You can change the quantity and the system automatically transfers the new quantity to the item of the relevant summarized
JIT call. In addition, it creates a new item with the remaining quantity in the call. Therefore, you can use this item to deliver the
remaining quantity later.
If the remaining quantity is not to be delivered, you can de ne the new internal processing status "park status". Then you can
decide later whether this remaining quantity is to be delivered later or not.
If you create a new call item for a call and make a partial quantity delivery but you do not want to deliver the remaining quantity,
you can set a "parking status" for this new call item. You can then retrieve this remaining quantity to the active delivery worklist
status or delete it.
 Note
Note that when making any changes to quantities, you respect the tolerances de ned in the scheduling agreement.
If, for example, you have a call for 100 pieces, the tolerances have been de ned at +/- 10% and you want to deliver 89 pieces,
the system will not create a delivery as you are not within the allowed tolerance level.
Quantity change not permitted
You are not allowed to change the quantity. For additional quantities of a material, you have to create a new call.
Delivery Split
For delivery grouping in summarized JIT calls you have the following options:
Standard splitting : The summarized JIT calls grouped during processing are collected into one delivery as long as they
have the same external call number and no standard splitting criterion (for example, grouping indicator at scheduling
agreement item) that hinders such a grouping.
Grouping mandatory (as Seq.JC) : The system checks whether summarized JIT calls with the same external call number
can be grouped. The delivery is not created if a grouping is not possible (for example, due to a grouping indicator). This
setting is mandatory for delivery creation with already existing Handling Units (packed in production).
Split per grouping information : For summarized JIT calls grouped during processing, different deliveries are created
depending on grouping information. The grouping information is copied to the delivery header as an external
identi cation of the delivery.
Split per external call : For summarized JIT calls grouped during processing, different deliveries are created depending
on grouping information. The external call number is copied to the delivery header as an external identi cation of the
delivery.
Item split per summarized JIT call item : For summarized JIT calls grouped during processing, separate delivery items
are created per item (= per row in transaction JIT1 Receipt of JIT Calls ).
Item split per grouping information : For summarized JIT calls grouped during processing, separate delivery items are
created per grouping information.
Item split per external call number : For summarized JIT calls grouped during processing, separate delivery items are
created per external call number.
12/12/2022
Split per external call number and item split per grouping information : For summarized JIT calls grouped during
processing, different deliveries are created per external call number. The external call number is copied to the delivery
header as an external identi cation of the delivery. Within a delivery, a separate delivery item is created for each
grouping information.
Delivering Operations to be Shipped
Use
This procedure describes a possible procedure for delivering summarized JIT calls. The procedure may vary, depending on your
user role.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Follow-on Functions Delivery Summarized JIT Calls Due for
Delivery (Transaction JITK).
This takes you to the initial screen of the list and from here you can set the user role.
2. In the eld Shipping point enter the relevant shipping point and if necessary, limit the delivery creation date. The system
uses the planned shipping time of the components group for the delivery creation date.
3. Choose the tab page User Role .
4. In the eld Role , enter a user role and then choose .
The system displays the settings of the user role.
5. If you want to change the user role in the current session, delete the selection with the indicator Use list pro le and then
choose .
The system also displays the tab page Summarized JIT call , if the indicator With summarized JIT calls is de ned in the
user role.
If you want to display the user role in Customizing, choose Role .
6. If you want to limit the selection further, choose the tab page Summarized JIT call and enter the relevant data.
7. Choose .
The system displays the list of operations to be shipped. The rows that contain summarized JIT calls are displayed in
yellow.
The status traffic lights at the beginning of each row show the priority of the shipping (yellow and red). You de ne the
time periods for the traffic lights in Customizing in the control pro le for the summarized JIT call.
8. If you want to deliver a partial quantity , you can manually enter the quantity changed for an item.
9. Select an item and choose Background.
If there are additional call components for the summarized JIT calls of the items selected, the system initially displays
this call component in a dialog eld. You can also select these call components and then create the delivery.
 Note
You can only create deliveries in the background. It is not possible to process summarized JIT calls online.
10. If you want to display a delivery creation log, choose .
12/12/2022
11. Continue by delivering further calls, or choose to exit processing.
Result
The system assigns to the components groups of the call components the internal processing status, which is de ned in the call
control according to action VL10 . You can monitor the process with JIT monitoring .
Goods Issue Posting for a Delivery
Use
You can use this function to post the goods issue for a delivery or to reverse this posting. Using the action GOIS Post Goods
Issue , you can post the goods issue for a delivery from JIT Monitoring. Using the action GOCC Reverse Goods Issue Posting you
can reverse goods issue from JIT Monitoring.
However, you can still use transactions VL02N and VL06G to post or reverse goods issue as well. If you use the standard
transactions for posting goods issue, the action GOIS is executed automatically. The internal status of the call is updated.
Integration
You can complete the goods issue posting in JIT call control using the following actions:
Description Action
Post goods issue GOIS
Reverse goods issue GOCC
Prerequisites
In your JIT control you have planned the action GOIS or GOCC for the current internal processing status of the relevant
components groups.
If you want the system to update the internal status of a call when you post goods issue you must set the Status Update
indicator in Customizing for JIT Inbound under De ne Control Pro le De ne Control Pro le for the Delivery.
Activities
You can post the goods issue for a delivery by executing action GOIS in JIT Monitoring, for example. Note that for this action all
the components groups contained in a delivery must be selected.
Updating the Statistics in the BW
Use
With this function you can update the JIT call data in the SAP Business Information Warehouse (BW), to carry out an analysis for
JIT Inbound. The system only transfers data to the BW that is important for the evaluation. This includes, for example, the data
of the JIT customer and the components group data.
In the BW you have evaluation options, such as:

12/12/2022
the number of JIT calls in a speci c period of time or per JIT customer
the number of components groups transmitted
the number of call components per components group
the number of repeat orders per components group
the frequency of a speci c variant or of a components group material
For more information on evaluations, see the documentation for the Business Information Warehouse.
Integration
In call control you can update the statistics in the BW with the following action.
Description Action
Update the data in the Business Information Warehouse STAT
Prerequisites
You have installed the SAP Business Information Warehouse.
In your call control you have permitted the action STAT for the current internal processing status of the components
groups.
Features
You determine when the data is to be transferred, using the scheduler in the SAP Business Information Warehouse. The
system then updates all components groups, whose current internal processing status permits the action STAT .
The system extracts the necessary data to ll the BW InfoSource of the call header and the BW InfoSource of the
components groups and the call components.
Completion
Use
With this function you can indicate a JIT call as completed. A JIT call is usually completed after your JIT customer has con rmed
the delivery and has paid the billing document. You can then select all JIT calls in the delivery using the delivery number and
mark them completed.
Integration
You can complete the process in the process control with the following actions:
Description Action
Complete call/components group FINI
Prerequisites
12/12/2022
In your process control you have planned the action FINI for the current internal processing status of the relevant components
groups.
Features
The action FINI simply causes a status change and does not trigger any further functions.
Activities
You can complete JIT calls by carrying out action FINI in JIT monitoring , or in the progress con rmation .
Reorganization
Use
With this function you can delete inbound and outbound JIT calls from the database. The high volume of JIT calls, common in the
automotive industry, means that you will soon have a large amount of data in the system. Reorganization means that you can
no longer completely delete the data from the database.
 Note
If you want to access the data of the JIT calls again later, you can also archive it delete it from the database in the archiving
session.
Note that when you are reorganizing inbound JIT calls, all the forwarded outbound calls are automatically included in this
reorganization.
When reorganizing outbound JIT calls, the system checks whether the selected calls have the goods movement status C
Completed . If this is not the case, the system terminates the reorganization.
Integration
In JIT call control you can carry out reorganization using the following actions:
Description Action
Reorganize JIT data REOR
Delete outbound JIT calls OREO
Prerequisites
In your call control you have planned action REOR or OREO for the current internal processing status.
Features
The system deletes all the data from the database that belongs to the selected JIT calls.
Actions
12/12/2022
You can execute reorganization by creating a Progress Con rmation using action REOR or by carrying out action OREO in JIT
Monitoring Outbound .
Printing JIT Calls
Use
You use this function to print the JIT call data. You can use the different options for formatting the printout and the various
forms to adapt the print function to suit your requirements.
Features
The print control in JIT processing usually depends on both actions and users. This means you can assign a speci c print mode
to individual actions and individual users. The individual print parameters are dependent on the plant and production line. You
make the settings for print control in Customizing for JIT Inbound.
Print Formatting
You usually have the following options for formatting your printout:
SAPscript : For more information see also: Controlling the Print Output
Smart Forms: For more information see SAP Smart Forms .
 Note
You should note that for new functions only SAP Smart Forms are supported.
Output to local work le: The data for a certain JIT call is saved to a local le.
Express Mail : You can send the data for a call to a user or to a distribution list, for example.
Printout without form formatting: In this print mode, only the raw data, that is only the speci c call data, is printed
without the form data.
Print formatting using customer exit: In enhancement JIT03_03 you can use the following customer exits:
Customer Exit Description
EXITJIT03_03 Using this customer exit, you can format the printing of the
components list.
EXITJIT03_04 Using this customer exit, you can format the printing of the pick
list.
EXITJIT03_014 Using this customer exit, you can modify the spool le created.
See also: Printing with forms.
Printing with Forms
In general, a form should correspond to the data of the action for which you want to de ne the printout.
The following templates are delivered in the standard system:
12/12/2022
JIT_ML001: You use this template if you want to create the form for a component list. This template is provided for
actions PINP and PCOM.
JIT_R001: You use this template if you want to create the form for a pick list. This template is provided for the action
PICK.
JIT_SW001: You use this template if you want to create the form for a components group switch list. This template is
provided for the action PSWC.
If you want to adjust your own forms to suit a JIT action, you can do so using SAPscript or SAP Smart Forms. To do this using
SAPscript choose Tools Form Printing SAPscript Form.(Transaction SE71).
For SAP Smart Forms, choose Tools Form Printing Smart Forms.
You can create your own forms using the above-mentioned customer exits.
Printing Actions
The following printing actions are available:
Action Description
PCOM/PINP Print the component list
REPR Reprint the component list
PICK Print the pick list
PSWC Print the list for the component groups switch
For more information, see Actions .
Control and Monitoring
Use
You can use these functions to control, monitor and access JIT calls in your system. It is particularly necessary with sequenced
JIT calls, that you have constant information about the processing status of the calls, and that you can process this as required.
Features
You can process the JIT calls manually.
You can evaluate the JIT calls with JIT monitoring or enter the processing progress with a progress con rmation.
You can evaluate the requirements situation with the component requirements list.
You can carry out a requirements match with forecast delivery schedules or JIT delivery schedules.
In an emergency you can work with special functions.
You can create internal calls and after production store them in a buffer storage location.
Processing JIT Calls Manually
12/12/2022
Use
You can use this function to create, change, display or simulate JIT calls manually. This can be useful, if you want to check the call
structure of a call or if a customer informs you of a change to a call by telephone. In addition, you can also create internal calls .
 Note
There are also special functions available for emergency operation , such as when there are problems with the EDI
connection.
Prerequisites
You have created the necessary master data in the SAP system.
You have de ned the basic data for JIT Inbound.
Features
You can process all types of call with these applications. The maintenance modes EDI, components group and call component
are available for processing. You can process the JIT calls manually as follows:
Create JIT calls
This application corresponds to the Inbound EDI. You can create a new call or change all the data of an existing call.
Change JIT calls
You can change speci c data for a JIT call that you have already created. This includes the sequence number, the
additional information, the external status, the customer material or the quantity of the call components.
Display JIT calls
You can display JIT calls that are already created.
Simulate JIT calls
In this application you can process all the data for a call. However, you cannot save the changes. This function is useful for
testing the components group determination.
Maintenance Mode
Use
With this function you can display different views for processing JIT calls and their call structures. You can select the various
views depending on the call type that you want to process.
Features
The following maintenance modes are available:
EDI
12/12/2022
This mode is presented as the actual inbound IDoc. It is divided into the areas call header, components groups and the call
components. You enter the call header and then the call components. Then the system can carry out the components group
material determination, to assign the call components to the components groups.
Components groups
This mode is useful if you receive calls for assemblies. After you have entered the call header in the header data you can enter a
components group directly. You then assign the call components to the components group.
Discrete material
This mode is useful if you receive calls for discrete materials or summarized JIT calls. As the components groups and call
components can be considered as a logical unit, enter only the call components here. The system does not display the area for
the components groups.
Activities
You can select the maintenance mode in the entry screen in the list eld Maintenance mode .
You can also enter a maintenance mode as a proposal value for a JIT customer in the basic data.
Working in the Maintenance Mode EDI
Use
This mode is presented as the actual inbound EDI. It is divided into the areas call header, components groups and the call
components. You enter the call header and the call components. Then the system can carry out the components group
determination, to assign the call components to the components groups.
This procedure describes how to create a JIT call. Changing, displaying and simulating all function in the same way and you can
only make small changes to the data.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound JIT call Create.
2. This takes you to the initial screen.
3. Enter the data of the JIT customer in the elds Sold-to party and Partner description .
4. In the eld Call type , specify whether you want to create a sequenced JIT call, a summarized JIT call or an internal call.
5. In the eld Ext.call number enter the description of the call.
6. If you want to create a call as a repeat order for a call which has already been delivered, select the indicator Repeat
order .
7. In the list eld Maintenance mode choose EDI .
8. Choose .
This takes you to the screen JIT Call Inbound.
1. Enter the rest of the call header data.
12/12/2022
2. In the area Call components enter all call components of the call. This means that the external status should be the
same for all call components that belong to a components group.
3. If you want the system to propose data of an existing call, choose Propose call and enter the call in the following
dialog eld.
4. If you want to carry out a mass change for the call components, select the call components and choose Proposal
item. In the subsequent dialog box, you can propose data for speci c elds.
5. If you have entered all call components, choose .
The system carries out the components group material determination and assigns the call components to the components
group types.
1. Choose to create the call in the system.
Working in the Maintenance Mode Components Groups
Use
This mode is useful if you receive sequenced JIT calls for assemblies. After you have entered the call header in the header data
you can enter a components group directly. You then assign the call components to the components group.
Procedure
This takes you to the initial screen.
3. In the eld Ext.call number enter the description of the call.
order .
5. In the list eld Maintenance mode choose Components groups .
6. Choose .
This takes you to the screen JIT Call Inbound.
dialog eld.
2. Enter other data of the call header, such as the sequence number.
3. In the area Components groups , enter a components group and its external status.
4. If you want to add further components groups, choose and enter the components groups.
5. Choose .
12/12/2022
The system displays the screen area Call components and transfers the components group materials into the table.
1. Enter the call components for the components groups. To add an additional row to a components group, select the rows
of the components groups and choose .
Working in the Maintenance Mode Discrete Material
Use
This mode is useful if you receive calls for discrete materials or summarized JIT calls. As the components groups and call
components can be considered as a logical unit, enter only the call components here. The system does not display the area for
the components groups.
This mode is presented as the actual inbound EDI. It is divided into the areas call header and call components. You enter the call
header and the call components. Then the system carries out a components group determination to assign the call components
to the components groups internally.
Procedure
2. This takes you to the initial screen.
5. In the eld Ext.call number enter the description of the call
order .
7. In the list eld Maintenance mode choose Discrete material .
8. Choose .
9. This takes you to the screen JIT Call Inbound.
dialog eld.
11. Enter the rest of the call header data.
12. In the area Call components enter all call components of the call. This means that the external status should be the
same for all call components.
13. Choose .
The system carries out the components group determination and assigns the call components to a components group types in
the background.
12/12/2022
JIT Monitoring
Use
With this function you can monitor the processing of the JIT calls. You have an overview of all current or past call processing and
also carry out actions with calls or components groups. In the initial screen you can select calls according to your own criteria.
You can:
Display all JIT calls beginning with an external call number
Display all JIT calls of the last 24 hours, that were re-ordered
Display all JIT calls at a speci c assembly location.
You can then display detailed data for the calls selected, or carry out actions to complete or reorganize calls.
 Note
You can also use JIT monitoring for problem situations. For this purpose, there are several other functions available (see also
Emergency Operation ).
Features
You can display JIT monitoring in the graphic JIT cockpit or in list form. For both formats, you can determine which calls
should be displayed based on extensive selection criteria.
You can de ne the structure of the list and the graphic.
You can monitor the frequency of calls arriving by EDI with a signal monitor.
In addition to the data of the call header and the call components, you can display the following detailed data:
Additional texts for the call
Material data of the call components
Detailed data for the JIT Customer
You can export the list of calls in a le of the following types:
Spreadsheet
Text processing
HTML
You can select calls or components groups and apply actions to them. The system only offers you actions that are
permitted for the internal processing status of a components group, according to the call control .
You can specify the time zone, for which you want to evaluate calls in JIT monitoring. This can be useful, if your JIT
customer is in a different time zone.
The initial screen for JIT monitoring is rather complex. The selection options are very comprehensive. To make it easier to
access JIT monitoring you can use a selection variant to con gure an initial screen that suits your own requirements. If
you choose transaction JITMX the system displays an initial screen for JIT monitoring that lists all the possible selection
criteria. You can use a selection variant to hide the selection criteria that you do not need.
12/12/2022
Carry Out JIT Monitoring in a List
Prerequisites
If you want to sort the list with a speci c sort variant, you must have already de ned this in Customizing for JIT Inbound.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Control Data Monitoring List.
This takes you to the initial screen of JIT monitoring.
2. Enter the selection criteria on the tab pages Status, Call header data, Components groups and Call components.
 Note
In transaction JITMX all possible selection criteria are listed. Using a transaction variant, you can con gure an initial
screen for JIT monitoring that suits your own requirements.
3. If you want to determine the structure of the list, choose Settings. This takes you to a dialog box, in which you can:
4. As a default, the system uses your user’s time zone. If you want to set another time zone, choose Time zone .
5. Choose .
This takes you to the list, in which all the calls that correspond to the selection criteria are displayed.
6. If you want to carry out an action, select the calls or components groups you desire and choose Actions.
This takes you to a dialog box listing the actions that are possible according to the call control. A traffic light shows you
whether the actions can be applied to all components groups or only for some of them.
Select an action and choose Apply and go back or Apply , to update the list at the same time.
The system carries out the action with the possible components groups.
7. You can display detailed information on the individual dates, by double clicking.
8. You can also process a JIT call, by selecting it and choosing Goto JIT call Create/Change/Display .
This takes you to the application for processing the call.
9. Choose to end JIT monitoring.
Graphic JIT Monitoring in the JIT Cockpit
Use
You use this procedure if you want to carry out the JIT monitoring in the bar chart of the JIT cockpit .
Prerequisites
You have made the basic settings .
You have set the subscreens .
You may have created a display variant .
12/12/2022
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Control data Monitoring JIT Cockpit.
The system displays the JIT cockpit in the display variant, that is assigned to you as an entry variant.
1. You can display detailed information on a call as follows:
1. If the screen area Detailed information on the JIT calls is not displayed in the, choose Show details .
2. The system displays the call structures of all JIT calls selected, in an overview tree.
3. You can display detailed information on a call header, a components group or a call component, by double clicking on it.
This takes you to a dialog eld, from which you can move to other relevant areas, such as the scheduling agreement.
1. You carry out actions by selecting the relevant calls in a subscreen and choosing Action selection.
This takes you to a dialog eld, in which actions are offered, that are permitted for the relevant calls.
1. The basic settings and the settings in the subscreens can be changed as desired.
Signal Monitoring
Use
With this function you can monitor the frequency of calls arriving by EDI. The signal monitor tells you when the last call for a
speci c external status arrived by EDI. Using your empirical values, you can establish from the time difference between the
calls, whether there may be problems in the EDI connection.
 Example
If, during normal operation, a call enters every 5 minutes with the external status Production release , and now the last call
was received 10 minutes ago, there is likely to be a problem.
Prerequisites
You have selected the indicator Signal monitor active in the basic data for the relevant JIT customer.
Features
The system displays the time in a table that the last call with a speci c status was received and created. From the entry,
you can establish the sold-to party, the partner description and the external status information.
The system displays the time that has elapsed since the call was received.
The system automatically updates the display every 60 seconds.
You can implement a connection to the work ow using a customer exit. You can, for example, monitor the time difference
from the last call and when a speci c value has been exceeded, you can send an express mail.
Activities
12/12/2022
Choose Logistics Logistics Execution JIT-Inbound Control Data Monitoring Signal Monitor. This takes you to
the signal monitor table.
iViews for JIT

You use iViews to display information from the JIT component in the Supplier Workplace .
iViews provide the JIT controller with a fast overview of selected information.
 Note
To be able to use iViews in the Supplier Workplace, you have to release them for the internet in the SAP Web Repository .
Choose Tools Web Development Web Repository .
This takes you to the screen SAP Web Repository: Initial Screen .
Choose Internet Release Reports. .
This takes you to the screen Releasing Reports and Function Modules .
Enter the name of the report and choose .
Four different iViews are available for the JIT component in SAP Automotive .
Name Description Report
Lean JIT Monitoring This iView provides you with a quick RJITWPL001
overview of the number of calls and
components groups with a certain status or
for a speci c customer. Therefore, you can
recognize critical situations fast.
You can use the following selection criteria,

for example: Sold-to party, partner
description, unloading point, assembly
location or plant.
For more information, see JIT Monitoring .
Signal Monitor Using this iView, you can display a list RJITWPL002
which shows the last call for a certain
manufacturer as well as for an external
status. For this call, you can display the
time of receipt, the time that has since
passed and the accompanying IDoc.
For more information, see Signal Monitoring

.
12/12/2022
Name Description Report
List of extra copies orders This iView provides you with an overview of RJITWPL003
all extra copies orders. The extra copies
orders are displayed with statuses.
The following selection criteria are

available, for example: Sold-to party,
partner descritpion and plant(of supplier).
For more information, see Extra Copies

Order .
JIT Alert Monitor This iView provides you with an overview of RJITWPL004
the key gures which, if reached, causes a
critical situation – such as a certain number
of postprocessing records, for example.
Using this iView, you can see how many
postprocessing records exist and take
precautionary measures, if necessary.
The following selection criteria are

available, for example: Plant and ABC
indicator for the corresponding material. You
can use tolerance limits to control lights
which can also be displayed.
For more information, see Reports .
IDoc Monitor for Inbound JIT Calls
Use
You can use the IDoc Monitor for Inbound JIT calls to observe the processing of incoming IDocs. In this way you have an overview
of the processing of all current and previous JIT calls. You can easily identify IDocs containing errors and edit them if necessary.
The IDoc Monitor combines the technical function (IDoc) with the task function (JIT call).
Integration
From the IDoc Monitor you can directly trigger the processing of the calls/IDocs.
Prerequisites
If you want to de ne a particular message type for certain message you must have carried out the IMG activity De ne Message
Type in Customizing for JIT Inbound.
Features
The IDoc Monitor provides you with an overview of the processing of incoming IDocs.
The following table gives you an overview of the individual symbols and their meanings.
Symbol Meaning
, , Give the overall status of an IDoc.
12/12/2022
Symbol Meaning
Dialog You can use this function to process an IDoc in the dialog.
Background You can use this function to process an IDoc in the background.
You can use this symbol to logically delete an IDoc.
IDoc Displays an IDoc in a list.
Displays the status history for an IDoc.
Refreshes the IDoc Monitor data.
Indicates that text is available on header and/or item level.
Displays a legend of the symbols used.
Activities
1. Choose Logistics Execution JIT-Inbound Environment IDoc IDoc Monitor for JIT Calls (Transaction EMJIT).
This takes you to the screen IDoc Monitor for Incoming JIT Calls .
2. Enter you selection criteria and choose .
Progress Con rmation
Use
With this function you can enter the progress of JIT calls in your plant and thus document the processing status. You can carry
out an action for a quantity of JIT calls or components groups and transfer them to a new internal processing status.
This function is generally only relevant for sequenced JIT calls, which you deliver in sequence. For summarized JIT calls the
tracking of the processing status of individual call components is usually not necessary.
The progress con rmation is usually used by an employee, who enters a completion message for the components groups, after
production. The employee assigns the components groups produced to a transport rack, according to their sequence number,
and enters a completion message.
You can also carry out other actions with the completion message, such as:
Trigger back ush
Create delivery
Complete JIT call
Prerequisites
If you do not want to sort the JIT calls by sequence number, you must have de ned a sort variant in Customizing for JIT Inbound.
Features
You de ne the type of progress con rmation by the action that you enter in the initial screen. The system then only
selects components groups that this action can be applied to.
12/12/2022
You can enter a sort variant in the initial screen, with which the system sorts the calls.
The system automatically determines the next sequence numbers to be completed. You can also specify a sequence
number as an entry point. This means that you can repeat the completion message for calls, for example.
You can specify an entry unit. The entry unit is the number of calls that you want to process as a package in the progress
con rmation. This means that you can enter the capacity of your transportation racks as an entry unit, and then carry
out progress con rmation for entire transport racks in one work step. In addition to the entry unit, you can display a
forecast of the subsequent calls in the list.
The system selects all components groups in the list that you can enter in one work step and displays them with a green
traffic light. You can remove a call or individual components groups from the selection to exclude them from the progress
con rmation. The traffic light turns red if the whole call has been excluded, and yellow if individual components groups
have been excluded. You can also display a legend to the traffic lights in the upper screen area.
If you enter several production lines in the initial screen, the system groups components groups with the same sequence
number, to one call. This can be of use if you produce the left wheel of a vehicle on one production line and the right
wheel on another production line, for example. Otherwise the system groups the components groups per production line.
However, a cross-line plausibility check does not take place.
As well as the action entered in the initial screen, you can also carry out special actions per components group. The
system proposes all actions that are permitted in the process control for the current internal processing status of the
components group as special actions.
You can also specify other internal processing statuses in the initial screen, for which the selected action is not
permitted. The system then also displays these in the list. However, by doing this, you can ensure that gaps in a
transportation rack, caused by scrap for example, also appear in the list.
You can display a dialog box for each JIT call with detailed data for the call.
You can select, in the settings, that the system processes the calls directly, without displaying the list beforehand.
In the settings you can select that you want to specify the grouping term in the progress con rmation. You can then
specify the number of the packing rack as grouping information in the progress con rmation. This means that you will
later be able to establish which components group you have shipped in which packing rack.
You can preset a time zone for the call display.
The initial screen for progress con rmation is rather complex. The selection options are very comprehensive. To make it
easier to access progress con rmation you can use a selection variant to con gure an initial screen that suits your own
requirements. If you choose transaction JITFX the system displays an initial screen for progress con rmation that lists
all the possible selection criteria. You can use a selection variant to hide the selection criteria that you do not need.
Enter Progress Con rmation in a List
Prerequisites
If you want to sort the list with a speci c sort variant, you must have already de ned this in Customizing for JIT Inbound.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Control Data Progress Con rmation List.
This takes you to the initial screen of the progress con rmation.
1. Enter the desired action in the eld Activity to be performed .
12/12/2022
2. If you want to carry out the progress con rmation for a speci c entry unit, enter this in the eld Entry units . If you want
to display a forecast of other calls, alongside the entry unit, enter the desired number of calls in the eld Forecast units .
3. In the tab pages Customer, Production and Rel. data , enter the relevant data.
4. If you want to make further settings, choose Settings .
5. This takes you to a dialog eld, in which you can:
set, in the eld Process action directly , that the system processes the action without displaying the list beforehand.
This is useful if you want to carry out the progress con rmation with a variant in the background.
select the aggregation of the data on call level or on the level of the grouping information, in the eld Aggregation level .
In the eld Additional internal processing statuses , you can specify that you want to ll gaps in the sequence with the
additional internal processing statuses. You could, for example, ll gaps in a transport rack, that have occurred because
of scrap. Components groups that have come up as scrap, are still listed for this processing status, but cannot be
processed.
In the eld Permitted special actions you can limit the special actions that can be carried out.
In the eld Grouping maintenance , you can specify that you want to enter the grouping term manually in the list in the
progress con rmation. Then, in the progress con rmation you can enter, for example, the number of the shipping rack as
grouping information for the components groups displayed. This means that you will later be able to establish which
components group was shipped in which rack.
In the eld Sort variant , you can enter a sort variant, which determines how the calls are sorted in the list. If you want to
sort the calls in the sequence that they are received, you do not require a sort variant.
In the eld Display variant , you can enter a variant that controls the format of the list.
1. Choose .
2. This brings you to the list of the progress con rmation, in which you have displayed either all calls selected or the entry
unit, sorted by sequence number or sort variant.
3. Choose Show/hide legend , to display the legend for the traffic lights.
4. Choose to execute the action for the calls or components groups selected.
The system carries out the action with the components groups selected and sets the new internal processing status of the
components groups. The components groups disappear from the list and the next entry unit is displayed in the list.
1. Choose to display a list of possible special actions in a dialog box. If you want to carry out a special action, select it
and then choose .
The system carries out the special action with the components groups selected and sets the new internal processing status of
the components groups. The components groups disappear from the list and the next entry unit is displayed in the list.
1. If you want to carry out the progress con rmation from a different sequence number as an entry point, choose and
enter the sequence number in the dialog box.
2. To leave the progress con rmation, choose .
Graphic Progress Con rmation in the JIT Cockpit
Use
12/12/2022
You use this procedure if you want to carry out the progress con rmation in the bar chart of the JIT cockpit .
You carry out this progress con rmation in the rst subscreen (back ush window) of the JIT cockpit. It is usually sufficient to just
display this window. As administrator you can make the settings for this subscreen once and save them in a display variant. You
then assign this display variant to the employees in production, who enter the progress con rmation. Depending on the
authorization there are various functions in the progress con rmation.
Prerequisites
You have made the basic settings .
You have set the subscreens . If you want to carry out the progress con rmation for a speci c number of JIT calls or
components groups, you can enter the number in the settings of the subscreen. To do so, double-click in the screen area
Settings on the nodes of the subscreen.
You may have created a display variant and assigned it to the corresponding user.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Control data Progress con rmation JIT Cockpit.
The system displays the JIT cockpit in the display variant, that is assigned to you as an entry variant.
1. To enter the progress con rmation for all calls that are displayed in the rst subscreen, choose Process .
1. If other actions are permitted for the internal processing status of a components group, you can choose Special actions .
This takes you to a dialog eld, in which actions are offered, that are permitted for the components groups selected.
To carry out a special action, select an action and choose Apply and go back or Apply .
1. If you want to choose another action, choose Change action and enter the desired action in the dialog eld.
1. If you want to display a component list in HTML format, choose Show component list .
2. You can display detailed information on a call as follows:
If the screen area Detailed information on the JIT calls is not displayed in the, choose Show details .
The system displays the call structures of all JIT calls selected, in an overview tree.
You can display detailed information on a call header, a components group or a call component, by double clicking on it.
This takes you to a dialog eld, from which you can move to other relevant areas, such as the scheduling agreement.
Barcode Entry
Use
You require this function if you do not select the components groups for the progress con rmation in a dialog, but enter them
using a barcode scanner. You can import several calls or components groups with the scanner and carry out the action for this
group.
12/12/2022
 Note
Make sure that the selected action is only applied to the components groups that correspond to your selection criteria in
situations where several components groups exists in a call, for example.
Integration
In Customizing for JIT Inbound under De ne Barcode Quali er , you de ne which information you use to identify the entry
objects These quali ers determine which identifying attributes of the entry object you print on the barcode. The following
attributes are possible:
the internal number of the components group
the internal number of the call
the grouping information of the call or the components group
the external call number
the customer’s sequence number
the material number of the call component (for barcode entry (speci ed))
The entry object always consists of two parts:
the barcode quali er, which speci es the identifying attribute of the object in question.
the following barcode identi er, that speci es the actual identifying attribute of the object.
 Example
You want to enter the progress con rmation for a components group/call component with the material number 2345 using a
barcode. The object quali er for the material number has key number 1. Consequently, barcode 12345 must be printed on the
components group.
You can print the barcodes with action PCOM (print components list). To do this you can select the print format with SAPScript
in Customizing for JIT Inbound under De ne Print Formatting. The standard form JIT_ML001 already contains the text elements
for printing the barcode.
Features
You can update several entry objects with the barcode scanner. You can trigger the speci ed action manually, or the
system can automatically carry it out after an entry unit, which the system proposes as default. In this way, you can
specify the capacity of a packaging rack as an entry unit and automatically start the action when the rack is full.
You can enter the entry units (not speci ed) in any sequence or you can choose barcode entry. When entering speci ed
barcodes, you can determine the next object to be entered, using selection criteria and thus preset a sequence of entry
objects.
You can de ne transaction variants for the applications and thus hide elds in the dialogs.
You can also create additional documentation data such as batch numbers or serial numbers, for example.
Entering Bar Codes

12/12/2022
Use
You use this procedure, if you do not want to specify a sequence for the components groups or calls, when you enter bar codes
for the progress con rmation.
Prerequisites
You have de ned the object quali ers in Customizing for JIT Inbound.
If you want to use transaction variants in the application, you must de ne these rst. To do this, choose transaction
SHD0 .
Procedure
1. Choose Logistics Logistics Execution JIT Inbound Control Data Progress Con rmation Bar Code Entry.
This takes you to the bar code entry screen.
2. Enter the action that you want to carry out.
3. If you want to use a transaction variant, choose Sequenced JIT Call Transaction Variant .
4. If you want to carry out the action automatically after a certain number of entry units then enter this number in the
Entry Units eld.
5. If you enter the external call number or sequence number as a bar code, enter the sold-to party and the partner
description.
6. You can now enter bar codes with a scanner or you can manually enter the entry objects in the Data Entry Obj. eld .
The system copies the entry objects to the table Components Groups Entered .
7. If you have not speci ed a number of entry units, you can trigger the actions in intervals, as required, by choosing .
8. Choose to leave bar code entry.
Enter Speci ed Barcodes
Use
You use this procedure, if you want to preset a sequence for the components groups or calls, when entering the barcode for the
progress con rmation, using selection criteria. You can, for example, preset a production line and a sort variant, then you can
only enter the components groups from this production line in the sequence of the sorting.
Prerequisites
You have de ned the object quali ers in Customizing for JIT Inbound.
If you want to use transaction variants in the application, you have to de ne these rst of all. Choose Tools
AcceleratedSAP Personalization Transaction Variants .
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Control Data Progress Con rmation Barcode entry
(speci ed).
12/12/2022
2. This takes you to the barcode entry (speci ed) screen.
3. Enter the action that you want to carry out.
4. If you want to use a transaction variant, choose SeqJC Transaction variant and enter this.
5. Enter any other selection criteria to determine the entry sequence.
6. If you want to carry out the action automatically after a speci c entry unit, enter this entry unit.
7. Choose .
The system copies the next call according to the selection criteria in the elds, which are not ready for input, Next call number,
Next sequence number, Next components group number. You can now enter only the components group proposed by the
system.
1. Now enter the barcodes of the entry objects with a scanner or enter the object in the eld Entry object.
The system copies the entry object to the table Components groups entered and automatically proposes the next entry object.
1. If you have not entered an entry unit, you can trigger the actions in intervals, as required, by choosing .
1. Repeat the process or choose if you want to leave the barcode entry.
Creating Additional Documentation Data
Use
You can use this function to create additional documentation data on individual call components or BOM parts per barcode
scanner. You can de ne whether the creation of this data is optional or mandatory.
The function has been designed so that you rarely require your mouse or keyboard. You make all the entries with a scanner.
Then the appropriate input elds are then automatically available after scanning.
Integration
The creation of additional documentation data is an extra function along with the standard function Barcode Entry for the
Progress Con rmation .
Prerequisites
In the JIT control data, under Maintain Production Info you have de ned whether additional data is to be created or not.
You have maintained a components group material.
If you want to create additional documentation data for BOM components, you must also set the BOM explosion
indicator under Maintain Production Info in the control data.
Features
You have two different indicators for creating additional documentation data: Optional creation of documentation data and
Change existing documentation data. These two indicators provide you with the following four possible combinations:
One of the two indicators set:
12/12/2022
Additional documentation data must be created.
Indicator Optional creation of documentation data set: set:
Optional and mandatory documentation data must be created.
Indicator Change existing documentation data set: set:
Mandatory documentation data already preassigned can be changed and created.
Both indicators set:
Both types of documentation data can be changed and recreated.
In addition to the standard delivery, there are two customer-exists with example coding that you can implement in the following
scenarios:
If, for example, you create batch numbers for a material and this material is packed per batch in crates of 50 pieces, then
the last number entered can be saved. This number is saved until the number 50 has been achieved. You only have to
create a new number when you start a new crate with a new batch number.
The creation of documentation data is usually independent of any action. In another customer exit, you can link the
creation of documentation data to certain actions. This means you can integrate the creation of documentation data in
your business process.
If additional documentation data has bee created for a material in a JIT call, you can display this in JIT monitoring by choosing
Goto Display Docu. Data .
To change already existing documentation data, choose Logistics Logistics Execution JIT Inbound Control Data
Display/Change Documentation Data .
Barcode Entry Using Hand-held Devices
Use
You can process JIT calls using mobile data entry devices if they are equipped with a display in addition to the barcode scanner.
This means you can process errors on site - if errors occurred when setting a status.
Already existing screens of the JIT component are converted via the SAPConsole into character screens so that they can be
represented in the display of a data entry device. This means you do not require any external middleware for the conversion of
the screens.
 Note
Make sure that the selected action is only applied to the components groups that correspond to your selection criteria in
situations where several components groups exists in a call, for example.
Integration
If you want to use this solution, you de ne the settings in Customizing for Logistics Execution .
The conversion of the character screens is carried out using the SAPConsole. Information on the SAPConsole and how it
works is available in the SAP Service Marketplace under Alias SCM . Here, choose Solution Details Cross-Industry
12/12/2022
Solutions mySAP Supply Chain Management Execution Info Center SAP LES Presentations Radio Frequency
to access the User Guide of the SAPConsole.
Prerequisites
In Customizing for Logistics Execution under Mobile Data Entry RF Queue Management Assigning Processors to Queues
, you have assigned the main menu SEQJIT or a main menu you have de ned to your users.
 Caution
In the Status eld, enter the indicator activating the mobile data entry functions for the user.
The warehouse number used in menu management must correspond to the warehouse number of the assignment of the
user to the queue. This is necessary for technical reasons only because the warehouse number is not signi cant for this
procedure in JIT processing. You can ll the Queue eld as necessary as it also has no signi cance for JIT processing.
Actions
1. On the logon screen, choose the desired presentation format and choose F1 Save .
2. The RF Menu screen appears.
3. Choose the number of the process you require and choose F4 Nxt .
4. The processes are executed in exactly the same way as if working without a mobile data entry device.
5. To logoff, choose F8 Logoff .
Abbreviations
Abbreviation Description
F1 Save Save or con rm entry
F2 Clr Clear entered data
F3 Back Go back one screen
F4 Nxt Continue
F5 No / yes Optional documentation data no/yes?
F6 No / yes Change existing documentation data no/yes?
F8 Logoff Logoff
Components Requirements List
Use
With this evaluation you can also gain an overview of which materials your customer has called, and in which quantities. If you
work in the JIT process without availability check, you can evaluate the requirements of the components over a speci c period of
time. In this way you can choose whether you want to evaluate call components only, or also their BOM components.
Prerequisites
12/12/2022
If you want to evaluate the BOM components, you have chosen the setting Carry out repetitive manufacturing back ush for the
corresponding materials, in the production info basic data.
Features
As well as the requirements for the individual daily periods, the list displays the available stock, the backlog and the
cumulative released quantity for a material.
You can also explode the BOM of the call components and evaluate the BOM components. The system indicates the call
components in the list with the symbol .
You can branch to the stock/requirements list for a material.
You can carry out an ABC analysis in the list.
Evaluate Components Requirements List

1. Choose Logistics Logistics Execution JIT-Inbound Control Data Components Requirements List.
This takes you to the initial screen of the evaluation.
1. Enter the selection criteria.
2. If you also want to display the BOM components, select the indicator Display BOM components .
3. If you want to enter other selection criteria, choose Options , make your entries in the dialog box and con rm with .
4. Choose .
This takes you to the components requirements list.
1. You can branch to the stock/requirements list, by clicking on a material.
Requirements Match
Use
With this function you can match the requirements from JIT calls that you have already received, with requirements from JIT
delivery schedules and forecast delivery schedules. In this way it is clear from the evaluation, whether the requirements of the
call components:
are critical
This means that the quantity called exceeds the quantity from the forecast delivery schedules or JIT delivery schedules. You
may have problems with the availability of the components to be assembled.
are balanced
This means that the quantity called corresponds to the quantity from the forecast delivery schedules or JIT delivery schedules.
are not balanced
This means that the quantity called is less than the quantity from the forecast delivery schedules or JIT delivery schedules. It is
possible that you have an unnecessarily high component stock.
12/12/2022
From the evaluation, you can generate JIT delivery schedules for the call components, for the amount of the JIT requirements.
Thus, you can react quickly to critical JIT calls.
Integration
You can move from the evaluation directly to the stock/requirements list and to the JIT delivery schedules and forecast delivery
schedules.
Features
You can compare the cumulated requirements of the call components from JIT calls with the requirements of the
forecast and JIT delivery schedules. The basis for the requirements match is the planned shipping date of the JIT call and
the loading date of the forecast/JIT delivery schedule line.
A list with traffic lights tells you whether the requirements are critical, balanced or not balanced.
From the evaluation, you can trigger the generation of JIT delivery schedules.
In the comparison, the system only considers the relevant forecast/JIT delivery schedules. The requirements from
demand planning are not taken into consideration.
The system displays a cumulated daily comparison. You can expand the rows for a day and then compare the
requirements on the basis of the call components. In addition, you can reverse the structure of the two-level list so that
you see the call components in the rst level, and the dates in the second.
The system groups open requirements from the past under the current date.
You can restrict the selection of calls. This means that you can only select calls with internal processing status Call
created .
You can enter tolerances for the deviations permitted.
You can plan background processing for the match and for the generation of JIT delivery schedules.
You can format the comparison in a graphical display.
Carrying Out the Requirements Match
Prerequisites
If you also want to generate JIT delivery schedules for the requirements match, you must note that existing JIT delivery
schedules will be overwritten. Generating JIT delivery schedules is useful if you only receive forecast delivery schedules and JIT
calls and only use JIT delivery schedules for this requirements match.
Procedure
1. Choose Logistics Logistics Execution JIT Inbound Control Data Requirements Matching.
This takes you to the initial screen of the requirements matching.
1. Choose the time period you want to use for the match.
If you also want to generate JIT delivery schedules in the requirements match, you can select the indicator Match until
end JIT calls. You thereby prevent the system from generating JIT delivery schedules outside this time period, for which
you have already received JIT calls.
12/12/2022
If you want to preset this period, you can select the indicator Match until specif.date and enter a date.
1. Enter the selection criteria.
1. Choose Options. This takes you to a dialog box, in which you can:
reverse the structure of the two-level list with the indicator Material sorting.
set a graphic display of the match with the indicator Prepare as graphic .
enter the tolerance limits for shortage and excess of the JIT requirements.
set the options for background processing of the match.
1. Choose .
This takes you to the requirements matching list.
1. If you want to generate JIT delivery schedules, choose JIT delivery schedules .
The system generates JIT delivery schedules for the amount of JIT call requirements.
1. Choose to end the evaluation.
 Note
Using the report RJITLAB001, you can execute a match between sequenced JIT calls and forecast delivery schedules. In the
initial screen of the requirements match, you can determine when the JIT delivery schedule is created (under Options ). For
more information, see Job Scheduling .
Emergency Operation
Use
You can use these functions to be able to react quickly to problems and so that you can maintain your service level. Problems
can occur, for example, in the EDI subsystem or in the physical material ow. The error handling in your system helps you to
recognize errors and their causes quickly.
Features
With JIT monitoring you can evaluate the JIT calls that have already been created in your system.
If the EDI subsystem or the delivery to your JIT customer fails you can:
create or change JIT calls manually
change the status or time of an existing call using the fast change
If problems occur during the physical material ow, you can reset the status of a call and then transfer it to production
again.
Before your system fails, it is a good idea to display a list of calls in your system and export it to a local le (such as
spreadsheet). You can, for example, select and download all calls with internal processing status Call created .
12/12/2022
Error Handling in the System
Use
This function helps you to quickly establish and remove the cause of any errors. The following errors can occur:
Technical transmission errors (inbound EDI)
Errors in the components group determination , the material determination or the scheduling agreement determination.
Errors in the data administration in the database.
Errors carrying out the back ush , the delivery or the billing document .
Features
The system prints each error with a detailed error statement.
The system can trigger a work ow process on receipt of a call. If an error occurs, the system sends an express mail to
the person responsible, containing a description of the error.
When an error occurs, the system stops the process. However, other calls are still processed.
Entering Fast Changes
Use
If you have problems with the EDI system, you can use this procedure to quickly change the external status or external status
information, the time, and the sequence number of calls that have already been created. For example, you can enter the
external status Production Release and thus transfer a call to production.
Prerequisites
The new external status or new external status information is permitted in call control for the components groups of the
relevant call.
Procedure
1. On the SAP Easy Access screen, choose Logistics LogisticsExecution JIT Inbound Emergency Fast Change.
The JIT Call Fast Change: Sequence Number, Status screen appears .
2. Enter the required header data of the call.
3. Enter the new external status or new status information, the times and, if necessary, a sequence number.
Result
The system checks whether a new external status or new external status information is available. If you have entered both, the
system uses the external status. The system changes the call and now carries out the action de ned in call control for this
status change.
12/12/2022
Status Correction
Use
With this function you can change the external status and the internal processing status of a JIT call, without considering
business dependencies. The system makes the change, without considering the call control de ned in Customizing.
For example, you can reset a call whose components groups have been damaged on loading. You can assign this call the
external status Forecast and the internal processing status Call created . Then in JIT monitoring , you can carry out action PIN
and then transfer the call to production again.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Emergency Status Correction.
This takes you to the screen Report for Status Cleanup .
1. Enter you selection criteria and choose .
The system selects all calls that correspond to the selection criteria. You can simultaneously carry out the status correction for
these calls.
1. Enter the new external status and the new internal processing status.
2. Deselect the relevant indicators, that document the processing progress.
Result
The system changes the status without considering call control. It does not carry out any actions with the components groups.
Carry Out the Excel Download
Use
With this function you can download JIT calls that already exist in your system, into a local Microsoft Excel le. In this way, you
are prepared if your system should fail.
Prerequisites
You have installed a 32 bit operating system on your workstation.
Procedure
1. Choose Logistics Logistics Execution JIT-Inbound Emergency Excel Download.
This takes you to the screen Download monitoring block list to local workstation.
1. In the eld File name , enter the path and the le name, or use the name proposed by the system, that contains the
current weekday. Make sure you note the correct spelling of the operating system.
12/12/2022
2. If possible, enter a time zone and a sort variant.
3. Choose the structure of the list:
The Components groups block display is suitable for calls for assemblies.
The Call components block display is suitable for calls for discrete assemblies.
1. Enter the selection criteria in the tab pages.
2. Choose .
Result
The system loads the selected calls onto your workstation and saves it in the le speci ed. You can process the le in Microsoft
Excel.
Grouping Term
Use
This function enables you to group a number of JIT calls and to assign a sequence for the calls within this group. The group ID is
the grouping information, and the sequence is de ned by the grouping index.
You can, for example, group the components groups that you want to send in one packaging rack, under one grouping
information. Then you can reproduce the sequence within the rack, using the grouping index.
Features
The system saves the grouping term in the components group. The grouping term consists of the grouping information
and the grouping index.
You can either assign a 20 gure alphanumeric name or a 10 gure numerical name. If you use a numerical name, you
must enter the complete number in every application.
You can, for example, generate the grouping term in JIT monitoring with action CGRP and simultaneously assign a
quantity of components groups. The system then generates the grouping information from a separate number range. It
assigns the grouping index according to the sequence in which the components groups are displayed in the list.
You can assign the grouping terms in the list of the progress con rmation. There you can also specify the number of the
packaging rack as grouping information (see also: Enter Progress Con rmation in a List ).
You can assign the grouping term using a customer exit. Here, you can decide whether you want to assign the grouping
term when transferring to production (action PIN ) or after completion from production (action POUT ).
You can enter the grouping term as a criterion in a sort variant. In this way you can sort the calls in JIT monitoring or in
the progress con rmation according to the grouping term and then select the JIT calls for the delivery.
You can use the grouping term to assign an internal sequence number. This means you can produce the calls according
to your internal sequence number and only carry out the delivery according to the external sequence number of the JIT
call.
Internal Calls (Buffer Storage Location)

12/12/2022
Purpose
You use this process when processing sequenced JIT calls. You can produce components 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.
Prerequisites
You have created a Control pro le for internal calls in Customizing for JIT Inbound.
The call type internal call corresponds to a sequenced JIT call with a ctitious external call number. The call components
of an internal call refer to a scheduling agreement. You must therefore de ne special components group types for
internal calls in the basic data for customers you want to create internal calls for. You assign a Control pro le for internal
calls to the components group types.
In Customizing in the call control you have de ned a suitable action status network for the components group types of
the internal calls and of the relevant sequenced JIT calls.
You have de ned 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.
Process ow
The process with internal calls could take place as follows:
1. You create an internal call. The components groups of the call are given park status (1500 wait) before production.
2. If you want to produce the internal call in advance, release it for production with action PIN (production release). The
components groups are given internal processing status 5000 released.
3. After production carry out a completion message with action POUT and then a back ush with action BFLU . The
components groups are given internal processing status 6200 (back ushed).
4. You store the internal call with action WIN (store call) in the buffer storage location. The components groups are given
internal processing status 6300 (stored). The call waits there until your customer sends a concrete JIT call.
5. Your customer transmits a sequenced JIT call that is created in the system with action CREA and which has the internal
processing status 0000 (created). You want to use this call from the buffer storage location.
6. The system searches for identical components groups and you carry out the components group switch with action
SWCG.
The internal call receives the non-produced components groups of the sequenced JIT call. The system assigns these
components groups to the internal processing status 1500 (wait). If you want to produce the internal call again, you can release
it again for production.
The sequenced JIT call receives the non-produced components groups of the internal call. The system assigns these
components groups to the internal processing status 6300 (stored).
1. With action WOUT you remove the components groups of the sequenced JIT call from the buffer storage location. The
components groups are given status 6200 (back ushed).
Then you can deliver the sequenced JIT calls.
12/12/2022
Creating an Internal Call
Use
With this function you can create an internal call for all sequenced JIT calls that you need out of the buffer storage.
The internal call is in constant circulation, as you supply it to production again after the components group switch. You therefore
only create the internal calls once, when you set up the process.
Integration
The call type internal call corresponds to a sequenced JIT call with a ctitious external call number. The call components of an
internal call refer to a scheduling agreement. Therefore you create the internal call with reference to a customer, but with a
ctitious external call number.
Prerequisites
The internal call corresponds to a sequenced JIT call with a ctitious external call number. You therefore also require the
following:
You have created the necessary master data in the SAP system.
You have de ned the basic data for JIT Inbound.
Features
You create an internal call manually. All the functions for manual processing are available here. The maintenance modes EDI,
components group and call component are available for processing.
Activities
12/12/2022
Proceed as in Processing JIT Calls Manually and in the initial screen in the list eld Call type , choose Internal call (buffer
storage).
Storing in the Buffer Storage Location
Use
With this function you can store a components group of a JIT call in the buffer storage location. The components group remains
in the buffer storage location until you switch it with the components group of a sequenced JIT call and then store it.
Integration
In the process control you can store using the following actions:
Description Action
Create Handling Unit from components group CRHU
Store components group WIN
Prerequisites
Action WIN or action CRHU are permitted for the current internal processing status of the components groups,
according to call control.
You have assigned a control pro le for internal calls to the components group type.
You have assigned a components group material to the components group type. For this components group material you
have created a production version, in which you have entered the receiving storage location.
Features
You can store the components group from storage with action WIN . The system determines the receiving storage
location as the issue storage location from the production version of the components group material. It calculates the
receiving storage location from the Control pro le for internal calls .
You can pack a components group in a Handling Unit (HU) with packing instructions with action CRHU before storage.
This means you pack each components group in a separate HU. In this case, the buffer storage location should be HU-
managed.
 Note
The Handling Units that you create with action CREA are only used for temporary storage in the buffer storage location.
These Handling Units are not transferred into the delivery. Therefore, you should delete these Handling Units after removing
the components groups from storage (see also Remove Components Group from Storage ).
Components Group Switch
Use
12/12/2022
With this function you can switch the components groups of a sequenced JIT call with the components groups of another JIT call.
It is preferable to switch the components groups with those of an internal call. Depending on the control pro le for internal calls
it is possible to switch the components groups of two sequenced JIT calls.
You can select a components group of sequenced JIT calls, and let the system search for identical components groups in the
buffer storage. If the system nds identical components groups of an internal call, you can switch the components groups.
Integration
In the process control you can carry out the components group switch using the following actions:
Description Action
Switch components groups SWCG
Print list of components groups to be stored PSWC
Pack and delete handling unit DEHU
Remove components group from buffer storage WOUT
Prerequisites
In call control you have de ned the necessary actions for the current internal processing statuses of both components
groups.
You have assigned a control pro le for internal calls to the components group type of the components group of the
internal call.
You have assigned a components group material to the components group type of the components group of the
sequenced JIT call. For this components group material you have created a production version, in which you have
speci ed the issuing storage location for the components group of the internal call.
Features
You can carry out the components group switch either from the JIT monitoring list or from the graphic JIT cockpit.
In JIT monitoring you can select a components group and search for equivalent components groups in the system. In the
control pro le for internal calls, you can de ne whether the system should only search for equivalent components groups
in internal calls, or also in sequenced JIT calls.
If equivalent components groups are available you can switch components groups with the action SWCG . Both
components groups contain the internal processing status, that is de ned in the call control for action SWCG .
Depending on the control pro le for internal calls, the system also switches:
the internal processing status of the components groups (status switch).
the internal components group number.
the system does not switch the grouping information of the components groups.
After the components group switch the components group of the sequenced JIT call is still in the buffer storage. You can
remove the components group from storage with action WOUT. The system determines the receiving storage location
from the production version of the components group material. The buffer storage location is de ned in the Control
pro le for internal calls .
12/12/2022
With action PSWC you can print a list of components groups to be removed from storage. You can then transfer this list
to the storage location administrator.
If you have packed the components group before storing it in a handling unit, you can carry out action DEHU after action
WOUT . Action DEHU unpacks the components group and deletes the handling unit.
You can also link action SWCG with action WOUT . To do this, enter action WOUT in Customizing in the Control pro le for
internal calls as an additional action.
Status Switch (Internal Processing Statuses)
Use
You can use this function if you want to carry out a progress con rmation at other points between the production release and
the completion message, so that you can document the production progress more exactly in longer lead times. With this
function you can also switch components groups that are already in production.
The components groups of the internal call are usually given an internal processing status after the components group switch,
that is prior to the release for production (park status). You can then transfer the components groups to production and
reprocess it at a given time. However, if you want to switch the components groups of an internal call with a components group
that is already in production, you can also switch the internal processing status of the components group after the components
group switch. In this way the components groups of the internal call enter production and you can complete production.
Prerequisites
You have selected the indicator Status switch . in Customizing for JIT Inbound in the control pro le for internal calls.
Features
The system carries out the components group switch by executing action SWCG. The components groups are given the internal
processing status that is de ned in the call control. Then the system switches the internal processing status of both
components groups.
12/12/2022
Switching Internal Item Numbers
Use
You can use this function if you also want to switch the internal item numbers of the components groups, in the components
group switch. This item number identi es the components group.
If you assemble materials, for which documentation about serial or batch numbers is necessary, you can switch the internal item
numbers
If you use the internal item number for identi cation in the production, and for example you print it on the components group as
a barcode, then such a switch is not necessary.
Prerequisites
You have selected the indicator Switch int.item no . in Customizing for JIT Inbound in the control pro le for internal calls.
Features
The system carries out the components group switch by executing action SWCG. Then the system switches the internal item
numbers of both components groups.
Switch Components Groups
Procedure
1. Select the components group that you want to switch.
2. If you are working in the JIT monitoring list, choose List Switch components group.
3. If you are working in the JIT cockpit, choose Graphic Switch components group .
4. The system searches for equivalent components groups in the system and then displays them in a dialog box.
5. Select the components group that you want to transfer in the sequenced JIT call.
6. Choose Switch.
If action SWCG is permitted for the internal processing statuses of both components groups, the system carries out the
components group switch.
Result
The system has switched the components groups according to the settings in the control pro le for internal calls. You can
update the JIT monitoring by choosing . You may have to change the selection criteria, so that the call is displayed.
Summarized Range Call
De nition
12/12/2022
JIT call for which a range of summarized JIT calls is entered. This range is then split into x number of individual calls. The delivery
date is the same for each individual call.
The following graphic shows the structure of the summarized range call:
Use
You 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.
JIT Cockpit
De nition
The JIT cockpit is a graphical application, with which you can display important information on the current status of production.
In the graphic, you can display several subscreens, in which the system shows the JIT calls or the components groups in a bar
chart. You determine which calls are determined in the subscreens using extensive selection criteria.
You can display detailed information for the bar charts and you can use them to execute actions.
Use
You can use the JIT cockpit for JIT monitoring and for the progress con rmation for both JIT inbound and JIT outbound. The JIT
cockpit is thus an alternative to working in a list or with the barcode entry.
Structure
The JIT cockpit consists of the following screen areas:
12/12/2022
Subscreens in the graphic
In the subscreens the system displays the calls or the components groups in sequence as a bar chart. You can display a
maximum of ve subscreens in the JIT cockpit. For the progress con rmation you generally require only one subscreen, in which
you can display the orders to be back ushed. For each subscreen you can enter a sort variant, with which you determine the
sequence of the orders.
Settings
In this screen area you de ne which JIT calls the graphic displays in which subscreens. You can specify basic settings, that are
valid for all subscreens. Then you can set the selection criteria for each subscreen.
Details
In this screen area you can display detailed data on the JIT calls. The system reproduces the call structures in an overview tree
and you can display detailed information on the call header, the components groups or the call components by double-clicking.
You can access the scheduling agreement from the detailed information, for example.
Component list (HTML format) (only for JIT inbound)
You can only display the component list in the progress con rmation. The component list displays the components groups and
the call components that are shown in the rst subscreen (back ush window). The component list also displays the BOM
components of the call components, if you have selected the BOM explosion in the basic data, under Maintain Production Info .
If you do not require the information of a screen area, you can hide it.
Basic Settings of the JIT Cockpit
Use
With this function you make the basic settings for the subscreens of the JIT cockpit. You can display a maximum of ve
subscreens. The basic settings are valid for all subscreens.
Integration
The basic settings that you make in the JIT cockpit for JIT monitoring are independent of the basic settings that you make for
the progress con rmation.
Features
Main criterion and secondary criterion
With these criteria you determine the structure of the subscreens.
The main criterion sets a lter over the whole subscreen. The subscreens are distinguished according to the main criterion. You
can, for example, display only calls from a speci c JIT customer or calls with a speci c external status. The system displays the
main criterion and its characteristics in the header column of the subscreen.
With the secondary criterion you can divide a subscreen into several rows. You can, for example, display a row for each
production line for which you are responsible.
 Example
12/12/2022
For JIT inbound, you choose the sold-to party as the main criterion and the production line as the secondary criterion. You
can then display a subscreen for sold-to party A and a subscreen for sold-to party B. In the rst subscreen you display the
calls on production line 1 in a row and the calls on production line 2 in another row. In the second subscreen you only display
the calls on production line 3.
For JIT outbound, you could choose the supplier as the main criterion and the internal processing status as the secondary
criterion. As for JIT inbound, you can then display a subscreen for supplier A and a subscreen for supplier B.
Display level
With the display level you set whether you want to see the JIT calls or the components groups as a bar chart in the graphic. If
you choose components groups, you can carry out actions only with selected components groups. Otherwise you carry out
actions on selected calls.
You can set which attribute of the call or the components groups the system uses to describe the bar charts in the
graphic and which quick info text the system displays.
You can set that the system automatically displays the sum of the calls or components groups in a row in a column.
You can set that the system also displays the gaps in the sequence of the calls.
You can set that the system automatically updates the graphic in regular intervals. If you do not use this function you can
only update the graphic manually.
You can set that the system only displays speci c call types in the JIT cockpit.
In addition, you can specify a time zone and a color pro le .
Activities
Choose in the screen area Settings for the graphic of the JIT cockpit and carry out the basic settings. The settings are valid
for all subscreens of the graphic.
De ning the Color Pro le
Use
With this procedure you de ne the colors the system uses to display the bars in the graphic, depending on the characteristics.
Procedure
1. From the JIT cockpit choose Settings Color pro le .
2. Choose New entries .
3. Enter a description and a short text for the pro le.
4. Enter a color group (such as JIT000) that groups several color types.
5. Enter which selection criterion (such as internal processing status) you want to make the color of the bar dependent on.
6. Choose Assign color .
7. Choose New entries .
8. Enter the color types and the corresponding characteristics of the selection criterion.
12/12/2022
If you do not enter a color type for a characteristic, the system displays the order bars with this color in white.
Result
You have created a color pro le. If you want to use the color pro le, enter it in the basic settings of the JIT cockpit .
Setting Subscreens
Use
This procedure describes the settings that you can carry out alongside the basic settings for the subscreens. You can add or
remove subscreens. Each subscreen contains options for setting:
the main criterion in the basic settings
the secondary criterion
additional selection criteria.
Prerequisites
You have made or adjusted the basic settings for the JIT cockpit.
Procedure
1. If the screen area Settings is not displayed in the JIT cockpit, choose Show settings .
The system displays the screen area Settings . Here, the system displays all the subscreens of the graphic in a selection tree.
1. If you want to add further subscreens, choose .
2. If you want to remove subscreens, choose .
3. Expand the nodes of the rst subscreen.
4. Select the characteristics of the criteria, by double-clicking on them.
Characteristics with the symbol are selected for the subscreen.
Characteristics with the symbol are not selected for the subscreen.
1. If you want to select or deselect all characteristics of a criterion, select the criterion and choose Select all or Deselect all
in the context menu.
1. Repeat the operation for all criteria of the subscreen.
2. Double-click the subscreen in the selection tree or use the right-hand mouse button.
This takes you to the screen Changing the settings for the current subscreen .
1. In this screen specify how many calls you want to display in each row of the subscreen and whether the calls are to be
sorted according to a sort variant.
12/12/2022
2. These settings are relevant for the graphic progress con rmation, if you want to enter the entry units in a speci c
sorting.
3. Choose .
4. Choose to update the graphic and to copy the settings to the subscreens.
Result
You have set the selection criteria for the subscreens. If you want to keep the settings, you can create a display variant .
Creating and Assigning Display Variants
Use
You use this procedure to retain the settings that you make for the graphic of the JIT cockpit, for later sessions. You can also
create display variants for the progress con rmation as an administrator, and then assign them to various users.
The system saves all settings for the graphic in a display variant.
You can de ne a display variant as being user-speci c so that only you can call it up.
You can de ne a display variant as an entry variant so that the system automatically uses this display variant when you
call up the JIT cockpit.
Prerequisites
You require authorization 70 for authorization object C_AUTO_JIT to create display variants.
Procedure
1. From the JIT cockpit choose .
This takes you to the dialog eld Save display variant .
1. Enter a description and a short text for the variant.
2. If you want to reserve the display variant for yourself, select the indicator User-speci c .
3. Choose .
The system saves the display variant.
1. If you want to de ne the display variant as an entry variant, choose Settings Entry variant Administration.
This takes you to the dialog eld Variant management .
1. Select a display variant and choose Entry variant .
2. Choose .
3. If you want to want to assign a display variant to a user for the graphic progress con rmation , choose Settings
Assign variant and enter the variant and the user.
12/12/2022
Inter-Plant JIT Processing with External Service Provider
Purpose
Changes in the market have revealed a trend in JIT processing: A number of manufacturers and suppliers have some plants that
concentrate on production and some that specialize in picking JIT calls. This plant’s function can also be taken on by an external
service provider (ESP).
You can represent this process using JIT processing. In this case, the customer of the JIT call is not the manufacturer but the
plant that specializes in picking calls, or the external service provider.
Prerequisites
If you want to integrate an external service provider into your JIT process you must have created a scheduling
agreement with the scheduling agreement type LZJE . This scheduling agreement type is a prerequisite for this process
because you can maintain a special stock partner in this type of scheduling agreement. Furthermore, the scheduling
agreement LZJE is not relevant for billing.
The external service provider cannot take delivery of any components in this process. The quantities remain the same
throughout the process.
In this process it is assumed that the ESP and the system supplier work in the same system or stock management is
carried out in one system.
Process Flow
1. The manufacturer sends a forecast/planning delivery schedule to the system supplier.
2. The system supplier uses the action DELI to create a delivery to the external service provider (EDL). This delivery
contains a reference to a scheduling agreement and thus reduces requirements. This delivery type is not relevant for
billing. The components are delivered to the ESP.
3. The manufacturer sends a signal, for example a JIT call to the ESP.
4. The ESP generates a delivery with delivery type LF to the manufacturer. This delivery also contains a reference to a
scheduling agreement but does not reduce requirements. This delivery is generated using the action DLSP and is
relevant for billing.
5. The ESP delivers the components to the manufacturer.
The following graphics gives you an overview of the process:
12/12/2022
For more information see Functions for the External Service Provider (ESP) .
Delivery Con rmation
Purpose
You can use this process if you receive delivery con rmations per EDI, in which your JIT customer con rms the call components
you delivered. In practice, these delivery con rmations are also called day’s collective delivery notes. The system can
automatically create a billing document on the basis of the delivery con rmation. Then you can carry out a logistic quantity
match with the calls in your system.
You can receive delivery con rmations in the formats VDA4913 and ANSI 861.
Prerequisites
You have set up the EDI Interface for the IDoc GSVERF02.
The corresponding JIT scheduling agreements have sales document type LZJQ (JIT scheduling agreements and the
items of item type LZQ (sched. agreement item in delivery con rmation). The settings necessary for the sales
documents and the billing documents are described in the IMG activity Delivery con rmation in Customizing for JIT
Inbound.
Process ow
1. First of all you deliver the JIT calls, without creating a billing document. The JIT scheduling agreements with purchasing
document type LZJQ are not relevant for the billing document.
2. The JIT customer sends a delivery con rmation in regular intervals. This does not usually have any direct reference to
your deliveries. The delivery con rmation contains the call components and their aggregated quantity. In addition it
contains the external call numbers of the JIT calls, on header or item level, in which the call components were assembled.
12/12/2022
3. The system automatically creates the billing document on the basis of the delivery con rmation.
4. You can then carry out a logistic quantity match. In this way you compare the quantities con rmed in the delivery
con rmation with the quantities of the JIT calls in your system. You can either start the match manually or let the system
carry it out automatically.
5. If differences occur, you can process these manually. You can then clarify problems with your JIT customers.
Creating the Billing Document by EDI
Use
The system carries out this function automatically when you receive a delivery con rmation from your JIT customer. The system
creates a billing document on the basis of the quantity con rmed in the delivery con rmation without carrying out a logistics
match without the quantities in your system beforehand.
Integration
The functions required in components SD Billing are integrated in the delivery con rmation.
Prerequisites
The corresponding JIT scheduling agreements have sales document type LZJQ (JIT scheduling agreements and the items of
item type LZQ (sched. agreement item in delivery con rmation). The settings necessary for the sales documents and the billing
documents are described in the IMG activity Delivery con rmation in Customizing for JIT Inbound.
Features
The system creates the billing document with type FX. (Billing ext.transaction) automatically on receiving the delivery
con rmation. It copies the number of the delivery con rmation, the call components and their quantities as well as the
sales area to the billing document.
 Note
As long as the billing document has not yet been created, you have no explicit claim against the JIT customer in your system.
However, as the JIT calls contain the materials and quantities delivered, that have not yet been paid for, this is only a minor
problem.
12/12/2022
If an error occurs when creating the billing document, the system terminates the operation and creates an express mail
that contains the status records of the IDoc. The person responsible can determine why the error has occurred, using
this mail.
You cannot cancel the delivery con rmation and thus you cannot create the billing document .
Activities
1. Choose Logistics Sales and Distribution Billing Billing Document Display to display the billing document.
2. Enter the data of the billing document and choose .
This takes you to the item overview of the billing document.
1. If you want to show the link to the IDoc, choose System Links .
2. If you want to display the reference to the delivery con rmation, choose and then the tab page Header detail .
The number of the delivery con rmation is in the area Accounting data in the eld Reference .
1. If you want to display the reference to the JIT scheduling agreement for an item, select an item and choose .
The number of the scheduling agreement is in the area Billing data in the eld Reference document .
Logistic Quantity Matching
Use
You can use this function to compare the quantities con rmed in the delivery con rmation with the quantities of the JIT calls in
your system. As the JIT customers do not usually create the delivery con rmation with any direct reference to your deliveries,
this can result in differences that you can analyze after the match.
The system can carry out the match automatically after creating the billing document. You can then process the result
manually.
You can trigger the match manually and then process it.
In Customizing for JIT processing, you can also de ne a simultaneous match. Such a match automatically takes all linked
delivery con rmations into account.
If you do not want to check the delivery con rmations your JIT customer sends to you, you do not have to use the logistic
quantity match. This then ensures better system performance.
Integration
In the process control you can also use the following actions to set the status of a components group to Matched or to reset the
match.
Description Action
Delivery con rmation: set to Matched (only status change) MTCH
Reset delivery con rmation match (only status change) UDMT
12/12/2022
Prerequisites
You have set whether and how you want to carry out the match in the control pro le for the delivery in Customizing for JIT
Inbound. You have assigned the control pro le to the corresponding JIT customer in the JIT basic data.
Features
The JIT customer transmits the call components and their con rmed delivery quantities in a delivery con rmation. In addition,
at header or item level, the customer transmits the external call numbers of the JIT calls in which the call components were
assembled. However, the customer does not transmit any information on which quantity is assembled in which call. Therefore, in
the match, the system calculates the quantities of all transmitted external call numbers and then matches the components
groups with the quantities of the delivery con rmation. The system displays the differences under the materials that cannot be
used for the match. As the JIT customer does not transmit the necessary information the system does not know in which JIT
calls the differences occur (see diagram).
You can carry out the logistic quantity match automatically or manually in a list. After the match you can process any
differences. You can select several delivery con rmations and match simultaneously.
The system displays a list of the delivery con rmations which have not yet been matched (yellow), which have been
matched completely (green) and which require processing (red).
If differences occur, you can set the delivery con rmation manually to status Matched , to conclude the delivery
con rmation. You can also reset the match (status change) and carry it out again later.
In the list you can display detailed information on the JIT calls, whose external call numbers are contained in the delivery
con rmation.
You can display the match result in a separate list. In the list you can display the match result at components group level.
Delivery Con rmations: Match and Reprocess Manually
Use
You use this procedure if you want to carry out the logistic quantity match manually, or if you want to reprocess the automatic
quantity match.
Procedure
12/12/2022
1. Choose Logistics Logistics Execution JIT-Inbound Control Data Matching Delivery Con rmation.
This takes you to the screen Manual Matching of Delivery Con rmation .
1. In the area Delivery con rmations enter the number of the delivery con rmation, the billing document or the date of the
billing document.
2. In the area Customer data enter the sold-to party and the partner description.
3. In the area Matching parameters , enter the status of the delivery con rmations that you want to process.
4. Choose .
The system displays the delivery con rmations selected in a list.
If you want to display a legend for the traffic lights, choose Legend .
If you want to display a list of the external call numbers transmitted and detailed information on the relevant JIT calls,
choose on header or item level.
If you do not want to match a delivery con rmation manually, select a delivery con rmation with the status Not matched
(yellow) and choose Matched .
The system carries out the match and updates the traffic lights, depending on the match result.
If you want to display the result, select a delivery con rmation that has been matched and choose Display match .
The system displays the result in a separate list. You can remove the matched quantities from the list.
If you want to display in which components groups the system has set the status to matched, choose at header or
item level.
If you want to complete the delivery con rmation independent of the match result, choose DC completed.
Choose to reset the display of the delivery con rmations.
If a delivery con rmation was not matched or if errors occurred, a log is saved in the database for this delivery
con rmation. You can display this log by selecting the delivery con rmation and choosing List Display Log . You can
also display the log after a delivery con rmation has been changed manually.
If you want to reset the match of a delivery con rmation, choose Reset match .
The system converts the status of the delivery con rmation to not matched and you can carry it out again.
If you want to delete a delivery con rmation, select it and choose Delete .
Choose to leave the logistic quantity match.
Comparison of JIT Calls with Delivery Con rmations
Use
You can use this report to compare the quantities in the delivery con rmations for a particular day with the required quantities
in the JIT calls.
Integration
12/12/2022
You can also match and reprocess delivery con rmations manually.While the manual matching of delivery con rmations gives
you an overview of the delivery con rmations and their status, the comparison of the JIT calls with delivery con rmations gives
you an overview of the materials and any arising deviations.If you want to change the status of a delivery con rmation, you
manually match the delivery con rmations.
Features
Selection
You can search for delivery con rmations according to the following criteria:
Reference document number for the delivery con rmation
Customer data, for example, ordering party
Material
JIT call
Period of the JIT call
Status of the JIT call
If you do not enter any calls, the system automatically searches for reference calls in the delivery con rmations that you have
entered.
Display of the Comparison Report
The system displays all materials with the following information in a list:
Customer material number
JIT call quantity
Con rmed quantities
Base unit of quantity
Difference between JIT call quantity and con rmed quantity
For each item in the list, you can display details, such as the related JIT calls and delivery con rmations.
Activities
To call the report, on the SAP Easy Access screen, choose Logistics Execution → JIT Inbound → Control Data → Matching
Delivery Con rmations.
Example
12/12/2022
For day 1, you have sent JIT calls for material A and material B to your supplier.You have posted a delivery con rmation for both
material A and material B.The report displays an overview of calls 1001 to 1004 for day 1 and the related delivery con rmations 1
and 2. You can use the report to check whether there are differences between the total quantity of JIT calls for day 1 and the
number of delivery con rmations.
Comparison of JIT Calls and Delivery Confirmations
Archiving JIT Calls (IS-A)
Use
Using archiving object JIT_SJCALL (for JIT Inbound) and JITO_CALL (for JIT Outbound), you can archive JIT calls. The archiving
data consists of call header, the components groups, the call components, the IDoc and the JIT call texts.
Integration
During archiving the system locks all calls, which are to be archived, in order to avoid parallel access.
Features
The following functions are available in archiving.
12/12/2022
Action Description Report
Archiving The archiving program writes the JIT call RJITARCH01 for JIT Inbound
database tables in an archive le with a
RJITOUTARCH01 for JIT Outbound
special archiving structure. If the operation
was successful, the data is deleted from
the system directly after it has been
archived, depending on the settings in
Customizing. You can also start the deletion
program separately.
Deleting The deletion program deletes all the RJITARCH02 for JIT Inbound
transaction data of the archived data from
RJITOUTARCH02 for JIT Outbound
the system.
Resetting After archiving, you can no longer change RJITARCHNO

the JIT calls using actions (for example with
(only for JIT Inbound)
JIT monitoring). However, if you want to
process the calls further, you can reset the
archiving with this report. Use the call
control to ensure consistency.
Administration With this function you can display past

archiving processes.
Archiving JIT Calls (IS-A)
Use
The archiving program selects JIT calls and writes these in archive les. This data consists of the call header, components
groups, call components, JIT call texts and IDocs.
You can create your own variant for the archiving run and optimize it, for example, using the following parameters:
Residence time
You can change the residence time in the variant. The key date for archiving is calculated from the system date less the
residence time. If the date of the relevant internal processing status before or on this key date, you can archive the call.
Maximum lock entries
The JIT calls to be archived are locked during archiving. As the number of calls is generally very high, the lock table can easily
over ow. To avoid this the system carries out the archiving in sections. You can determine the size of the sections with the
maximum number of lock entries.
Internal processing status
If, in the call control several internal processing statuses allow archiving, you can limit archiving in the variant to certain internal
processing statuses.
Test run
If you have not selected the indicator Create archive le you can simulate the archiving run in order to display the log, for
example.
Archive complete calls only
12/12/2022
You can partially archive calls, for example individual components groups. If you have not set the indicator Only archive
complete calls , you can also archive individual components groups of a call. If, however, you have set this indicator, and not all
the component groups of a call correspond to the selection criteria, the call will not be archived. The archiving run continues.
Prerequisites
The archiving program only selects those JIT calls with an internal processing status that permits the action Allow archiving
(ARCH for inbound calls or OARC for outbound calls ). You determine in Customizing which action is allowed for which internal
processing status.
Procedure
1. Choose Logistics Logistics Execution JIT Outbound or JIT Outbound Environment Archiving.
2. The Archiving Administration: Initial Screen appears.
3. Enter the name of the archiving object ( JIT_SJCALL for Inbound or JITO_CALL for Outbound) and choose Archiving .
4. Enter a SAP standard variant or your own variant.
If you want to create your own variant, enter a new variant name, and choose Maintain . Determine the criteria of the selection,
determine the technical control and save your variant.
 Note
For the next archiving run, make sure that you determine the selection parameters of the variant again, or that you check
the entries.
1. Determine a start date.
2. Determine the spool parameters.
3. Choose Execute .
Result
One or several archive les are created.
The archiving program logs the process in the form of a list. Depending on your settings (spool parameters, see Procedure) this
list is printed and/or stored temporarily in the spool after the program has ended.
This takes you to the processing log, in which you select the job executed in the Job overview and select Spool list . In the Spool
list you can indicate the corresponding spool request and choose Display . If you have not set the indicator for creating a
processing log in the variant, the log will not be very detailed.
You can evaluate the archived data with the archive information system. In this way you can select the calls according to the
external call number, for example.
Deleting JIT Calls (IS-A)
Use
12/12/2022
With the deletion program either the transaction data from the data records issued to the archive le or the JIT calls are
deleted from the database.
 Note
You only have to delete manually if you have not set the indicator Start automat . in Customizing under Technical settings
Settings for deletion program , or if you have set the indicator Delete only in test mode in the variant of the archiving
program.
Prerequisites
You can only delete those JIT calls that you have already archived.
Procedure
1. In the initial screen of Archiving choose Delete .
2. If you only want to simulate the deletion of data, choose Test run .
3. Select an archive.
 Note
The variant setting is in Customizing for archiving objects. There is a SAP standard variant for both the test run and the
update run. If you want to create your own variant, enter a new variant name, choose Variant and determine the criteria for
the selection. Save the variant.
1. Determine a start date.
2. Determine the spool parameters.
3. Choose Execute .
Result
The data records are deleted from the following tables:
JIT Inbound JIT Outbound
JITD (Call header) JITOHD (Call header)
JITIT (Components groups) JITOIT (Components groups)
JITCO (Call components) JITOCD (Call components)
JITED (Assigned IDocs) JITOGR (Material document assignment)
JITTE (Call texts) PABASN (Shipping noti cation assignment)
JITOAD (Additional data for call)
The deletion program logs the process in the form of a list. Depending on your settings (spool parameters, see Procedure) this
list is printed and/or stored temporarily in the spool after the program has ended.
This takes you to the processing log, in which you select the job executed in the Job overview and select Spool list . In the Spool
list you can indicate the corresponding spool request and choose Display . If you have not set the indicator for creating a
12/12/2022
processing log in the variant, the log will not be very detailed.
Interface for Subsystems
Use
You can use this function if you use a subsystem for the JIT process, alongside your SAP System. This can be, for example, a
production control system. Using the BAPIs described here, you can connect these subsystems to realize an automatic
completion message when reporting points are passed, for example.
Features
The following BAPIs are available for sequenced JIT calls or summarized JIT calls:
JITCallInbound.GetComponentGroupDetails
You can use this method to transfer detailed information on a list of components groups to a subsystem.
JITCallInbound.GetComponentGroups
You can use this method to transfer a list of components groups with given selection criteria to a subsystem.
JITCallInbound.GetDetails
You can use this method to transfer detailed information on a list of calls to a subsystem.
JITCallInbound.PerformAction
You can use this method to carry out an action for a list of components groups, from a subsystem.
JITCallInbound.PerformActionFullCall
You can use this method to carry out an action for a list of calls, from a subsystem.
 Note
As well as the BAPIs, you can call up the module JIT04_SET_ACTION_EXTERN by Remote Function Call (RFC). This gives you
extensive transfer parameters for carrying out actions.
JIT Inbound (IS-A-JIT)
Purpose
You use this EDI scenario to receive calls that you deliver just in time. After you have delivered the calls you can receive a
delivery con rmation from your customer and create a billing document, with reference to this.
A customer sends you a JIT call by requesting several call components to a product or a reference number. You can receive the
following types of call:
Sequenced JIT calls (seqJC)
12/12/2022
This type of call is for the receipt of JIT calls, which you supply with fully con gured components, both with reference to an order
and in sequence.
Summarized JIT calls (sumJC):
This type of call is for the receipt of JIT calls, whose items represent a pair of date and quantity. The items do not have any
reference to the nished product and are not delivered in sequence. The reference number of the call controls all subsequent
processes, such as the delivery. In practice, the reference number is also called the Delivery Order Number (DON). If your JIT
customer transmits summarized JIT calls with several identifying reference numbers, you must split these up into several JIT
calls in the EDI box.
Prerequisites
This process only describes the EDI scenario for receiving JIT calls. For further information about processing JIT calls, see the
documentation on JIT Inbound .
Process ow
With the JIT call, the JIT customer transmits an external status that describes the production progress at the JIT customer
(such as production release). Depending on this external status, the system creates the call in the system according to call
control and arranges it in the call structure .
Inbound EDI for a JIT Call (IS-A-JIT-SCJ, IS-A-JIT-MAB)
Use
In this EDI scenario you receive and process JIT calls that are sent to you by a customer system. You can receive both sequenced
and summarized JIT Calls as part of JIT Inbound.
Sequenced JIT calls are usually sent by a customer several times, each time with a different status or sequence number.
Therefore the system identi es a JIT call by the external call number and modi es it
Prerequisites
Customizing
Assign sold-to party
Here you obtain the customer number from the data sent by the customer. This number is maintained in your SAP
system.The inbound EDI of calls is set up in Customizing for Sales.Choose Logistics Sales and Distribution Sales
Sales documents Scheduling agreements with delivery schedules Control EDI inbound processing.
JIT Inbound
In Customizing for JIT Inbound you have processed the necessary IMG activities.Choose Logistics Logistics Execution
JIT Inbound .
IDoc Interface
The basic types of the IDoc for the JIT calls are called SEQJIT01 , SEQJIT02 and SEQJIT03 .
Compared with SEQJIT01, SEQJIT02 offers you additional reference numbers. You only need this IDoc type if you work with
work additional reference numbers. If you do not work with more than three additional reference elds you can also work with
12/12/2022
SEQJIT01 and the most current segment release.
You use SEQJIT03 if you work with JIT Outbound and con gurable materials.
The following elds are maintained in the partner pro le:
Parameter Value
Partner type KU (Customer); in the ALE scenario (IDoc is transmitted from the
ERP system via tRFC): LS (logistics system)
Message type SEQJIT (sequenced JIT calls)
PAB_ORDERS (summarized JIT calls)
Transaction code SJCL
Processing Example: immediate processing
Processor permitted Organizational unit (for example, user)
Application
You have created the necessary master data and the JIT basic data in the SAP system.
Activities
Inbound Processing
The IDoc interface receives the IDoc and obtains the processing module IDOC_INPUT_SEQJIT from the control record and the
corresponding partner pro les. The system calls up the ALE services.
The system processes the IDoc in the background. It obtains the sold-to party from the IDoc data records. If the JIT call with the
external call number transmitted no longer exists in the system, the system creates the call again. If the JIT call already exists,
the system modi es it.
Then the IDoc has the new status 53 (application document posted) in the IDoc interface).
Exception Handling
If a processing error occurs in the applications, the system generates a work item and determines the processor for this work
item following the standard method in the IDoc interface. The IDoc has status 51 ( application document not posted). It can be
processed manually in the background, or online.
To display IDocs from JIT Inbound choose Environment IDoc.
Inbound EDI for a Delivery Con rmation (IS-A-JIT-DLC)
Use
In this EDI scenario you receive and process delivery con rmations that are sent to you by a customer system. In the delivery
con rmation, the customer con rms the materials received. It contains the call components, their aggregated quantities, and
the appropriate external call numbers.
12/12/2022
The system creates a billing document on the basis of this delivery con rmation. Then you can match the quantities con rmed
with the quantities of the JIT calls in your system. You can carry out the match automatically or manually.
Prerequisites
Customizing
Assign sold-to party
Here you obtain the customer number from the data sent by the customer. This number is maintained in your SAP
system.The inbound EDI of calls is set up in Customizing for Sales.Choose Logistics Sales and Distribution Sales
Sales documents Scheduling agreements with delivery schedules Control EDI inbound processing.
JIT Inbound
In Customizing for JIT Inbound you have processed the necessary IMG activities.Choose Logistics Logistics Execution
JIT Inbound .
Billing document
So that the system can automatically create the billing document after the inbound EDI, speci c prerequisites must be
ful lled. These prerequisites are described in Customizing for JIT Inbound in the activity Delivery con rmation.
IDoc Interface
The basic type of IDoc for the delivery con rmation is GSVERF02
The following elds are maintained in the partner pro le:
Parameter Value
Partner type KU (Customer); in the ALE scenario (IDoc is transmitted from the
ERP system via tRFC): LS (logistics system)
Message type DELCON
Transaction code DLCN
Processing Example: immediate processing
Processor permitted Organizational unit (for example, user)
Application
You have created the necessary master data and the JIT basic data in the SAP system.
Activities
Inbound Processing
The IDoc interface receives the IDoc and obtains the processing module IDOC_INPUT_DELCON from the control record and the
corresponding partner pro les. The system calls up the ALE services.
The system processes the IDoc in the background. It obtains the sold-to party from the IDoc data records. Then it creates the
billing document and if necessary, carries out the automatic logistic quantity match.
Then the IDoc has the new status 53 (application document posted) in the IDoc interface).
12/12/2022
XML Upload
Use
Using the XML Upload function, you can load JIT calls to a local XML le. The XML upload can replace the Electronic Data
Interchange (EDI) which means you do no require an EDI converter to use this function.
You load a le from a computer to the SAP System. The data is then processed via the inbound EDI in your system. The data is
split into individual IDocs.
This XML le format is an XML version of SAP and not an official XML form. Its structure is similar to the IDoc structure.
Prerequisites
You have installed a browser on your workstation.
Activities
1. Choose Logistics Logistics Execution JIT-Inbound JIT call XML Upload.
This takes you to the screen Upload SEQJIT XML File .
1. Enter the le name and the recipient port.
2. Choose .
The data is now processed as a standard IDoc.
Business Add-Ins JIT Inbound

You can adjust JIT Inbound to suit your own requirements.To enable you to do this, SAP provides a number of Business Add-Ins
(BAdIs).You can nd the BAdIs in Customizing under Logistics Execution JIT Inbound Business Add-Ins (BAdIs). For JIT
Inbound, the following BAdIs are available:
Business Add-In Description
JIT_DELCON You can use this BAdI to in uence the IDoc inbound processing of
the delivery con rmation. You can change elds, execute actions
and adjust the processing logic to suit the process you are using.
JIT_MONITOR You can use this BAdI to enhance JIT-Monitoring with your own
function keys.
JIT_NUMBER You can use this BAdI to assign an internal key when you create JIT
basic data (components group type, destination) .
JIT_GM_TYPE Movement type for stock transfer
JIT_FIND_SA Determines delivery schedule
For more information, see the documentation for the individual BAdIs.

SAP - JIT CALLS - Inbound (SeqJC, SumJC)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP - JIT CALLS - Inbound (SeqJC, SumJC)

Uploaded by

Copyright:

Available Formats

12/12/2022

JIT Inbound (SeqJC, SumJC)

SAP ERP Support Package Versions | 6.0 SP31

Original content: https://help.sap.com/docs/SAP_ERP_SPV/1ca7f6aba1c940e7b97ec51bd2841bf2?locale=en-

For more information, please visit the https://help.sap.com/docs/disclaimer.

JIT Inbound (SeqJC, SumJC)

Sequenced JIT calls (seqJC)

Summarized JIT calls (sumJC):

Module Component (documentation)

LO – Logistics - General LO – Material Master Data

SD – Sales and Distribution SD – Basic Functions (customer master records)

SD – Scheduling Agreements for Component Suppliers (forecast

SD - Sales (scheduling agreements)

LE - Logistics Execution LE - Shipping (outbound delivery)

Transactions: JIT Inbound

Inbound JIT Calls

Create JIT Call JIT1

Change JIT Call JIT2

Display JIT Call JIT3

Simulate JIT Call JIT4

XML Upload JITXML

Controlling Inbound JIT Calls

Inbound JIT Monitoring JITM/JITMX

Enter Progress Con rmation in a List JITF/JITFX

Signal Monitor JITJ

Inbound JIT Cockpit JITG

IDoc Monitor for Incoming JIT Calls EMJIT

Status Correction JITE

Action Log JITLOG

Barcode Entry JIT6

Bar Code Entry with Standard Value JIT7

Components Requirements List JITA

Requirements Match JITH

Delivery Con rmations: Match and Reprocess Manually DLCN

Comparison of JIT Calls with Delivery Con rmations DLC2

Change/Display Documentation Data JITZ

Inbound JIT Monitoring JITM

Fast Change JIT5

Status Correction JITE

Microsoft Excel Download JITX

Emergency Creation of Summarized Range Call JITEMRA

Maintain Control Data JITV

Maintain Production Information JITL

Maintain Sort Variant OJIT5

Reorganize the Basic Data JITR

Internet Access Data OJIT14

Reprocess Goods Movements JITB

Delivering Operations to be Shipped JITK

Overview of JIT Calls JITI

Display Action Network JITQ

JIT Inbound OJITI

JIT Outbound OJITO

Call Structure and Call Types

Calls for assemblies

Calls for discrete materials and summarized JIT calls

The call header identi es the call.

Sequenced JIT Calls for Assemblies

With sequenced JIT calls for assemblies:

Sequenced JIT Calls for Discrete Materials

With sequenced JIT calls for discrete materials:

Summarized JIT Calls

Several materials (pick up sheet)

Ranges of production numbers

Additional Reference Data