algorithm edi to edixml

[Former Member]

Hi everybody,

I am trying to convert a flat EDI to EDIXML via JAVA.

JAVA is not the problem.

The problem is, that in the flat EDI several segments belong to different hierarchical segment.

Sample: The flat EDI has lots of DTM Segments.

How do I know to which parent segment the DTM segment belongs?

Any useful links?

Regards Mario

[Former Member · Accepted solution]

Hi,

Basically if you have the structure, it would definitely tell how the structure is formed. Like each segment can have multiple child node and they can occur multiple times within that segment. Also there can be another segment which many use the same child node name mentioned above and again it have multiple occurances.

So it all depends on which segment you use for mapping and what are the child nodes within that loop that has multiple occurance has to be noted.

For example, there can be an N1 segment in the structure which can have the child node for N3 and N4. here whenever an N1 segment is present, it can either have N3 and N4 segments. So depending on the N1 segment, N3 and N4 may or may not appear as they are optional.

Refer this link which can provide you an idea of the segments.. like mandatory, optional and relational kind of stuff along with few more details.

http://www.gxs.com/pdfs/Tutorial/Tutor_ANSI.SO_GXS.pdf

http://eidx.comptia.org/education/eidx-x12mapping.pdf

Hope this helps.

Regards,

Nithiyanandam

Reward points...

[Former Member]

Thanks to all,

I wrote the EDI Parser in JAVA. The Parser creates a EDIXML from a flat EDI.

Regards Mario

[Former Member]

Hi,

I dont know whether to go with java mapping for EDI to XML conversion as the EDi strucutre is very complex it will be very difficult to go with java mapping.

There are ways by which u can do the conversion.

1) use third party seeburger adapters.

2) Use stylus studio

3) Conversion agent.

Just refer the below link for the same:

EDI Adapter by SeeBurger

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d13916...

B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf7...

Integrating XI with SeeBurger

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e...

/people/ricardoandres.maienza/blog/2007/04/06/edifact-to-xml--stylus-studio-solution

http://www.stylusstudio.com/edi/EDIFACT_translate.html

The steps to convert EDI to XML / XSD can be found at the following link:

http://www.stylusstudio.com/edifact_to_xml.html

Stylus studio download link: http://www.stylusstudio.com/xml_download.html

Or

Using the Conversion agent

/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield

/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch

/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi

/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield

For detail strucutre refer the below link to get more understandiing of the structures.

http://www.edifactory.de/index.php?p=standards/standards

Thnx

Chirag

[Former Member]

Hi friends,

many thanks for the links you posted. But there is still one question open.

Asuming we have the following EDI

...

STS+xxxxxx // =Status

DTM+yyyyyy

DTM+zzzzzz

.....

Lets also asume we have DTM-Segments on different hierarchical levels.

- DTM in connections with the STS (=status); e.g. Date of the status Segment

- and DTM that stand alone; e.g. delivery date; order date

So: How has a parser to identifiy if the upper DTM belong to STS or not?

You will now argue, that you will see this on the qualifiers of the DTMs.

But, if you have a XSD that describes the EDI structure, the enumerations for DTM are not segment-depending! So it is NOT possible to determine if a DTM qith a specific qualifier belongs to STS or not.

The only thing I believe is, that the UNECE designs the structures that the DTMs are unique.

Means: A EDI-message like above will never exist?

So DTMs that could stand alone are placed after the header an DTM that are connected to other segments occur after the segment.

Lets asume we have two DTM and one belongs to QTY, than the EDI is designed to look like

...

DTM+aaaaaaa // belongs not to STS

STS+xxxxxx // =Status

DTM+zzzzzz // belongs to STS

.....

What do you think? Are there any other algorithm?

Thanks a lot

Regards Mario