Order Amendment: Task Running In Amend_do Exec Mode Is Not Completed Due To Java.sql.SQLException (Doc ID 2995323.1)

Last updated on DECEMBER 30, 2023

Applies to:

Symptoms

During order amendment, a task right before a pivot sub-process is running in amend_do execution mode. When it receives a successful response and tries to complete itself an exception is thrown in the logs with error "java.sql.SQLException: ORA-06530: Reference to uninitialized composite" and the task enters fallout mode.

Note that during the base order fulfillment the flow does not pass through either this task or its successor pivot subprocess, but during the revision order fulfillment the flow reaches the task for the first time, hence it runs in amend_do exec mode. However, when it tries to complete the task in order to reach the pivot subprocess also for the first time the exception referred above is thrown in the logs.

Below a schematic depiction of the base and revision order flow:

Base order: Task A (do) --> Task B (do)
Revision order: Task A (redo) --> Task C (amend_do) --> Pivot SubProcess D (amend_do) --> Task B (amend_do)

The exception is thrown when Task C tries to complete itself.

Cause

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