JIT Master data objects / Customizing

Master data

JIT& JIS Master data and basic objects
BOM
JIT Control Cycles
Source List
Material Master for Call Components
MM Scheduling Agreements
Business partner: Vendor
JIT customer
SD agreement
Components Group Types
Component group type determination
Components Group Material
Production Info ( Transaction JITL )
Shared buffers

Customizing

Call Control
JIT Inbound

CREA: JIT-Abruf anlegen
MODI, MODH, MOD*: JIT-Call change
JIT2: Ändern eines Abrufs über Trans. JIT2
CGAP: Teilegruppe hinzufügen (MAB)
CANC: Teilegruppe stornieren
DLET: Teilegruppe löschen
DELC: Komponente löschen
DEHU: Auspacken und Löschen Handling Unit
CRHU: Handling Unit für int. Abrufe erzeugen
SWCG: Teilegruppe austauschen (interner Abruf)
WIN: Einlagern in TG-Pufer (interner Abruf)
WOUT: Auslagern aus TG-Pufer (interner Abruf)
PSWC: Druck Teilegruppentausch (Puferabruf)
PIN: Übergabe an die Produktion
NIO: Fehlteilmeldung (Statuswechsel)
SCRA: Komponentenliste nachdrucken (Ausschuss)
BFLU: Rückmeldung durchführen
POUT: Fertigmeldung aus der Produktion
DELI: Lieferung anlegen
DELR: Lieferungspositionen über VL02N löschen
DELD: Herausnehmen Teilegruppe aus Lieferung
DELU: Hinzufügen von Teilegruppe zu Lieferung
VL10: MAB-Lieferung aus VL10 erzeugen (DELS)
DLSP: Lieferung vom EDL an Kunde
GOIS: Warenausgang buchen
GOCC: Warenausgangsbuchung stornieren
MTCH und UDMT: Lieferquitt. auf abgeglichen setzen bzw. zurücknehmen
WFLW: Workfow-Ereignis auslösen
FINI: Teilegruppe abschließen
STAT: JIT-Abrufe in BW fortschreiben
ARCH: JIT-Abrufe zur Archivierung freigeben
REOR: JIT-Abrufe reorganisieren (löschen)

JIT Outbound

Master data

JIT& JIS Master data and basic objects

Define the customers, from whom you want to receive JIT calls.
Define the lead times of the JIT customer for the simple delivery scheduling.
Define the conversion of the external status information in your own external status description for each customer.
Define the destinations of the JIT customer. These are the unloading points and the assembly locations to which you deliver the components groups.
Define the components groups that you deliver to the destinations of the JIT customer.
Using the production info, you determine which call components you want to backflush or transfer.
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.

BOM

You usually require a BOM for the call components that you produce yourself. Then you can:

carry out a repetitive manufacturing backflush
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 confirmation.

You usually require a BOM for forwarded JIT calls outbound if you yourself produce components from the JIT call.

You may have an in-house production scenario as follows: You receive a JIT call from an OEM for which you directly forward JIT call components using a sequenced JIT call outbound and for which you also produce other components yourself. You create BOMs for the JIT components you produce in-house.

JIT Control Cycles ( JIT-Regelkreise )

You use the JIT control cycle to control replenishment for a particular material.

You assign a supply area, an external procurement strategy, a production call profile, and a scheduling profile to a particular material.

The scheduling profile is used for requirement time scheduling for outbound JIT calls.

If you work with a scheduling profile you can take into account factory calendars and shift sequences during the required time schedule. You also define with which call type you procure this material from which supplier.

Prerequisites

In Customizing, you have maintained the replenishment strategies for summarized JIT calls both for stock transfer and for external procurement.
In Customizing, you have defined a JIT call profile.
In Customizing, you have defined a scheduling profile.
You have defined a tolerance profile in Customizing, if necessary.

Transaction: PKMC.

Prd.synchroner Abruf

the production supply area, transaction PK05, which specifies the point at which the material is to be staged in production.
the external procurement strategy, which previously had to be created in JIT outbound customis to specify the movement type for the goods receipt for each plant.
the number including item for the purchasing scheduling agreement to indicate to which reference the goods receipt is to be posted for release. MM-SA: Z (Lieferplan für Produktionsabrufe)
Message control: Application PA
The production call-off profile
SD delivery - LAVA to post GR at 1 Tier

MAB-Regelkreis

Zusatzfunktionen für Regelkreise aktivieren

Lebenszyklusstatus in der Regelkreispfege

Produktionsabrufprofil

Source List

In the source list, you define from which supplier you receive a certain material. For outbound JIT processing, you define the following for materials you receive from a supplier; the order to be used for these materials and the period in which these materials are to be delivered from this supplier.

You use the source list when the information (supplier, delivery schedule) is not contained in the control cycle. The advantage of the source list is for example that you may want certain materials to be delivered in a certain period by supplier A and then in a later period by supplier B. You can make these settings in the source list. The advantage of the source list entries is that you do not have to change the JIT control cycle.

Material Master for Call Components

....

MM Scheduling Agreements

As the outbound JIT process is integrated into the scheduling agreement process, you require an MM scheduling agreement or an MM scheduling agreement item for each call component.

You can generate the schedule lines of the MM scheduling agreement in an MRP run or you can also create them manually.

In the JIT basic data, you have defined the relevant JIT suppliers.
You have created material master records for the call components.

In the Production Supply field, enter a Z for Scheduling Agreement for JIT-Calls.
Select the field Goods Receipt based Invoice Verification if you want to work with a delivery confirmation.

Contract type: LPA scheduling agreement with delivery schedule.
In addtion, the JIT delivery schedule indicator must be set in the material master.

At the item level:

Prod. supply: "Y" (sumJCs from kanban) or
Prod. supply: "Z" (sumJCs from SAP for Automotive)

Aggregation with the Release Creation Profile: creation rythm, aggregation of the schedule line quantity and the release horizon.

Releases for the Supplier (!)

Firm/trade-off zone 1 (go-ahead for production);
Firm/trade-off zone 2 (material go-ahead);
Binding with regard to MRP(!).

Process

Net requirements calculation;
Scheduling;
Updating the schedule lines;
Schedule line aggregation according to release creation profile;
Date and change-oriented release generation ( FDS/JIT ) according to the strategy in the profile;
Message Output.
Stopping Releases

General stop at scheduling agreement item level;
Stop when the variance tolerances defined in the SA release creation profile are violated.

If stock transfer scheduling agreements are used, Alternatively, the partner function LW for supplying plant can be set in the purchasing scheduling agreements, the vendor/business partner and in the JIT call profile. can be set.

Business partner: Vendor

Maintain the partner roles Order address (BA) or PAB Order address (BP). When creating the master data, there are no further specifications that need to be observed for JIT outbound.

JIT customer

JIT customer represents the business partner/debtor from whom sequence releases (MAB and PAB) are received. ( DE: Der JIT-Kunde repräsentiert den Business Partner/Debitor, von dem Sequenzabrufe (MAB und PAB) empfangen werden )

Transaction JITV is used to access JIT customer maintenance.
Using the description part it is possible to vary it for several plants or storage locations for one customer

Table: JITCU

* Das Kundenwerk muss damit auch im Debitor/Business Partner unter der Partnerrolle WE eingetragen werden + Unloading points are speicified in the business partner data
Zum JIT-Kunden muss eine Umsetzung der externen Statusinformation zum externen Status eingestellt werden.
*Eine weitere Einstellung zum JIT-Kunden sind die sogenannten Vorlaufzeiten. Über Vorlaufzeiten können auf Grundlage des Bedarfsdatums vom Kunden oder auf Basis des Zeitpunkts des externen Status das geplante Versanddatum gebildet werden.
** Mit der Destination und dem Teilegruppentyp detailliert man die Angaben des zu liefernden Produkts an den JIT-Kunden.
* Der Teilegruppentyp wird zur Destination angelegt und wird bei Anlage des Sequenzabrufes dazu verwendet, um mehrere Abrufkomponenten des OEMs in einer Teilegruppe, also einer logischen Gruppe von 1 bis n Materialnummern, zusammen zu fassen.
* Zum Teilegruppentyp wird die Abrufsteuerung hinterlegt. So kann man festlegen, dass eine Teilegruppe komplett anders abgewickelt wird wie die Andere.
Release order usage** ( Die Abrufverwendung ) is used in determining the JIT scheduling agreement ( SD-Lieferplan ) and is stored in Customizing for the sales document type for the SD scheduling agreement
S: Serie
E: Ersatz
M: Muster
JIT call type ( Abruftyp, The information is entered in the field ABTYP (release type) of the header segment E1KSJCL, SEQJIT)
S: Production-synchronous call-offs that is called off by a JIT customer (=PAB: Produktionssynchrone Abrufe).
D: Summarized JIT calls (=MAB: Mengenabrufe), which are called off by a JIT customer
I: internal call-offs to control business processes within an organization such as for example, the pre-production of frequently requested variants, which are stored in a buffer stock to be brought. ( die Vorproduktion von häufg gefragten Varianten, die in ein Puffer lager gebracht werden )
1..* External status mapping: The external status information shows the production progress at the customer. however, different customers often send different names for the same business content.
Ist das Feld für die externe Statusinformation in der EDI-Nachricht nicht gefüllt, wird bei der Umsetzung in den externen Status mit einem leeren Feld gearbeitet.
Profiles
Profile for comp. group : to a JIT customer assignment
Determines whether and with which priority the system considers specific logistics objects, when it assigns the call components of an incoming call to the components group types. It initially checks the mandatory objects and then the priorites in ascending order. As soon as a clear assignment is possible, the system ends the components group determination.
For example, you can define whether the system should check the match between the unloading point and the assembly location in the call component and components group. The components group determination does not depend on whether you use the process for assemblies (seqJC) or for discrete materials (seqJC, sumJC).
If you do not receive the components group material of the call component from your customer, you can take it from the call component before the components group determination. You can:
Transfer the call component material yourself; this is useful for discrete materials
Transfer the configurable material, which is entered in the material master record of the call component.
Control Profile for Summarized JIT Calls (SumJC)
With this profile you can determine, whether:
a change in the quantity of calls is permitted with or without quantity splitting
the calls should be provided with the status warning or alarm, from a certain time interval to the planned time of delivery.
Control Profile for the Delivery Creation ( Steuerungsprofl für Lieferungen festlegen )
This indicator allows you to define
whether a delivery is relevant for picking
whether and how handling units are generated on creating the delivery
whether and how a logistic quantity match is carried out
whether production numbers are transferred into the delivery IDoc
how the system calculates the open deliveries in successive delivery creation.
Control profile for Internal calls
Control profile for HU
Lead time settings for an external status , Vorlaufzeiten
Über Vorlaufzeiten können auf Grundlage des Bedarfsdatums vom Kunden oder auf Basis des Zeitpunkts des externen Status das geplante Versanddatum gebildet werden. Anhand des Tabellenmodells ist zu erkennen, dass nicht nur zum JIT-Kunden, sondern auch abhängig vom Teilegruppentyp und vom externen Status Vorlaufzeiten vergeben werden können.
The time is deducted from the base date/time in case of Bedarfsdatum and added in case of Datum des externen Status
Ist die Vorlaufzeitentabelle gefüllt, wird EDI-Eingang von SEQJIT-IDOCs aus dem Bedarfsdatum und der Bedarfszeit ein geplantes Versanddatum und die geplante Versandzeit errechnet. Wird keine Vorlaufzeit gepfegt, bleibt das Feld geplante Versanddatum und geplante Versandzeit leer.
JIT customer destination
Key, under which delivery-relevant data, such as the unloading point or assembly location, is recorded for the customer
Unloading point (Abladestelle) : the point at which the material is to be unloaded
Assembly location (Verbauort) at the customer's side
Component group type ( der Teilegruppentyp )
At the parts group level actions are performed and both the external status and the internal processing status.
The components group material is generally a configurable material and the call components are the corresponding configurable materials.
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 → Define Control Profiles → Define 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.
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.
Components group type ( customer-dependent )
Data inside
The production version of the components group material that you can enter (optional).
The control profile for internal calls
The destination
The material number of the components group material (optional).
The call control
The plant of the components group material.
Prerequisites:
The destinations for the components group types.
If necessary, a material master record for the components group material
The call control for the components group types in Customizing for JIT Inbound.
Signal monitoring
In the signal monitor you can track incoming JIT calls to a specific external status, dependent on the customer. For example, you can check the time which has elapsed since the last incoming call.

SD agreement

JIT scheduling agreements should be created with one item and therefore one material number for the performance reason.
LZJ: JIT scheduling agreement - JIT process without EDL and without delivery confirmation. Suitable both for PAB, MAB, and internal call-offs.
LZJE: JIT scheduling agreement EDL - JIT process with EDL.
JIT-Aktion DLSP (Lieferung vom EDL an Kunde)
Performance issue: Über eine zusätzlich entwickelte JIT-Aktion muss die Möglichkeit bestehen, eine Umlagerungslieferung zu erstellen, um die Materialien von einem beispielsweisen Versandlagerort in einen virtuellen EDL-Lagerort umzulagern
LZJQ: JIT scheduling agreement (LQ) - JIT process with delivery confirmation.
Unter Lieferquittierungen versteht man auch die Verarbeitung von Tagessammellieferscheinen (=TSL).
Im Anschluss daran werden Lieferquittierungsnachrichten vom Kunden in Form des Nachrichtentyps DELCON (Basistyp GSVERF03) im System verarbeitet und führen einen Mengenabgleich von gelieferten und vom Kunden bestätigten Mengen durch.
wird eine externe Faktura erstellt (Fakturaart FX)
Notes:
Ist dieses Kennzeichen gesetzt, wird bei der Anlage und Änderung eines JIT-Lieferplans mit dem Funktionsbaustein JIT02_SELECT_FROM_JITCU_ SB geprüft, ob der Auftraggeber in der Kombination mit dem Kundenwerk und der Abrufverwendung in der Transaktion JITV als JIT-Kunde angelegt ist.
JIT-Lieferpläne werden benötigt, um aus dem Vorplanungssystem des JIT-Kunden bzw. des OEMs Liefer- und eventuell auch Feinabrufe zu empfangen und zu speichern. Werden keine Feinabrufe vom OEM empfangen, besteht die Möglichkeit Feinabrufe aus Sequenzabrufen über die Transaktion JITH zu generieren. Wird die JITH nicht verwendet, sind die Sequenzabrufe nicht dispositiv relevant.
Der Bezug zur Produktionsnummer geht über die JITH verloren

Components Group Types

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.

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 defined the destinations for the components group types.
If necessary, you have created a material master record for the components group material.
You have defined the call control for the components group types in Customizing for JIT Inbound.

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 profile 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.

Component group type determination

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 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.

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 profile for the components group determination, you can define 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
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 activity Define 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).

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 configurable material of the call component as a components group material. To do this you must have entered the configurable material in the material master of the call component in the tab page Basic data 2 in the field Cross plant conf.mat.

SAP-Erweiterung JIT03_07 und Userexit EXIT_SAPLJIT03_007 ( see JIT: ABAP development )

Finding the part group via the production version is only possible if a production version is assigned to the call-off component in the user exit for input processing.

You have to set profiled differently for PAB/ Internal and MAB.

Components Group Material

The components group represents the assembly, the module or the system that you assemble from the call components transmitted and that you deliver. We 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.

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 configurable material and the call components are the relevant configured materials. You can also enter the call component directly as a components group material.

.....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.

The system determines the production line from the production version of the components group material
In sequenced JIT calls, the system determines the packing instructions from the components group material
The system determines the storage locations from the production version of the components group materials
Material type: KMAT
Assign it to components in the Basic data 2.

Production Info ( Transaction JITL )

With this function, you can define for each plant how the system handles the call components in the backflush.
If you create a call component in in-house production, you can choose the repetitive manufacturing backflush. In this backflush, the system posts the receipt of the goods for the call components and the backflush 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.
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 maintain entries with and without plant. As a default the system uses the entry with plant, if this is available.

Trigger the backflush with the actions BFLU (carry out backflush), BFLP (carry out backflush in the background), and BFDL (create backflush and delivery).... how the system handles the call components in the backflush.
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.
Else 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 to the receiving storage location.
Custom behavior
Set that the system does not post goods movement or that you can realize the movement of your own goods using a customer exit.
Repetitive manufacturing backflush
If we produce the call components by ourselves and a BOM exists in the system, we can post both the goods receipt of the call component as well as the goods issue of the components assembled in it (backflush).

Shared buffers
Die Aktualisierung des Shared Buffers fndet über die Transaktion JITR statt
Customizing
Call Control
Intern and External status

In the case of call-off control, a distinction is made between external call-off control and internal call-off control.
JITF - progress message: the entry into the transaction takes place with the JIT action. In the background, all call-offs are determined according to selection conditions including consideration of the internal processing status in which the action may be executed.
JIT6 - JIT action entry: the entry into the transaction also takes place  with the JIT action, for which all call-offs are selected that are in the associated internal processing status. The difference to transaction JITF is that the The difference with transaction JITF is that the entry object, e.g. the production number or the grouping number (= order number) must be entered manually. Transaction JIT6RF uses the same same logic, but is optimized for RF devices.
JIT7 - JIT action entry with default: the entry and logic of the programme correspond to the logic of transaction JIT6 or JIT6RF. In transaction JIT7 however, the next sequence number of the JIT call to be executed in the internal processing state of the desired JIT action is displayed. Transaction JIT7RF performs the same logic, but is optimised for RF devices.
JITM - JIT monitoring: JIT monitoring can be started with various settings and selection conditions and selection conditions.
JITK - summarized JIT calls due for dispatch: a separate dispatch monitor is available for summarized JIT calls, which can be specially set in Customizing. The monitor requires the JIT action VL10, which must be stored in the call-off control.
The execution of the JIT action from the JIT Cockpit (transaction JITG) cannot be recommended for reasons of not recommended due to user-unfriendly handling.

JIT action: Inbound or/and Outbound, only automatic?

JIT Inbound
Aktion CREA: JIT-Abruf anlegen
Only when JIT production number has not been created for a JIT customer. if it exists, then update ( action MODI ) is carried out. Reorders are not changed via EDI messages, only via transaction JIT2. The sign for Repeate order is stored in the header table.
MODI, MODH, MOD*: JIT-Call change
MODI action changes the entire JIT call-off, data on the call-off scope, the part group and call-off components.
MODH action modifies the call-off scope and part group data. There is no update of the call-off component data. A change is always EDI input always by external status information/external status.
MODG action only changes the parts groups of the JIT call-off and no call-off components.
MODC action only changes the call-off components of the JIT call-off and updates the part group data, as a change of the external status and the internal processing status takes place at part group level.
MDSC action performs various functions depending on the CHANGETYP field in the SEQJIT-IDOC from the segment E1PSJC
If CHANGETYP has no value, no change is performed.
If CHANGETYP=01, the retrieval component is the call component is transferred to the part group.
If CHANGETYP=02, the call component is deleted from the part group.
If CHANGETYP=03 the quantity for the call-off component is changed. In addition, the part group data is updated to update the external status and the internal processing status.
INSC inserts call-off components into the part group. The action thus corresponds to the action MDSC if CHANGETYP=01. However, no CHANGETYP must be
If the MODI action is executed and the JIT call-off does not yet exist in the database, the JIT call-off is created in the system.
JIT2: Ändern eines Abrufs über Trans. JIT2
CGAP: Teilegruppe hinzufügen (MAB)
The JIT action CGAP duplicates already existing parts groups for summarised JIT calls which are transmitted via EDI.
CANC: Teilegruppe stornieren
If a call-off can be cancelled, a process must also be cancelled, how a cancellation can be cancelled. If the call-off remains cancelled, it must be be checked from when in the process the cancellation was carried out. If the parts group has already been built, it must be temporarily stored or even dismantled, depending on the process. The JIT action CANC only carries out a status change of the internal
processing status and the external status. No further logic takes place.
DLET: Teilegruppe löschen
The JIT action DLET is used in the call-off control to delete a parts group from the JIT call-off. This is useful if the JIT customer transmits other call-off components to a different part group during a repeated call-off as in the previously transmitted JIT call-off. DLET is also an internal action and is only executed via EDI.
DELC: Komponente löschen
With the JIT action DELC, call-off components can be deleted from created JIT call-offs (MAB, PAB and internal call-offs). If only individual retrieval components are to be deleted from the retrieval, then the retrieval components that are already stored in the database must also be included in the SEQJIT-IDOC and have different external status information so that the JIT action DLET is not executed.
CGRP: Gruppierungsinfo generieren und zuweisen
Number range object: JIT_GR_01. The grouping information is stored for the part group in the table JITIT in the field GRPIN, GRIND ( how many groups ?) field.
PICK und PCOM: Komponentenliste/=Kommissionierliste drucken
HUPP: Handling Unit in Produktion erzeugen
The JIT action HUPP creates a handling unit (=HU) for one parts group each in a process for MAB, PAB or internal call-offs.

When creating the SD delivery via the JIT action DELI the handling unit is included in the SD delivery.

When executing the JIT action HUPP, the same logic is executed as with the JIT action CRHU, except that the HUPP action does not require a profil for internal calls. HU number is set in JITIT.

A packing instruction is required. When using packing instructions, make sure that When using packing instructions, make sure that a packing instruction is stored on the packing instructions must be stored on the parts group material.

In order for the JIT action HUPP to be executed, a handling unit profl must be defined in the SAP JIT. The HU profil is assigned to the part group type under the JIT master data.

JIT03_02 und Userexit EXIT_SAPLJIT12_003

DEHU: Auspacken und Löschen Handling Unit
The JIT action DEHU performs the unpacking of the call-off components from the handling unit and the subsequent deletion of the HU. The reference of the handling unit at the part group level is set to initial.

The call-off components that have been unpacked from the handling unit are transferred back to the "from storage location" (movement type 311).

CRHU: Handling Unit für int. Abrufe erzeugen
No handling unit profil is required for the CRHU action. The relevant information for the formation of the handling unit is read from the control profile for internal calls. JIT03_02 und Userexit EXIT_SAPLJIT12_003.
SWCG: Teilegruppe austauschen (interner Abruf)
Select two part groups from different JIT calls.
One should have the indicator for internal JIT call ( Übergabe an Prod. )
Both part groups must have the same components and the same JIT SD SA
Profile for Internal calls should allow exchange
WIN: Einlagern in TG-Pufer (interner Abruf)
The JIT action WIN performs a relocation of the call-off components for internal call-offs (call-off type=I) with movement type 311.

Storage location is set in the Production version of the group component material.
WOUT: Auslagern aus TG-Pufer (interner Abruf)
The JIT action WOUT is the counterpart to the action WIN and stores the call-off components back to the receiving storage location from the production version of the parts group material (movement type 311).
PSWC: Druck Teilegruppentausch (Puferabruf)
PIN: Übergabe an die Produktion
The JIT action PIN sets the indicator "Transfer to production done" at the level of the parts group. If the call-off has not yet been created in the system, the JIT call-off is created via the PIN action.

Erweiterung JIT04_04 mit dem Userexit EXIT_SAPLJIT04_004.
NIO: Fehlteilmeldung (Statuswechsel)
On the process side, the action NIO is used when a feedback - for example from an MES system - has been processed and the assembly of the parts group was "not OK".
SCRA: Komponentenliste nachdrucken (Ausschuss)
The SAP user (for example, the production manager) receives information via the ExpressMail that a parts group from production has been reported as "not OK" (= reject). has been reported as "out of order" (= rejects).
BFLU: Rückmeldung durchführen
With the JIT action BFLU, two goods movements defined in the SAP standard can be carried out. On the one hand, the stock transfer of call-off components from one storage location to another storage location and, on the other hand, the backflush in series production.

When transferring components, movement type 311 is used and the storage location is taken from the production version of the parts group material. A prerequisite for this is that a production version has been created for the part group material and that it has been and that this is stored in the JIT master data in transaction JITV for the part group type.

The definition of which BFLU variant is used in the process takes place via the transaction JITL.
POUT: Fertigmeldung aus der Produktion
JIT action POUT carries out a change of the internal processing status and sets the indicator "Finished message from production" (field RUECK) at the part group level.

If a customer-specific finished message is to be executed, the extension JIT04_04 with user exit EXIT_SAPLJIT04_005 is available. The user exit is used to save grouping and sorting information after production on the parts group.
DELI: Lieferung anlegen
Create delivery with FM RV_DELIVERY_CREATE. After processing, set the sign in JITIT.
Für die Liefererstellung gibt es den Userexit EXIT_SAPLJIT03_015 in der Erweiterung JIT03_10.

with EWM: JIT specific data can be obtained from the EWM via the RFC module JIT08_GET_PRODN_IN_DELIVERY and the import parameter of the SD delivery in order to store part group information, sequence number, production number and other data and use them for a feedback.
DELR: Lieferungspositionen über VL02N löschen
VL02N: Delete a delivery. Reset the sign in JITIT.
DELD: Herausnehmen Teilegruppe aus Lieferung
The JIT action DELD enables the removal of the call-off components of a parts group from an SD delivery. The prerequisite for using the DELD action is an existing an existing SD delivery that was created via the JIT action DELI. The sign is reset.
DELU: Hinzufügen von Teilegruppe zu Lieferung
With the help of the JIT action DELU, call-off components from parts groups can be added to the existing SD deliveries.
VL10: MAB-Lieferung aus VL10 erzeugen (DELS)
The JIT action VL10 is an internal action and is executed via the transaction JITK - summarised JIT calls (call-off view). This programme is a dispatch monitor for summarised JIT calls due for dispatch in order to create SD deliveries with the JIT action VL10.
DLSP: Lieferung vom EDL an Kunde
With the help of the JIT action DSLP, the EDL withdrawal can be created in the SAP system when the delivery is made from the external service provider to the customer.
GOIS: Warenausgang buchen
WS_DELIVERY_UPDATE_2
GOCC: Warenausgangsbuchung stornieren
VL09
MTCH und UDMT: Lieferquitt. auf abgeglichen setzen bzw. zurücknehmen
A check of the logistical reconciliation can be carried out for the user via transaction DLC2. This report shows the user which items have been confirmed and not confirmed. The manual reconciliation of the delivery confirmation takes place via transaction DLCN.
If the "Adjustment" button is pressed, the JIT action MTCH is executed. JITIT-AGTSL = 'X'
The button "Adjustment back" executes the JIT action UDMT. The sign is reset.
WFLW: Workfow-Ereignis auslösen
The JIT action WFLW triggers a workfow event with the module SAP_WAPI_ CREATE_EVENT and cannot be used in the SAP standard without further development adaptation.
FINI: Teilegruppe abschließen
The action performs a pure change of the internal processing status.
STAT: JIT-Abrufe in BW fortschreiben
ARCH: JIT-Abrufe zur Archivierung freigeben
Setting up archiving for JIT calls in JIT inbound is done via transaction JITY.
REOR: JIT-Abrufe reorganisieren (löschen)

JIT Outbound
Nachrichtenkonditionssatz zur Erzeugung des SEQJIT IDOCs. Application PA ( roles: LI, LW )
MAED (MAbrufe (EDI))
MAFO (MAbruf Druckformular)
The condition records can also be maintained via the transactions PJNK1/PJNK2/PJNK3.

FM JITOUT04_SET_ACTION_INTERN
BAdI – JITO_ACTION

OCRE: Outbound-Abrufe generieren
The JIT action OCRE generates a JIT outbound call-off from a JIT inbound call-off. and forms the basis for generating a SEQJIT03-IDOC.
A control cycle must be created in the corresponding plant for each material in the JIT inbound parts group.
In the control cycle, the external procurement strategy must be specified, which describes, with which movement type the goods receipt is posted.
The details of the purchasing organisation, the relevant vendor/business partner and the purchasing scheduling agreement number as well as the item number containing the material to be called off complete the details in the control cycle.
In addition, it must be ensured that a valid order book record is available, since the JIT action OCRE checks the order book before generating the JIT outbound call-off. on the source list before generating the JIT outbound call.
The planned requirement date is from the planned dispatch date of the inbound parts group. A special calculation date can be calculated for summarised JIT calls via the time defnition and the scheduling profiles in JIT outbound customising.

At the end of the creation of the JIT outbound call-off, the function module JITOUT04_ACTION_SEND_PREPARE is called, which generates the SEQJIT03-IDOC.

This module is also called in the JIT actions OSDP and OCRS

Additional fields:
Type of reference number "CC": the control cycle number is written into the reference number.
Type of reference number "PV": a different packing instruction is written in the reference number.
Type of reference number "CN": the number of load carriers is written into the reference number.
Type of reference number "BC": batch characteristics are written in the reference number.
Type of reference number "OP": the part group key of the JIT outbound call-off is written into the reference number is written into the reference number if the field GRPIN (=grouping information) is filled. If the field Grouping information is not filled, the outbound part group key is transmitted into the GRPIN field.
Reference number type "SA": the purchase delivery schedule number is written into the reference number.
Type of reference number "SI"=the position in the purchasing delivery schedule is written into the reference number.
BAdI JITO_IDOC, Methode CHANGE_IDOC_JITCALL

JITIT Feld OUTEX - a sign after action

The JIT action OCRE is also executed when creating summarised JIT calls, z. e.g. via transaction PK23.

OMOD: JIT-Outbound-Abruf modifzieren

The JIT action OMOD is also executed when changing summarised JIT calls, z. e.g. via transaction PJ02.

In the process, the combined use of the MODI and OMOD actions makes sense when a call-off is sent from the OEM to the 1-tier supplier and this is immediately passed on to the 2-tier supplier or to the partner production facility.

OAPP: Teilegruppe zu Outbound-Abruf hinzufügen
Mit Hilfe der Transaktion PK23 und der JIT-Aktion OAPP werden einem vorhandenen Mengenabruf eine Teilegruppe hinzugefügt

OREP: Outbound-Abruf senden: Nachr. erzeug. WH
The JIT action OREP is responsible for re-issuing a SEQJIT03 IDOC. This is always necessary if a change has been made to the JIT outbound call-off and the and the update is sent by EDI message to the 2-tier creditor/business partner or to another or to another production site of the 1-tier supplier.

OSDP: Outbound-Abruf senden: Nachricht erzeug
The JIT action OSDP executes the same functional logic as the action OREP. With exception that it checks whether an IDOC has already been generated. If the latter is the case, processing is exited with an information message, that an IDOC has already been generated. No new SEQJIT03 IDOC is generated.

OSDD: Outbound-Abruf senden: Nachricht verarb
The JIT action OSDD is responsible for processing SEQJIT03 messages.
The use of the JIT action OSDD is always useful if no IDOC is sent directly via the JIT outbound call-off generation with the JIT action OCRE, but only generated.

OGRE: Wareneingang zu JIT-Outbound buchen
After each goods receipt processing, the number status of the delivery confirmation is counted up and and saved accordingly in the reference tables for outbound delivery confirmations (table DLCNOHD, DLCNOCO, DLCNORF).

Via inbound processing, an MM inbound delivery is created with reference to the purchasing scheduling agreement at the 1-tier supplier with the process code DELS (function module IDOC_INPUT_DESADV1).
E1EDL52 Qualifer PRN für die Positionsebene

Incoming despatch advice IDOCs can be monitored via transaction EMASN.

For both MAB and PAB, the transaction Alternatively, the transaction PJWE can be used for the goods receipt posting for both MAB and PAB.

Both the JIT action OGRE and the programme for transaction PJWE call the goods receipt function module JITOUT09_UPDATE_AFTER_GR.

OCGR: Wareneingang stornieren
VL09

OSHP: Avis zum Outbound-Abruf verarbeiten
The JIT action OSHP does not execute any further business logic, but sets the indicator "Shipping notification for JIT outbound delivery" at the part group level of the JIT outbound call-off and enables the jump from the transaction JITOM to the inbound delivery.

All links of summarised JIT calls as well as the production-synchronous calls to the shipping notification are stored in the table PABASN.

OCSH: Aus Anlieferung löschen
If an existing delivery is updated or cancelled via a new ASN, the function module for the action OSHP is automatically called and the assignment of the ASN as well as the indicator "ASN received for JIT outbound" are corrected. Conversely, this means that the JIT action OCSH  must be allowed in the desired internal processing status in the call-off control if the inbound delivery is changed, for example also if the inbound delivery is to be deleted.

ODLC: Outbound-Abrufe: Lieferquitt. Senden
Der OEM sendet einen JIT-Abruf
Über das SEQJIT03-IDOC vom 1-tier Zulieferer wird beim 2-tier Zulieferer ein JIT-Abruf erstellt.
Bei der Erstellung der Auslieferung beim 2-tier Zulieferer wird über die Nachrichtenart LAVA ein DELVRY07-IDOC erzeugt (Lieferavis), das beim 1-tier Zulieferer automatisch eine Anlieferung generiert. Über die JIT-Aktion OSHP wird das Lieferavis dem Abruf zugeordnet. Die JIT-Aktion OGRE verbucht den Wareneingang und erzeugt einen Materialbeleg.
Der erzeugte Materialbeleg ist die Grundlage für die JIT-Aktion ODLC, damit das GSVERF03-IDOC für die Lieferquittierung erzeugt werden kann. Die Lieferquittierung bestätigt den Wareneingang beim 1-tier Zulieferer und ermöglicht im Anschluss die Erstellung der Rechnung beim 2-tier Zulieferer.
Die Lieferquittierungsnachricht erzeugt beim 2-tier Zulieferer automatisch eine externe Faktura. Voraussetzung ist allerdings, dass als JIT-Lieferplanart die Belegart LZJQ verwendet wird. Über die JIT-Aktion MTCH kann abgeglichen werden, welche Fahrzeuge geliefert und welche abgeglichen wurden.
Three main functionalities can be carried out in the ODLC monitor (transaction ODLC):
Lieferquittierung abschließen
Lieferquittierung löschen
IDOC für die Lieferquittierung versenden
A delivery confirmation can also be entered manually by using transaction ODLCM, the vendor/business partner number, the ordering party and the partner description are entered.

JITOUT07_IDOC_CREATE_DELCON

OCNF: Bestätigen von JIT-Outbound-Abrufen
The action would set an indicator on the JIT outbound part group (CONFR field)

ORDC: Material zu Lieferquitt. hinzufügen
The JIT action ORDC is always executed when a call-off component is to be is to be added manually to a delivery confirmation.

OTCR: TA zu JIT-Outbound erzeugen
The JIT action OTCR is classically used for summarised JIT calls and creates a WM transfer a WM transfer order for each group of parts. However, there are no restrictions to use the action also for production-synchronous JIT outbound calls.

OTCA: TA zu JIT-Outbound stornieren

ODLI: Auslieferung zum JIT-Outbound erstellen
The action is always used for MABs when a stock transfer within a plant or a posting change from a WM-managed storage location to an IM-managed storage location is to be carried out. The JIT action OTCR cannot be used for this, but the JIT action ODLI must be used, which uses an outbound delivery for a stock transfer of the materials.

OCDL: Auslieferung zum JIT-Outbound über VL02N löschen
The SD delivery is deleted via transaction VL02N and the reference to the part group is removed via JIT action OCDL.

OFIN: Outb. Teilegruppe abschließen
With the JIT action OFIN it is possible to complete the JIT outbound call-off. Thereby As with the inbound action FINI, the internal processing status is changed. is carried out. In addition, on the call-off component level of the outbound call-off the field goods receipt status (technically: GRDON) is set to "1" (=completed), if it was not already set to 1. The goods receipt status is normally set by the JIT action OGRE.

OARC: Archivierung Outbound-Abrufe
This has no function logic and is executed as an internal action by the programme of transaction JITOA.

Transaction JITOA behaves similarly to transaction JITY for archiving inbound calls. The archiving object JITO_CALL used can therefore also be therefore also be used via transaction SARA.

OREO: JIT-Outbound-Abrufe löschen
With the JIT action OREO, the JIT outbound delivery schedule is deleted in its entirety. All tables that refer to the JIT outbound such as additional texts, goods receipts, links to transfer orders, shipping notifications or delivery confirmations are also reorganised.

JIT Call Profile
Assign a JIT call profile to a control cycle, thereby setting the automatic controls for all JIT calls created via this control cycle.

Defines the partner function in which you determine the output partner for the transmission of the JIT call.  Through the output partner, you control the grouping of JIT calls and the telecommunication of the calls (determination of the corresponding partner table in the vendor master record).
Determines whether and how you group material requirements.  You can group requirements according to plant or plant and unloading point.
Determines the period of time in which the requirements are grouped to a call.  You group all requirements whose delivery dates lie within the same period of a time defintion.
Time Definition
Customizing of JIT outbound offers the possibility of combining material requirements for summarised JIT calls at the exact time or on the exact day.

In summarizing to the day, you can define that the period on which the summary is to be based is 3 days. This is defined in the planning calendar, which you enter here along with the appropriate plant. The system summarizes the requirements whose delivery dates fall within this period.
Scheduling Profiles (MAB)
The system uses a factory calendar, a grouping, and shift sequence to determine the Operating time for a scheduling profile. The system then uses this operating time to execute forward scheduling taking the total replenishment lead time into account to determine the requirements date.

Shift Sequences
Using the grouping you can create shift sequences and shift definitions for special areas (for example, different plants or different areas of a plant) and when maintaining the available capacity choose from between work centers.You can assign the shift sequence of a capacity category as the available capacity at the work center.You define a sequence of shifts per weekday. The shift sequence represents a collection of shift definitions.
In capacity planning the system uses the predefined values from the shift definition to determine the available capacity of a work center.

External Procurement Strategy for Sequenced JIT Call ( Fremdbeschafungsprofil )
Determine the movement type to be used for posting the goods receipt.

Tolerances for delivery integration (MAB)
In the processing of the JIT action OMOD (transaction PJ02), all the deliveries assigned to the outbound parts group are selected and the tolerance profil is read. In the case of inbound deliveries for which no goods receipt was posted, the settings of the tolerance profile can be applied.

Use these tolerances in JIT Outbound, for example for selecting releases and creating alerts.

The tolerance profiles are assigned in the MAB control Cycle.

Summarized JIT Call
Define Replenishment Strategies for External Procurement

Define Replenishment Strategies for Stock Transfer

Define Scheduling Profiles
Define Storage Location Vendors
The summarized JIT call replenishment strategy can be a stock transfer. A storage location vendor is used to find a summarized JIT call during stock transfer of an output partner. This output partner is necessary for a summarized JIT call output.

The summarized JIT call creation process is detailed below:
To trigger the message control, the system accesses data from the control cycle in the Event-Driven KANBAN: Create Kanban.
The system then uses the production supply area-storage location to determine the storage location vendor.
The system then uses the partner roles from the JIT call profile and the partner roles from the Display Vendor: Initial Screen to determine the output partner.