Exception Handling During Transaction Data Sync

This feature allows you to identify and handle exceptions raised when data from external system is synced into Buying service through event listeners.

When data is coming in from an external system, while the listener may be able to receive the entity data, it might not be able to process the data due to functional errors. Examples of such functional errors include missing or incorrect values for mandatory attributes and issues with reference entity (like for example, Party account is the reference entity for Product order).

Error information can be be retrieved, with details on the entity, the source system, the reason, related entity errors, along with status. Based on this, the incorrect data can be corrected and sent again for sync into Buying. Once this is successful, the error record status can be set to Resolved. Status of error records can be marked for verification too as required and once, verified, they can be updated to be Resolved.

The business benefit of this feature is that it provides clear information on the specific reasons that failed the data sync from external system so that the data can be corrected and synced back into Buying.

Steps to Enable

You don't need to do anything to enable this feature.

Access Requirements

Use the Business Operations Specialist role privilege to query exceptions and update exception records.