Friday, December 7, 2012Configuration of outbound order (ORDERS) EDI message Output type and Determination Procedure

You can use standard output type NEU. In case you decide not to use NEU for some reason you can copy NEU and create your own output type. Just make sure once you have created your own output type it is added to Message Determination Procedure. In standard system Purchase order uses determination procedure RMBEF1. You can find out the right determination procedure assigned to purchase order in IMG menu path Material Management->Purchasing->Messages->Output Control->Message Determination Schemas->Define Message Schema for Purchase order-> Assign Schema to Purchase Order. In order to use your own output type it should be included in this determination procedure. To look at determination procedure and assigned output type goto transaction NACE, select line EF-Purchase Order and select 'Procedure' button from tool bar. Then select the determination procedure and double click on 'Control'.

Requirement are routines (basically ABAP form) which decides whether output can be generated or not based on certain condition. It sets SY-SUBRC value to 0 if output type can be issued.

Access sequence and Condition record

Access sequence is group of tables which stores the condition(s) on which output type automatically triggers with document. For purchase order to automatically process output type, condition record should exist in one of the Access table defined under Access sequence.. For example you may want raise ORDER message for a particular vendor or for a particular purchase order document type. In standard system Access sequence assigned to NEU condition record is 0001 which is group of 3 access tables.

To define condition record go to transaction MN04 input output type NEU (or your own configured output type) press enter and system will prompt you to select access table. Access table you select depends on your business requirement. Assuming you want to activate ORDERS message per vendor select first access.

Then create condition record specifying your vendor, function as VN, transmission medium as 6 (EDI) and Despatch time as 4 (Immediately) then save.

EDI Partner profile setup

EDI partner profile define various parameters using for transmission of EDI message to partner. Typically partner in case of purchase order is Vendor. Create new partner under node Partner type LI in transaction WE20. Specify vendor number partner and 'recipient of error notifications' which can be user, organisation unit etc. After that press save.

Under 'outbound parameters' table press 'Add' button. This is the place where we will specify EDI message type, Idoc type and outbound process code and link this EDI message with output type NEU. Unless you have developed your own custom functionality SAP standard values are

Process code ME10Basic Idoc type ORDERS05Message type ORDERS

Enter values as per screen shot below. Receiver port will be specific to your landscape you might be able to get that from Basis consultant.

Move on to Message control tab and add line as per screen shot below.

Save and exit transaction.

If you now raise purchase order under purchase organisation and vendor we created condition record in previous step you should see condition type NEU with Medium EDI.

See sap help on Sending a Purchase Order via EDI