Problems with Inbound Mapping
There are two main types of failure at this stage:
- Mapping Aborted - in this case Mapping cannot continue as the
result of errors. The Transmission object goes to 'Failed' state and
will be visible in the All-Alerts screen on the FTM OAC. A Mapping
Aborted event should be available on the transmission details and
will contain full details of the broker exception. Errors that might
occur at this stage include :
- Parser Errors
- Validation Errors
- Mapping Errors (caused by errors in application code)
- Database Errors
- Mapping Failed - in this case mapping has been stopped and the failure state is logically set by the mapper for business reasons, for example, missing data required by customer use-case. The Transaction will be set to the 'Failed' state and will be visible in the All-Alerts screen on the FTM OAC. As this is a 'controlled' error the relevant data will be set in the error records associated with the failed transaction. The message will be configured to roll back to a Queue and will end up either at the top of the Input Queue or on the 'Failed' Queue.