IDoc support would be aweasome

[ghost]

IDoc (SAP format) is based on EDI I think.

It would be great to have the possibility to parse IDoc's in a handy way.

Kind regards

[cleftheris]

Hi @XdX-Software

I would very much like to support a SAP format in EDI.Net, but I am not familiar with SAP R/3 and the IDoc spec. From what I can find on the net, it seems to be an EDI format with segments and all but I cannot seem to find any specs for the grammar (Control characters & structural segment names etc.).

If you could provide with the specs/or info and you are willing to help test this I definitely would consider it.

Thanks for your interest!

[ghost]

This is the best I could find. http://help.sap.com/saphelp_nw70/helpdata/en/dc/6b824843d711d1893e0000e8323c4f/content.htm https://blogs.sap.com/2012/12/31/idoc-basics-for-functional-consultants/ http://www.guru99.com/all-about-idocdefinition-architecture-implementation.html http://www.tcodesearch.com/tcodes/search?q=idoc

On German (Google Translate) http://edi-wissen.de/edi/datenformate-nachritenstandards/idoc/

I hope that helps you. Sure, I'm willing to help testing it.

[cleftheris]

@XdX-Software I took a first look at the resources you provided and have come up to the conclusion that there is a way to handle IDocs with EDI.Net. The main issue is that due to the fluidity of the spec the grammar would be constantly changing.

these are the additions/enhancements needed:

1. support of longer segment names (how long I do not know but as of now we support up to 4 digit segment names)
2. support the \t and \n whitespace characters as separator characters of elements and segments respectively. Related to #24
3. The structure elements are not well defined as is the case with other formats. Do something about their absence.

That is for now. I do not have a plan as to when I could start looking more into this. Maybe a task for someone with the time to play around with the idea and the resources and knowledge to test it could help (access to SAP/R3).