Anatomy of a Translation Error
Incoming Documents
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.
The Challenge: How to locate and fix a translation error?
The Challenge: How to locate and fix a translation error?
The Solution: Locate the Mapping Instruction using the Map Sequence (4) and the Element (3) in the translation format printout (PED754N) this will be the "First" mapping instruction to be reviewed. Review properties of fields and elements and their values and results of the mapping from the first mapping instruction up to the mapping instruction just before next mention of an element (6) in a mapping instruction. When testing values/results; the test can be limited to the confines defined by the Data Sequence (2).
The Solution: Locate the Mapping Instruction using the Map Sequence (4) and the Element (3) in the translation format printout (PED754N) this will be the "First" mapping instruction to be reviewed. Review properties of fields and elements and their values and results of the mapping from the first mapping instruction up to the mapping instruction just before next mention of an element (6) in a mapping instruction. When testing values/results; the test can be limited to the confines defined by the Data Sequence (2).
For this particular example: The "First" mapping instruction to be reviewed can not be the cause of this error. This is an error that occurs when the result field/element is numeric. The first thing, we did was to check the error message field/element value : 0000000000000000003000000000000. By looking at it, you would need at least 13 to fit this value. After checking the properties of all result fields, we found out that the last mapping instruction which involves the work field UP was the culprit.
For this particular example: The "First" mapping instruction to be reviewed can not be the cause of this error. This is an error that occurs when the result field/element is numeric. The first thing, we did was to check the error message field/element value : 0000000000000000003000000000000. By looking at it, you would need at least 13 to fit this value. After checking the properties of all result fields, we found out that the last mapping instruction which involves the work field UP was the culprit.
Page updated
Google Sites
Report abuse