EDI management for POs

Question

I just am looking for a simple outline (with possible screenshots) regarding managing and following up with vendors that are set up with EDI. All the vendor master data and materials master data is set up, I am just looking for a basic outline for EDI PO processing and managing/overseeing the IDOC messages (both inbound and outbound) and the possible responses to vendor's IDOC messages.
Thanks.

Answer 1

Hi,
Managing/overseeing IDOC Messages:
Transactions : WE02 or WE05 (Display IDOC)
EDI PO Processing:
Define the output type “NEU” (new) or your own output type for XXX in purchasing master data and assign the Message Control dispatch time “4” (immediately with application update) and the transmission medium “EDI”. Choose the output mode “Transfer IDoc immediately” and “Start subsystem immediately” for XXX in the partner profiles of the IDoc interface and assign the logical message ORDERS to the combination “Application: Purchasing orders”, “Output type: NEU” (new). IDoc type ORDERS01 is assigned to this logical message.
Define Partner Profiles for your Partner. Maintain Application and Output Type  to an IDOC Type in Partner Profile under additional outbound parameters.
1. Message determination: Call the master data from the application and create the message as a message- or condition record, that is to say, you define the conditions under which the message is found and proposed, as well as the message properties. For example, you can enter the purchasing organization and the business partner as the conditions and the output medium (in this case 6 for EDI), dispatch time and language in which the message is to be sent as the output properties.
2. Message processing through IDoc dispatch: The messages are sent by the Message Control module as defined in the condition record, especially with regard to the selected dispatch time. You must also define a dispatch time (“output mode”) in the partner profiles of the IDoc interface: standard combinations of the two times are shown in the table below. The Message Control parameters from the partner profiles must also match the corresponding fields in the output type. These parameters include:
− Application
− Partner
− Partner function
− Output type
The central selection program of the Message Control module, RSNAST00, locates and triggers the form routine EDI_PROCESSING in the program RSNASTED in table TNAPR for the selected output type. EDI_PROCESSING reads the partner profiles and uses the process code to determine the function module which is to generate the IDoc. The process code also determines the type of further processing, for example whether the IDocs are to be processed by the ALE service.
The function modules for generating the IDocs are usually called IDOC_OUTPUT_<MT>, where <MT> represents the relevant message type. Depending on the output mode, the generated IDocs are either collected or forwarded for immediate dispatch. If the IDocs are collected, the report RSEOUT00 must be scheduled in order to forward the IDocs for dispatch.
Regards,
Naveen.