Purge Script Deleting In-progress Orders When Condition Set As v_not_running_orders
(Doc ID 2614468.1)
Last updated on NOVEMBER 28, 2019
Applies to:Oracle Communications Order and Service Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Customer ran the following purge order command:
a_online => false,
a_delete_before => trunc(sysdate) - 30,
a_drop_empty_ptns => true,
a_purge_xchg_prg_tables => true,
a_stop_date=> sysdate + (1/24) + (30/60/24),
and noticed that the purge script deleted in_progress orders as well. Customer states that as per Oracle documentation v_not_running_orders do not include v_in_progress_orders. But in the purge package v_not_running_orders includes v_in_progress_orders (128) as well.
v_not_running_orders constant integer := 252;--128+64+32+16+8+4, 11111100
v_not_running_orders = v_failed_orders + v_wait_for_revision_orders + v_cancelled_orders + v_suspended_orders + v_not_started_orders
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