1. Setup SAP application
- Customize the application and create basic data
- Check the functionality of the application
2. Setup the EDI interfaces
- Maintain the control tables and create partner profile
- Test whether the Intermediate documents (Idocs) are successfully generated and posted
3. Setup the EDI subsystems
- Maintain the control tables
- Test whether the EDI subsystems can process and generate Idocs.
- Setup the RFC trigger
To combine EDI with your functional module (MM/SD/FI..) the following steps are a pre-requisite.
The steps I mention here and in most of my blogs are more biased towards MM ( and sometimes WM) as I am an MM consultant. Again if some one is willing to post on other module behalf contact me and I am more than happy to share the blog space.
1. Port declaration:
This step is required to create a gate for the 2 system (Internal and external) systems to communicate.
T.Code: WE21
2. Create a Vendor
Though this step is independent , A vendor should exist so that for the communication to take place.
T.Code: XK01
3. Create a Partner Profile
For a vendor profile creation select LI and for a customer select KU
Enter the partner (vendor) number
Enter the partner type as LI
Once you save, Eter the Outbound parameters
Partner Role as VN
Msg type ORDERS ( for 850 setup)
For the corresponding, enter the Outbound options, Message control
The output mode will let you to select the mode ie, if you want to send them as soon as they are created or if you want to collect ALL the idocs and send them at regular intervals.
If you have selected collect all idocs, you can still over-ride for a paricular idoc via the PO screen and RSEOUT program.
Idoc type is ORDERS 05
In the message control screen,
Select Application type as EF
Msg type NEU ( SAP standard)
Process Code (MEPO)
Create a PO via ME21. Save and again in change mode, click on Messages.
- change the medium to EDI
- Click on further data, change to Req process Send Immediate and Save
On the top you should see that the button is in green state indicating that the IDOC is processed successfully.
Helpful EDI/IDOC T.Codes
- WE02: To view the IDoc
- WE05: To see the IDoc list/structure
- WE60: Documentation of IDoc type or segment type
- WE30: Create/Extend an IDoc
- WE31: Create a new segment
- WE41: View Outbound process code
- WE42: View Inbound process code
- WE14/prg RSEOUT00 : To release an outbound IDoc
- BD20/prg RBDAP00: For inbound processing of Idoc
- WE81: Display Logical message type for Idoc
- WE82:Display o/p types assigned to IDocs.
very informative
ReplyDeleteits an highly informative, thanks for the writer.
ReplyDeleteits an highly informative, thanks for the writer.
ReplyDeleteits nice information, you can add partner profile tcode : WE20.....
ReplyDeleteThanks for share this good information about EDI. IT might be helpful.
ReplyDeleteHello,
ReplyDeleteThanks for the information you gave. I will glad if you can inform me about scheduling agreement. For outbound EDI delfor , should scheduling agreement unic for part number, or can we use one scheduling agreement for each vendor?
Thank you
Good Document
ReplyDeleteHi Thanx for sharing this article with us. This is really helpful and interesting to read.
ReplyDeleteEDI Testing Challenges