Let me confirm what you are asking. Did you prune the X12 provided type tree to just the 837 and want to simpify further or you are asking how to prune the entire X12 to just the 837? If you are wanting the former, to simplify the 837 after it has been pruned from the other types and versions, I would strongly recommend NOT doing that. EDI is a very fluid conversation with trading partners. You never know when you might need something in the transaction set that you pruned out. There will be a lot of NONE mapping and that is OK.
If you need a primer on pruning out just the 837 for a particular version - then I am sure I or several others can provide basic steps.
Happy mapping!
------------------------------
Lisa Edwards
Software Engineer / Subject Matter Expert
Rainbow Data Systems, Inc
------------------------------
Original Message:
Sent: Wed October 30, 2024 10:47 AM
From: Rajesh Jayathirtha
Subject: XML to EDI - best approach
I have a requirement to transform a XML message to EDI 837. To facilitate the XML message generation, I have exported the 837 schema from the type tree. Is there a way to simplify this schema or a better approach for this transformation?
------------------------------
Rajesh Jayathirtha
------------------------------