Message determination in Purchasing includes:
- Message schemas
- Message types and fine-tuned control
- Access sequences and condition tables
- Partner roles for outputting messages
- Printer determination
- Change messages
Messages are an important means of communication with suppliers in relation to purchase transactions.
You can send messages through the postal service or electronically. A message-control facility, dependent on a number of different criteria, enables you to process and send these messages subject to certain conditions and with predefined restrictions.
The message determination process enables you to output messages on a variable and differentiated basis. Message determination is a variant of the condition technique.
In addition to the settings for message determination, you need to assign printers for print output.
When you create or change a purchasing document, for example, a Request for a Quotation (RFQ), a purchase order (PO), or an outline agreement, the system checks whether it has to create an output format for this document. A document in output format represents a message.
Message Output
Message Output with Message Determination
To use message control via NAST, you must first ensure that SAP S/4HANA output management has not been activated.
Then, you must assign a message schema to each purchasing document category.
If no message determination schema is assigned, the system cannot perform automatic message determination for the corresponding purchasing document category.
Working with message schemas results in the following:
- Any message type can be output.
- In case of print output, the system determines the printer in the following sequence:
- Output medium and dispatch time can be defaulted, depending on the concrete values of influencing factors, such as document type and supplier.
The purpose of message determination is to output messages in accordance with predefined criteria.
With message determination, the system checks whether condition records exist for the actual application data in a purchasing document. The condition records specify how, when, where, and how often a message should be output. If condition records exist, then the system can generate and process (for instance, send electronically) one or more messages. Without a valid condition record, the system cannot generate a message automatically.
Example — Result of Message Determination
What does message determination enable you to do? For instance, message determination enables you to control the document output process for each supplier on an individual basis.
Depending on the actual application data in the document, you could specify the following options:
- Transmit purchasing documents for particular suppliers by EDI.
- Send purchasing documents with a particular document type to certain suppliers by fax.
- Print purchasing documents for the remaining suppliers.
In this example, the program uses different message records (condition records) for the outputs.
Example of Message Determination Process
With the relevant application data that you want to use for message output, condition tables must be created in Customizing.
In the message determination process, the system searches the condition records depending on the condition tables in a predefined sequence (the access sequence).
You can take into account various dependencies with the three different condition tables in the figureExample — Message Determination Process. Thus, supplier A can receive every purchasing document by EDI whereas supplier B only receives purchasing documents belonging to particular document types by fax.