Scribd
Upload
406 views

PO Output Determination

Messages are an important means of communication with vendors in purchasing. Messages can be transmitted electronically or through regular mail. There are different types of messages in SAP like purchase orders, order acknowledgments, and reminders identified by a 4-character alphanumeric code. Configuration involves defining message types, access sequences, condition tables, and assigning message determination schemas to applications to determine which message types are used for activities like creating a new document or delivery schedule. Condition records are then created using the transaction code MN04 to associate specific conditions with messages.

Uploaded by

gh
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
406 views

PO Output Determination

Messages are an important means of communication with vendors in purchasing. Messages can be transmitted electronically or through regular mail. There are different types of messages in SAP like purchase orders, order acknowledgments, and reminders identified by a 4-character alphanumeric code. Configuration involves defining message types, access sequences, condition tables, and assigning message determination schemas to applications to determine which message types are used for activities like creating a new document or delivery schedule. Condition records are then created using the transaction code MN04 to associate specific conditions with messages.

Uploaded by

gh
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP MM

PO Output Determination
Messages:

Messages are an an important means of communication with vendors in Purchasing.

Messages can be transmitted both by the regular mail (postal service) and electronically

Message Type:

The message type denotes different kinds of message in the SAP System (for example, communications
sent to vendors, such as purchase orders, order acknowledgments, reminders, expediters etc.).

Alphanumeric key of up to 4 characters, uniquely identifying a message type

Introduction

The 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 E-mail.The same
program and form are used for the output of several documents and
processes.The documents that can be output are:

 Request for quotation


 Purchase Order
 Contract
 Scheduling Agreement Delivery Schedule

The processes that require the output of a document are:

 Creating a new document


 Changing an existing document
 Creating a new delivery schedule for a scheduling agreement
 Urging/reminding a delivery

Messages can be created and sent for Request for Quotations


(RFQ), Purchase Orders (PO), scheduling agreements, delivery
schedules and contracts.To transmit a message you can use
different media like printer, fax, EDI, E-Mail or SAPoffice. To set up

Caterpillar: Confidential Green


the message determination of purchasing documents you have to
assign a message schema to a purchasing document

Condition/Message Type contains Access


Sequence
Access Sequence contains different Condition
Tables
Condition Table contains different combinations
like Purchase Org/Doc type/Vendor etc.

Configuration Steps:
1. Define Message Types
 It is possible to maintain the message type and
define what print operations should be used for the
message type.
 Make sure that the flags for ‘Access to conditions’
and ‘Multiple issuing’ are set. The flag for ‘Multiple
issuing’ allows sending messages multiple times to
the same partner (this is relevant for urgings and
reminders).

Caterpillar: Confidential Green


 To create change messages properly, the program
FM06AEND and the form CHANGE_FLAG must be
maintained
 Replacement of Text symbols data will be useful to
send the mail with specific Purchase Order data
2. Fined-tuned Control:
 Defines which message type shall be used for which
print operation (new print, change print, urging letter,
expediter). For the message type NEU the print
operations 1 (new print) and 2 (change print) should be
always maintained
 In case scheduling agreements are used, the flag
‘Update print-dependent data’ (T161M-DRUAB) should
be selected.

3. Define Access Sequence:


 One access sequence is assigned to the message
type. The access sequence serves as key
combination for the creation of condition-/message
entries.

4. Message Determination Schemas:


 We assign required condition types to the Schema.
5. 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
RMBEF1 is assigned to application EF i.e. PO. 
 To make sure that the message determination
works properly, the flags ‘N’ for message
determination (T161N-NFIND) and ‘P’ for partner

Caterpillar: Confidential Green


determination (T161N-NEUPR) should be set. The
flag “Rel. mess.” (T161N-OBJLG) is only relevant
for scheduling agreement releases.

6. Create Condition Records:


 Transaction Code to create Condition Records for
PO is MN04

PO to vendor as Mail:
1. Proper communication strategy has to be maintained under
below configuration path
SPRO-IMG- SAP NetWeaver- Application Server-- Basis
Services- Message Control- Determine Communication
Strategy
2. SCOT settings for INT has to be maintained
3. Proper Program and Form routine have to be assigned to the
medium External Send for the Condition type
4. Vendor should have valid Mail address
5. Output medium 5 has to be set for the condition type in
Condition Records

Caterpillar: Confidential Green

You might also like