IDOCFlatToXmlConvertor: | |
Issue1: | |
*Sol: |
|
*Issue2: |
Most of us think we have an issue with the data. Right, I agree. Let's suppose we have a mapping we can suggest formatNum function, but if we don’t have the mapping defined then still the issue persists. Based on the issue we all know that system is expecting value instead of null right.
*Sol: |
Note: If we use the same file for the inbound scenario as mentioned in the blog it works successfully but we don’t receive the file in the same format as same as mentioned in the blog.
For inbound scenario we can expect the control segment only with IDocType & MessageType data of that particular IDoc & for each Data segments there should segmentnumber & Parent Segment number defined. Sample file attached herewith…
Ref: http://help.sap.com/saphelp_me60/helpdata/en/1a/0e3842539911d1898b0000e8322d00/frameset.htm
I hope this will help you to understand more in detail about the file & the issues…
EDI_DC40 ORDERS05 ORDERS
E2EDK01 000001000000
E2EDK03 000002000000 00220120220
E2EDKA1 000003000000 AG I0180 824480123
E2EDK02 000004000000 001TEST04 20111230
E2EDKT1 000005000000 Z006E
E2EDKT2 000006000005 YTN
E2EDP01 000007000000 2 001 1200.0 EA EA 5.65 1 6780.0
E2EDP20 000008000007 1200.0 20120220 001
E2EDPA1 000009000007 WE 66