I have a scenario, where I have to pick up an EDI file via filepolling and submit it to TN, where I can invoke a service to transform EDI to XML.
Please help me in this scenario, having difficulties.
In the filepolling port configuration you can mention the Processing Service filed wm.tn.doc.xml:routeXML and also set the Content Type:application/EDIstream when ever the file available it will submit to TN and setup a TN processing rule (sender/receiver/document type) with action that invokes your custom service (that does all EDI parsing/mapping to XML structure etc…down stream processing)
Thank you sir…I did not think of that…
I would ask more if necessary…
Try it and let the forum know.
It is working…
but recommeded is to use a custom service, which includes routeflatfile in it…when working on live…
Yes that is the ideal way…And custom service should be using routeXML (for any XML/EDI routing to TN) not routeFlatFile it is only used for flat files routing…
Could you help in one more thing.
I have converted EDI to XML, and want to write that XML doc to a file…
Cannot find a service, and not comfortable with java service.
Please if you could help.
Do you have PSUtilities package installed? If not download it from Advantage site…
There is one “writeToFile” svc available which you can use that.
I want to ask about the different EDI qualifiers, which are there in ISA envelope.
And can I accept Order 850 through file polling to simple services? as it is giving me error of “Found no valid records”.
Thanks and Regards
Here are the few qualifiers used in the X12 and EDIFACT world respectively:
01 X12=Duns, EDIFACT=Duns
04 X12=IATA, EDIFACT=IATA
05 EDIFACT= INSEE
08 X12=UCC Comm ID, EDIFACT= UCC Id
09 X12=X 121 CCITT, EDIFACT = Duns with 4 digit suffix
10 X12=DoD Activity Address
12 X12=Phone, EDIFACT=Telephone Number
14 X12=Duns Plus Suffix, EDIFACT=EAN
15 X12=PAS of Canada Code
16 X12=Duns Number with 4-char suffix
17 X12= ABA routing number
18 X12=AAR Std Distribution Code, EDIFACT=AIAG
19 X12=EDICA Comm Id
22 X12=FICE, EDIFACT=INSEE
23 X12= NCES
25 X12=ACT, Inc. 4-digit Code postsecondary institutions
26 X12=Statistics of Canada list of postsecondary institutions
27 X12=HCFA carrier
28 X12=HCFA Fiscal Intermediary
29 X12=HCFA Medicare provider
30 X12=US Federal Tax Id, EDIFACT=ISO 6523 id
31 X12=IAIABC Jurisdiction id plus 4, EDIFACT=DIN
32 X12=US Federal Employer Id (FEIN)
33 X12=NAIC code, EDIFACT=BIA
Are you getting the error while parsing in convertToValues step? Did you set the correct EDIFFSchema and mapped the edidata (ST level string)?
Yes, I am getting error while parsing through convertToValues
and I have mapped edidata, and given right schema, that is …850
Check the edidata you are passing and make sure it is in correct format (includinig delimiters etc…)
There was a fault in edidata…I corrected it.
Now service is working, but when debugging it with save and restore pipeline, then errors come up as Delimiters not Set…
please help me, attatched is the input file.
In that case you can modify the pipeline delimiters part and parse it…
Sir, I did this thing also, but still saying “Found no valid records”.
I had hard-coded the delimiters from the input file.
I have attatched the input file here, please help me with the delimiters, if I might be wrong.
850.txt (3.04 KB)
Check original EDI file Delimiters with restore pipeline data Delimiters…if you find any difference then update me…
Probably the issue could be with this wierd record/segment delimiter (È) that you are getting it…For testing try replace with ~ or some thing and route it again…See how it goes and let us know…
Try using Hex editor (like ultraedit) and look it in ascii.
As above suggested by RMG repalce your segement delimiter by ~ or line break and in converttovalues specify the same delimiter in segment delimiter.
Thank you RMG and devexpert…
I would try doing with that and then confirm with this update.
good keep us posted…