Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Steps of EDI is used to transfer IDOC from R3 system to non sap system

Former Member
0 Kudos

Hi Experts,

Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?

Full points will be assigned.

Thanks in advance!

Sapna

2 REPLIES 2

Former Member
0 Kudos

Hello,

The EDI Configuration required to be done for Transfering IDoc to non SAP System is.

1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).

2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.

3. After that, assign the IDoc Type to Message Type in WE82.

4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.

5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).

6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.

7. Maintain Partner Profiles for the Outbound Message Processing in WE20.

8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.

i. In Message Control Configuration, we'll maintain

a. Condition Tables

b. Access Sequences

c. Output Types

ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.

iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.

Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.

For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.

However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.

Hope the above procedure was clear.

Thanks and Regards,

Venkat Phani Prasad Konduri

uwe_schieferstein
Active Contributor
0 Kudos

Hello Sapna

Have a look at the excellent overview document [Thoughts on EDI in an SAP XI Environment|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a].

Example: If you want to send an invoice as EDI message to a customer you have to define the corresponding output (6 = EDI) for the invoice which will generate an INVOIC.INVOIC02 IDoc that is sent to an external system (e.g. SAP-XI).

Usually you need to convert the IDoc into an EDI message standard that is defined by the customer (e.g. EDIFACT, ANSI.X12, EANCOM, TRADACOM, etc.).

On SAP-XI you would need to define an XSLT mapping to transform the IDoc-XML into an EDI-XML. Next the EDI-XML has to be converted into a flat EDI message for which you need an EDI converter.

The EDI message is then sent to the customer, either via VANs, via OFTP or via AS2 (secure internet connection).

Regards

Uwe