message determination in purchasing

8/9/2019 Message Determination in Purchasing

1/13

Message determination in Purchasing

Overview

This document includes an overview of relevant settings in Customizing for PO and shows with an example how to create anoutput type for a PO.

IntroductionThe printing program does not only confess with the output of purchasing documents on the printer but with all methods of

getting the documents to the vendor. This can be a printout but also sending a purchasing document by fax or !"mail.The

same program and form are used for the output of several documents and processes.The documents that can be output are#

$e%uest for %uotation

Purchase Order

Contract

&cheduling 'greement (elivery &chedule

The processes that re%uire the output of a document are#

Creating a new document

Changing an existing document

Creating a new delivery schedule for a scheduling agreement

)rging*reminding a delivery

(ifferent programs are involved in creating and sending messages. Our programs are &'PMM+,! &'P-M+,P and the

function groups M!PO M!($)C and M!($. -rom basis it is mainly $&/'&T++ and $&/'&T!( 0for !(I1. -or more

details see the 2I I page 3Print processing programs3. The message determination uses the same condition techni%ue as it

is used in Pricing. 4enerally spea5ing a message type is the same as a condition type but the term 6condition type7 is more

generic. Messages serve to send a purchase document or a dunning*reminder of a purchase document to the vendor.

Messages can be created and sent for $e%uest for 8uotations 0$-81 Purchase Orders 0PO1 scheduling agreements

delivery schedules and contracts.To transmit a message you can use different media li5e printer fax !(I !"Mail or

&'Poffice. To set up the message determination of purchasing documents you have to assign a message schema to apurchasing document. 9ut setting up the message determination of purchasing documents is not mandatory. 2hen creating

or changing a purchasing document the message determination will be always processed. The system loo5s up the

message schema that is assigned to the purchasing document. !ach schema contains several message types. The

message types themselves are lin5ed with condition tables which contain the condition entries. -or each message type

there is an access se%uence that determines in which se%uence the condition entries for a message type are loo5ed up. If a

valid condition entry is found then the message type of that entry will be chosen and a message in the purchasing

document will be created. The relevant data of the message will be ta5en from the condition entry e.g. partner medium

dispatch time. The schema summarizes this concept
http://wiki.scn.sap.com/wiki/display/ERPSCM/Message+determination+in+Purchasinghttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/display/ERPSCM/Message+determination+in+Purchasing


2/13

Customizing

The Customizing can be found in transaction O:M! ; Messages.

Message Determination Schemas

It is possible to maintain a message procedure and assign it to an application in Output Control ; Message determination

&chemas ; (efine Message &chema for PO.


3/13

Maintain Message Determination Schema


4/13

Assign Message Determination Schema

In this step we assign schema to the application# it is possible to define more than one schema but only one schema can

be assigned to one application# for example the standard procedure $M9!-< is assigned to application !- i.e. PO . To ma5e

sure that the message determination wor5s properly the flags 6/7 for message determination 0T 0T


5/13

Maintain Message Types for PO

In this step we define the message types for purchase orders.

In the details for the message type we can see several tabs.

General data


6/13

Ma5e sure that the f lags for 6'ccess to conditions7 and 6Multiple issuing7 are set. The flag for 6Multiple issuing7 allows sendingmessages multiple times to the same partner 0this is relevant for urgings and reminders1. If the flag for 6partner"independent

output7 is not set the system allows only certain partner roles for the message determination. To create change messages

properly the program -M+,'!/( and the form C@'/4!A-:'4 must be maintained. In case you want to send a message

via !"mail and provide purchasing"document"specific information in the title of the !"mail you need to maintain the area

$eplacement of text symbols with the program &'PMM+,! and form T!BTA& M9O:A$!P:'C!.

Default values


7/13

@ere you can maintain default value# for example the dispatch time and the transmission medium. In case a communication

strategy shall be used this has to be assigned here.

Mail title and texts

In case you use message type with medium D 0external send1 here you define the mail title. &ee 2I I page 3Purchase order

as an e"mail using Internet mail 0external mail113.

Processing routines

In the 6Processing routines7 the processing programs form routines and forms can be assigned to the message type.&ee 2I I page 3Print processing programs3.
http://wiki.scn.sap.com/wiki/x/KoPjEwhttp://wiki.scn.sap.com/wiki/x/KoPjEwhttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/x/mQHrEwhttp://wiki.scn.sap.com/wiki/x/KoPjEwhttp://wiki.scn.sap.com/wiki/x/mQHrEw


8/13

Partner Roles

@ere you assign Partner roles to the message type.

Fined tuned !ontrol

(efines which message type shall be used for which print operation 0new print change print urging let ter expediter1. -or

the message type /!) the print operations < 0new print1 and E 0change print1 should be always maintained. In case

scheduling agreements are used the f lag 6)pdate print"dependent data7 0T


9/13

Access se"uences

2e define the access se%uence under Output Control ; 'ccess se%uences ; (efine access se%uence for purchase order

0for PO the transaction is M*D+ this is a cross"client setting1. One access se%uence is assigned to the message type. The

access se%uence serves as 5ey combination for the creation of condition"*message entries.


10/13

The access se%uence orders the condition tables in a certain se%uence. Tables with the smallest se%uence number will be

loo5ed up first. The flag 6!xclusive7 prevents the system to loo5 up subse%uent tables in case one table was already

matched. This prevents that more than one message will be created.


11/13

EH ED and E, are the condition tables# they contain those fields for which a purchasing document will be chec5ed when

determining the message.In details we can see that fields ! O$4 and :I-/$ are defined for the access se%uence +++

message determination in purchasing

Documents