OFRDOCUMENT.BATCHNAME Column is not Updated when a Document is Routed to an Exception State to Create New Batch (Doc ID 1668569.1)

Last updated on SEPTEMBER 29, 2022

Applies to:

Symptoms

If using the 1006d project, the reporting feature does not update the OFRDOCUMENT table's BATCHNAME with the new batch name, if configured to split exception documents into new batches. The functionality to split into new batches is documented in the following note:

<Document 1238044.1> - Can Verifier be Configured to Create a New Batch for Every Document Added to an Exception State?

Steps to duplicate:

1. Process a batch containing multiple documents (e.g. batch 00000142).
2. Query the OFRDOCUMENT table.  There is a record for each document imported, and the BATCHNAME column is 00000142 for each document.
3. Within Verifier, set an exception state for at least 1 of the documents and release the batch. The documents are split into new batches if configured as documented in <Document 1238044.1>.
4. Query the OFRDOCUMENT table. The BATCHNAME for all the records remain as 00000142 when some of the documents were split into new batches.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.