DATAFIX: Order Header Remains in Booked Status Where as All Lines Are In A Closed And/Or Cancelled Status after End of Month
(Doc ID 1517127.1)
Last updated on MAY 18, 2023
Applies to:Oracle Order Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
After all order lines are closed and/or cancelled, the order header is stuck in a booked status and is not progressing to closure after end of month. The header level workflow process 'Close-Order' has a wait function with a value, which comes seeded with a constant value which sets it to defer closing until the last day of the month. (Refer to Doc ID 133837.1). The header workflow activity is in the close wait for line workflow activity as follows:
Order Flow - Generic Close - Order Active CPGI_R_STANDARD_HEADER CLOSE_HEADER_PROCESS
Close - Order Wait Null Complete CLOSE_HEADER_PROCESS WAIT
Close - Order Close - Wait For Line Notified CLOSE_HEADER_PROCESS CLOSE_WAIT_FOR_L
Expect that the order header would progress to closure since all lines are already closed or cancelled.
Data corruption issue cannot be reproduced at will.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document