11-21-2011 7:10 PM
Hi all,
I am doing a EDI 850 to ORDERS03 IDOC mapping. I imported the structure of ORDERS03 IDOC from SAP into our third party mapping translator. Its has the fields
E2EDK01005 instead of E1EDK01
E2EDK14 instead of E1EDK14
E2EDK03 instaed of E1EDK03. I exceuted the mapping and i see the IDOC getting created in SAP with E1EDK01 and so on....
I went through the forums and came to know that 1 means outbound, 2 means inbound and the E2EDK01...are the definitions are as per the 45B release...
But i am still not clear why there happens to be a difference in the IDOC segment name that has been imported into the translatorVS the IDOC that is getting created in SAP. Should i assume that E2EDK01005 is the equivalent of E1EDK01 etc....
can some one help me undertsnad this segment name mismatch??
C Nathan
11-21-2011 7:34 PM
E1EDK01 is the segment type and E2EDK01005 is the segment defintion that contains list of fields. If you have access to SAP, go to WE31 and see the details.
Thanks,
SKJ
11-21-2011 8:10 PM
Thanks SKJ.
So my understanding is the segment definition is release specific and contains new field every time there is a release.
so in my case E2EDK01005 has an additional field than compared to previous release E2EDK01004 and E1EDK01 simply defines the structure of E2EDK01005. in other words E1EDK01 is comparable to E2EDK01005??( for mapping purposes)
11-21-2011 8:19 PM
Hi,
When creating IDocs in the R/3 system using transaction WE30, three structures are created and numbered automatically for each IDoc segment. For example: Delivery header has E1TPDLH, E2TPDLH and E3TPDLH. E1 TPDLH is release-independent, E2TPDLH is release-dependent and E3 TPDLH is used for documentation. When segment names are transferred, you must specify the E2 segment names in order to be working independently of SAP release. That's the reason you see it differently.
Reference link http://help.sap.com/saphelp_40b/helpdata/en/1a/0e381b539911d1898b0000e8322d00/content.htm
Cheers,
Prasanna
11-29-2011 4:25 PM