I am new to webMethods and am trying to remove trailing zeroes from an 810 EDI document.
This is how the data looks coming in: 000000000853
What’s showing up in my map is 85300, I don’t know where the two extra zeroes are coming from and want to remove them, I am running webMethods Version 6.0.1
If possible can you post your 810 edi data.And if we dont know about mapping details that you are handling its hard to trace.I believe there might be some thing wrong in the mapping itself.
Here is what I’m sending in using from an AS400 flat file using a JDBC adapter:
Here is the data from my map:
ST8101
BIG2004052043535020040512689435
REFIA4706850
N1BY**930545
ITD01312004061930200406203185300
DTM1120040616
IT1288EA1CB213089567UP031600065750
PIDF
PO412
IT1**264EA2**CB216085710UP000006124112
PIDF
PO412
TDS7680000
CADMMKETMARKET TRANSPORBM0002150651
ISS552EA845
ISS46CA845
SE17*1
Not sure if this is needed, but here is the raw data I’m passing in:
0120040520435350 20040512689435 200406190030200406200031000000000853 This is the problem field
021% 30 NET 31 DAYS 20040416
03000000000288EA0000000001.20000213089567031600065750
050000012
03000000000264EA0000000001.60002160857100000006124112
050000012
07000000076800M MKETMARKET TRANSPOR BM0002150651
09000000000552EA0000000845
09000000000046CA0000000845
You need to remove the formatString from the EDI Schema.
The Schema is normally located in the wmEDIForTN package under the EDIFFSchema folder.
Determine which field is being referenced from the Dictionary in the Schema ie.213.
Locate the field in the Dictionary under Field Definitions and remove the formatstring for that field.
And also removing option is not recommended since when you move code to QA or Prod environments you have to do this procedure again or if you load any EDI fixes on the WmEDIForTN package chances are there to overwritten this change.
So contact wm support and get a fix for this problem and also they can suggest some flexible option.
I did this for a client and they didn’t like it either. So they contacted Tech support!
Guess what? They suggested the same solution but i’d be curious to see if there’s a new solution.