Note: This background process is deprecated as of Release 6.1. All new implementations must use the new (ERExportVerifyBkg, TPExportVerifyBkg and CRExportVerifyBkg) Verify background processes. The new Verify bkgs are documented in this section.

The DocumentExportVerifyBkg background process implements the Export Verification Activity. This background process monitors the alex_document_export_status table for work items in the verification queue. When the export status is received into this table from the external system, this background process processes the export status.

Document Export Verify Bkg
Class name DocumentExportVerifyBkg

A background process that posts the export status of an exported document and routes that accordingly to other Infor Expense Management workflow activities. This background process monitors the contents of the table alex_document_export_status for the work items in its queue. When status data is received from an external system, this processes the status data basedon 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, this 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.


DocumentExportVerifyBkg is a continuous, on-request start, work queue model background process. This requires an entry into the alco_background_process table and needs to be associated with a user id. An entry in the alwf_activity_permission table associates the bkg user with the document queues (activities) that is processed. This is a sample alco_background_process entry: 600023|DocumentExportVerifyBkg|1|3|60|m|3|123|1000|largesoft.documentExport|2|7001|localhost

The bkg_process_id (600023), server (localhost) and port number (7001) are samples and should be set to an appropriate value for the client installation.

Operations By default, DocumentExportVerifyBkg is defined to be started only on On-Request. But, the DocumentExportVerifyBkg can be configured to start when the application server starts and run continuously until stopped by a command request or an application server shutdown.
Recovery/restart The DocumentExportVerifyBkg can be set up to be auto restart by the background process monitor in case of failure.