Entering content frameProcess documentation Structure of the Message Determination Locate the document in its SAP Library structure


This process describes how the message determination is carried out in the case of a summarized JIT call. Message determination always appears when you create a new JIT call.


You have determined the necessary prerequisites for the summarized JIT call (control cycle with appropriate replenishment strategy, scheduling agreement etc.) Please read Creating and Transmitting a Summarized JIT Call.

In the SAP standard system, Customizing is already set for the message determination. However, you can carry out extensions in the customer name period. For the message determination the following are necessary:


Condition records are not provided in the SAP standard system; you have to fill out the condition tables yourself.

Detailed information on message determination can be found in the section Message Determination ff.

Process Flow

  1. You set a kanban to EMPTY or you generate an event-driven kanban, for which the replenishment strategy is planned as JIT call.
  2. The system checks whether a new JIT call is created or whether this material requirement as an item is attached to an existing JIT call.
  3. If a new summarized JIT call is created, the system opens the message determination.
  4. The system checks whether there is a condition record available in the condition table, whose content matches the data of the kanban which has either been set to EMPTY or which has been created (e.g. plant and JIT call profile or plant, JIT call profile and vendor).


The Customizing settings for message determination schema, partner function and message type determine which messages have been permitted and which partner functions can be used with these message types.

When searching for suitable condition records, the message determination covers the tables in the message determination schema, partner functions and message types.

  1. Since condition records are created for a specific message type, the system can create a message when the message determination has found a corresponding condition record.
  2. Using the partner function in the JIT call profile, the system can find the message partner, to whom the message is to be transmitted, with the vendor master record. The vendor, who is maintained in the corresponding scheduling agreement with this partner function, is transferred into the JIT call as message partner.

  3. You can now transmit the message.
  4. On issuing the message, the system reads the data from the JIT call and its items (e.g. in case items have been added after the creation of the message) and transfers this data to the vendor.

Example for Message Determination Structure

This graphic is explained in the accompanying text



Leaving content frame