ERExportVerifyBkg, TPExportVerifyBkg, CRExportVerifyBkg

Background processes that post the export status of an exported document and routes that accordingly to other Infor Expense Management workflow activities. These background processes monitor the contents of the table alex_document_export_status for the work items in their queues. When the status data is received from an external system, the background processes process the data based on the posted status:

• Completed status: Documents are routed to the next activity in workflow (usually archive or completed queue) and the corresponding status is posted in the staging header table for the document. If there is any external data to post to the document, it is done at this time (For example: expense report payment data is posted to the expense report document).
• Error status: Documents are routed to the Exception Handling activity for possible correction or rejection. Appropriate status is posted to the staging header table. Notes are added to the document header (top BOb) for each error status received for a header or line item. Sample notes appear in the client screen.

The notes are formatted with a heading line Document Export error reported followed by the error code and error message received from the external system. For error reports on line items the note continues with the line bobid, the expense description, item date, amount, and charge code.