Recognize -99999 as ZERO Feature
(the feature and the XML map bug)
Embedded Files
Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
Symptoms:
The "Recognize -99999 as zero" feature was implemented to save you the following steps when considering to post a "0" literal on the document when the UFD field is equal to zeros, instead of a *null by default:
Diagnosis: Considering Posting "0" instead of *null when mapping
Go to the UFD field and [Define Conditions] against =0.
During mapping time, map the <Zero> keyword whenever the UFD file=0 ELSE map the UFD field.
It might look it is simple and straight forward, BUT if you have more than 10 of these and all-around the map; you will appreciate this feature (it comes with a cost - you will need to ask your ERP to put this value when posting to the EDI work files). And all you need to do is check that box in Format Properties.
BUT sadly :(, it is NOT controllable in the XML map.
It is set ON on the onset of the map creation, but in the shuffle of backing it up, recompiling and renaming; the mapper turns it OFF. The only way to fix it is by creating a new format - thanks to the DTD/XSD import.
Do you have a CHALLENGE? Let us know HERE.
Page updated
Google Sites
Report abuse