Output of Purchasing Docs. (Message Determination) 

Purpose

The system always carries out the message determination process when you create an RFQ, a purchase order, a contract, an outline agreement, a scheduling agreement release, or a standard delivery schedule under a scheduling agreement. " Message determination" means that the system searches for a message record whose default values match up with the values from the relevant purchasing document.

Prerequisites

Process Flow

  1. You create a purchasing document.
  2. The system carries out the message determination process. This is based on the condition technique. (See the documentation Cross-Application Components under CA – Message Control for more on this topic.)
    1. The system assigns the message determination schema that is valid for the purchasing document. The schema contains the message type.
    2. The system searches the condition tables for a valid message record (e.g. for the document type) via the access sequence assigned to the message type.
  3. If a message record is found, the system generates a message for the purchasing document using the data of the record (transmission medium, transmission time-spot etc.) and places it in the message queue.
  4. You can view an analysis log of the message determination process as well as the message itself in the purchasing document via Header ® Messages. At this point, you can also change the output criteria for the message (see Changing the Output Criteria).

    Note that the analysis log is not saved and is only available immediately following the message determination process.

  5. The message is outputted from the message queue in accordance with the specified transmission time-spot. (See Outputting Messages.)

If the associated document is subject to a release procedure and has not yet been released (approved), the system will generate the message but you will not be able to display or output it.