User Manual

For
SAP EDI 850 OUTBOUND
Implementation
1 Contents
1. Introduction...................................................................................................................................3
2. Step 1 – Create Customer Master Record (XD01)..........................................................................3
3. Step 2 – Create Vendor Master Record (XK01)..............................................................................4
4. Step 3 - Partner Profile Maintenance............................................................................................4
a. Partner Profile (WE20)..............................................................................................................4
b. Outbound Parameters.................................................................................................................5
c. Outbound options......................................................................................................................6
d. Message Control........................................................................................................................7
5. Step 4 - MM Configuration............................................................................................................7
a. Condition Table (M/67).............................................................................................................7
b. Access Sequence (T- Code M/50).............................................................................................8
6. Step 5 - Message Type (T- Code M/34)..........................................................................................8
7. Step 6 - Partner role......................................................................................................................9
8. Step 7 - Maintain Message Determination Schema (OMFT)..........................................................9
a. The document category determines message schema M/36.....................................................10
b. Partner Roles per Message Type..............................................................................................10
c. Update the output determination using NACE/MN04.............................................................11
9. Test Procedure.............................................................................................................................12
1. Introduction
The EDI 850 is a Purchase Order transaction set, used to place an order for goods or services. The EDI
850 generally provides the same information you would find in a paper Purchase Order (PO)
document, including: Item, prices and quantities ordered.

In another way EDI is the electronic exchange of business documents between the computer
systems of business partners, using a standard format over a communication network. EDI is also
called paperless exchange.

A customer who wants to purchase an item creates a purchase order and then faxes or mails it to
the vendor. The vendor receives the purchase order and manually keys in a sales order. The vendor’s
system generates a confirmation date that is sent back to the customer via fax or mail. The vendor
then ships the goods via a carrier. The carrier delivers the products to the customer. When the goods
are shipped, the vendor invoices the customer. The customer makes the payment by check, and the
vendor deposits the check in the bank. Finally, funds are transferred from the customer’s account to
the

The component senders and receiver are called trading partners (Vendor and Customer)

2. Step 1 – Create Customer Master Record (XD01)

Create Customer master similar to vendor (100009870) through XD01 with the below combination
and map in vendor master (100009870)
3. Step 2 – Create Vendor Master Record (XK01)
Create Vendor master and assign Customer (316077) in vendor master.

4. Step 3 - Partner Profile Maintenance

a. Partner Profile (WE20)
Partner profile must be maintained for all the business partners to whom we want to send or receive
the IDocs. The TCODE for maintaining the partner profile is WE20.

Double clicking on the Partner will show the following screen:

Partner profile contains parameters for Inbound and Outbound processing of IDocs. For each
message type we can maintain, inbound/outbound options, message control, post processing
options and contact information within Inbound and outbound parameters .

b. Outbound Parameters

This involves sender/receiver port, Output mode and relation to IDoc type i.e. Basic Type and
extension.

Need to select icon for creating the new Outbound parameters. Refer above screen. To update
Message control, post processing so on select the line item as shown below:

Need to update each field in the detail screen of Outbound Parameters tabs.

c. Outbound options
d.

Message Control

(Header is common)
5. Step 4 - MM Configuration
a. Condition Table (M/67)

Maintain condition table using M/67 for output determination. Condition tables are accessed
through Access Sequence. In access sequence we can specify the requirements. A condition is
accessed only if requirement met.

b. Access Sequence (T- Code M/50)

Access Sequences determine the order in which condition tables are accessed.
6. Step 5 - Message Type (T- Code M/34)
The message type denotes different kinds of message (in Purchasing, mainly communications sent to
vendors, such as purchase orders, order acknowledgments, and expediters). For each document
type we can have different types of messages

Select an output type and click the system shows the properties of the output type. The most
important attribute of an output type is the access sequence.
7. Step 6 - Partner role

8. Step 7 - Maintain Message Determination Schema (OMFT)

A message determination schema contains the permissible message types for each message
application (new printout, reminder, etc.). This allows the system to automatically suggest the
associated messages as defaults in purchasing documents.

Prerequisites: You must first define the message types. Then you must include them in a message
determination schema.

Note: Only one schema and only one message type can be assigned to each purchasing document.
a. The document category determines message schema M/36

b. Fine-Tuned Control: Purchase Order: For each message type we create and must
specify the purpose for which it is to be used. For example, outputting
(printing/transmission) of new documents, outputting of change documents, outputting of
urging messages (expediters).
Activities
  You make the settings for fine-tuned control with regard to the various message types
in Customizing for Purchasing .
 If you wish to use different message types for each type of scheduling agreement
release, you should specify which message type updates the print-relevant data (e.g.
date of last transmission).

c. Partner Roles per Message Type

Select the Z850 and define Partner Roles for Purchase Order as shown below
d. Update the output determination using NACE/MN04

Select EF then select on condition records

Now pop will appear.

Select on Z850
Press Enter.

Change EDI Purchase order (Z850) will appear update as show below.

Press Enter.

Save.