Example for the Summarized JIT Call

Example for the Summarized JIT Call

Use

This section shows you, by means of a complex example, the options available with the summarized JIT call. The structures and functions described in the units Creating and Transmitting a Summarized JIT Call and Grouping Kanbans to a Summarized JIT Call are used here.

You have the following scenario:

Your vendor VEN1 delivers three materials from two different plants: MAT1 and MAT2 from North plant and MAT3 from South plant. For each of these materials there is a scheduling agreement.

The forecasts, that is to say the forecast delivery schedules for the scheduling agreements, are transmitted to the vendor’s headquarters. For the material MAT1, this forecast is also transmitted to the subvendors SUBVEN.

You want to send the summarized JIT calls directly to the vendor’s plant, without delivering the material. In addition you want to transmit the summarized JIT calls, which you are sending to South plant, to the carrier CARR.

You want to summarize the material requirements for MAT1 and MAT2, which are delivered from North plant, in a summarized JIT call.

Prerequisites

You have created a vendor master record for all the partners you want to send messages to. These are the vendors VEN 1, VEN1_North, VEN1_South, SUBVEN and CARR.

The following partner functions exist: VN (vendor), OA (ordering address - headquarters), OJ (ordering address JIT call), CR (carrier), SV (subvendor).

In the vendor master record you have entered the vendors with their partner functions.

You assign all partner functions, which are necessary for this processing, to VEN1 as headquarters. For North plant you only require the partner functions VN and OA; for South plant you also require the partner function CR, because you want to transmit the summarized JIT call not only to the plant but also to the carrier.

_Vendor	VEN1	VEN1_North	VEN1_South
Partner functions with message partner	VN - VEN1	VN - VEN1_North	VN - VEN1_South
	OA - VEN1	OJ - VEN1_North	OJ - VEN1_South
	OJ - VEN1_North		CR -SPED
	OJ - VEN1_South
	SV - SUBVEN

You can only take on those partner functions in the scheduling agreement which you have also maintained in the vendor master record.

You have defined scheduling agreements with partner functions for vendor VEN1 for your materials.

As the forecast delivery schedules are transmitted to headquarters, you must enter partner function OA - VEN1 for all materials. For MAT1, the forecast delivery schedule must also be sent to the subvendors. You therefore select the partner function „SV: MAT1 and MAT2 are delivered from North plant". For both of these scheduling agreements you enter the partner function OA - VEN1_North, so that you are later able to summarize material requirements. For South plant enter the corresponding partner function OJ - VEN1_South.

_{Scheduling agreement/ material}	SA_MAT1	SA_MAT2	SA_MAT3
_{Partner functions in the scheduling agreement}	VN - VEN1	VN - VEN1	VN - VEN1
	OJ- VEN1	OJ - VEN1	OJ - VEN1
	OA - VEN1_North	OA - VEN1_North	OA - VEN1_South
	_{SV - SUBVEN}

In the control cycle of materials MAT1 and MAT2 you have created a JIT call profile, which contains the partner function OJ. The system therefore summarizes your summarized JIT call according to VEN1_North and VEN1_South.

You have set the message determination for the scheduling agreements in such a way that messages are found for the partner functions or the partners OJ - VEN1 and SV - SUBVEN.

You have set the message determination for the summarized JIT calls in such a way that messages are found for either the partner functions or the partners OJ-VEN1_North or OJ-VEN1_South and CR - SPED. See also Structure of Message Determination.

Process Flow

You are starting a planning run.

The planning run generates a schedule line.

You transmit this schedule line as a forecast delivery schedule to OJ - VEN1 and in the case of MAT1 also to SV - SUBVEN.

The system carries out the message determination for the schedule line with the partner table, which is maintained for SA_MAT1.

You set a kanban for MAT1 to EMPTY or you generate an event-driven kanban.

If there is still no applicable summarized JIT call available, to which the material requirements can be attached (same vendor, same message partner, same plant), then the system generates a new summarized JIT call.

In generating a summarized JIT call, the system carries out message determination. The system finds the message via the vendor master record using the partner function(s) and message partners.

The system carries out this message determination with the partner table, which is maintained for VEN1_North in the vendor master record.

You set another kanban for MAT2 to EMPTY or you generate an event-driven kanban.

The system checks whether this requirement can be attached to the current summarized JIT call, in other words whether the vendor, message partner and plant are identical.

Whether or not the message partner is the same, the system can check the JIT call profile. It contains the partner functions, through which the system can determine the message partner in the scheduling agreement.

In our example, the JIT call profiles from MAT1 and MAT2 contain the partner function OJ. The message partner VEN1_North is assigned to the partner function for both materials.

If all necessary entries match, then the system attaches the material requirements to the current summarized JIT call as an item In this case, the summarized JIT call contains material requirements from two different scheduling agreements. The system does not carry out a new message determination.

For all further material requirements, the system carries out the same review.

If you do not want to transmit the message, then the system reads the data in the summarized JIT call and transmits this message to VEN1_North.

In the case of MAT3, the system would transmit the message to the South plant and also to the carrier.