Using Boomi EDI activities, can I able to generate EDI document from a Non-EDI data file (XML/Json) ?
Yes. I know that I have posted about my adventures about using a BN106 (fixed-length file) into an EDI 834 file, and there are others that have posted too.
Can you share the link ?
My requirement is to connect a database (or webservice) extract raw data into XML file.
Map that XML file to an EDI profile (Ex: 861) and send it to partner. But, my doubt is does Boomi EDI profile take care of itself to populate HL and NI (loops) by itself (especially line counts etc) or should we need to use groovy or XSLT to generate? Thank you.
I would recommend that you check out the FREE EDI content on the Train.boomi.com website.
Basically, you use the connection shape to read the xml file, and then the map shape to translate it from xml to edi.
You would recreate the xml profile as needed.
You would import the EDI profile (I never used a 861) and then modify it if needed. (say like your vendor needs some modifications).
In the mapping shape is where you map the XML elements to the EDI elements. The EDI looks just like an xml, in that it can be nested/looped.
Ok, I have followed below approach to meet my requirement and its working fine.
For EDI Outbound, I extracted data from my source system (xml format), created XSL Transformation to dynamically compose the required "dependent" elements (such as HL counters, Loops, Dates and other EDI dependent data, but note that "key/transaction specific" data is extracted from my source system) and kept that XSLT in my Atoms local directory. Created a groovy script (and called in my process component) to apply the XSLT file on extracted source data (which is in XML format). Finally mapped to EDI Profile.
That is awesome. Your methods are advanced. (My few dealings with XSLT have been painful)
Retrieving data ...