Subject:X12 to XML (837) Author:Dan Cooper Date:08 May 2006 10:10 PM
I am a new user of the trial version and am exploring the features of Stylus. I am trying to convert an X12 to XML via EDI 837 adaptor. The 837 Schema looks good for my use with a few custom modification to fit our databases. However I seem to be missing a step. How do I apply the schema to a X12 file?
Subject:X12 to XML (837) Author:Dan Cooper Date:09 May 2006 04:34 PM
Ivan, the first item I am trying to do is create an XML file from an X12 file using your 837 EDI convertor. I see the XSD created by Stylus but not the resultant XML. Then I would like to convert the XML to our in house format. How is this accomplished. XLST or modifing the 837 convertor to a customer convertor?
Subject:X12 to XML (837) Author:Tony Lavinio Date:09 May 2006 04:54 PM
>Ivan, the first item I am trying to do is create an XML file from an
>X12 file using your 837 EDI convertor. I see the XSD created by
>Stylus but not the resultant XML.
Try File|Open, choose your EDI file, check the box that says 'open with
adapter', and then press Open. On the next dialog, choose EDI adapter
and press OK, and you will have the EDI as XML.
>Then I would like to convert the XML to our in house format. How
>is this accomplished. XLST or modifing the 837 convertor to
>a customer convertor?
Take that same URL that was just built (it will look like adapter:...)
and use it as the input to XSLT. Or, build the schema that corresponds
to the version of X12 you are using via the File|Document Wizards|X12
to XSD Wizard, and use that as the source for the XSLT mapper.
Subject:X12 to XML (837) Author:Dan Cooper Date:10 May 2006 03:24 PM
I have created an XML document labeled 837XML from an X12 document based on the EDI 837 convertor. The result is as expected. Now I need to convert to our in-house format which is similiar to the standard the XML document created above (837XML). I have input the 837XML document as the source input to the XSLT mapper and a modified version of the 837XML XSD as the target document. Is there a way to map all common fields automatically (i.e., /+) rather than one at a time. I assume this will output an XML document in our in-house format. If so my thought is I can use the modified XSD directly rahter than the 837 convertor. Is this correct? If so, how.
Thanks
Subject:X12 to XML (837) Author:Tony Lavinio Date:11 May 2006 12:58 AM
>I have created an XML document
>labeled 837XML from an X12
>document based on the EDI 837
>convertor. The result is as
>expected. Now I need to
>convert to our in-house format
>which is similiar to the
>standard the XML document
>created above (837XML). I
>have input the 837XML document
>as the source input to the
>XSLT mapper and a modified
>version of the 837XML XSD as
>the target document. Is there
>a way to map all common fields
>automatically (i.e., /+)
>rather than one at a time.
At this time, there is no automap feature.
>I
>assume this will output an XML
>document in our in-house
>format. If so my thought is I
>can use the modified XSD
>directly rahter than the 837
>convertor. Is this correct?
>If so, how.
>Thanks
Well, the adapter is always going to generate the XML in the format
of the XSD that we generate - that's why we give you the ability to
generate those XSDs for specific 'flavors' of EDI.
Let's give these things names: the original XSD that comes out of the
Stylus Studio X12 to XSD Wizard will be Tony.XSD, and the one you
modified to represent your ultimate XML will be Dan.XSD.
I would use Tony.XSD as the 'source' for the mapper, and Dan.XSD as
the target for the mapper. The 837XML document that is the output of
the adapter will always conform to the Tony.XSD.
That way, whatever EDI comes in will be mapped properly to your
specific XML needs.
And, doing the map backwards will let you translate your XML based on
Dan.XSD to EDI, if you need to go the other way.
Subject:X12 to XML (837) Author:Tony Lavinio Date:11 May 2006 12:59 AM
But we should really continue this discussion under the Stylus Studio
Technical Forum, since this is the Website Feedback forum, and this isn't
website feedback. (And I'm the one who should know better :).)