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:
Unable to perform numeric conversion on value TPINTERCHANGE during record format initialization.
Error occurred while processing mailbox ID M0046656, data sequence 2, segment ID BEG, attempted to map the value TPINTERCHANGE from the stack to initialize a record. The value TPINTERCHANGE cannot be converted to a numeric value for the specified mapping. The value being converted must not contain invalid characters. The error is most likely related to envelope mapping or down mapping, and may not be related to the referenced segment.
For information on the Anatomy of a Translation Error: Click HERE
Diagnosis:
Envelop mapping is done via <Keywords>.
Look for mapping instructions with keywords.
Look for the value TPINTERCHANGE in the Mailbox Details.
If you can not find <Keywords> explicitly seen in the map instructions, check the UFD-Header under the ID fields.
Prescription:
The value TPINTERCHANGE is alphanumeric and is being implicitly posted to the N0CUS field which is zoned decimal, hence the "Unable to perform numeric conversion on value TPINTERCHANGE during record format initialization." error.
Based on the length of the interchange ID and the N0CUS field length, the UFD might have been configured incorrectly, the Partner ID Type might have been intended to be "Internal ID".
To fixed this error, an alternate alphanumeric field should be used for the Set ID Field - Partner ID or change the Field Type to alphanumeric (Warning: the actual database definition has to be checked or changed to avoid Move Fail errors.
Do you have a CHALLENGE? Let us know HERE.
Page updated
Google Sites
Report abuse