ProvisioningSequenceNumber Does Not Work The Same Way For Immediate WOs
(Doc ID 1279544.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Communications ASAP - Version 5.2.4 and later
Information in this document applies to any platform.
Running tests on an ASAP 5.2.4 system and observed the following:
1. When the WO is a FUTURE WO (i.e. requestedCompletionDate is a future date) the CSDLs are executed based on the provisioningSequenceNumber.
2. When the WO is an IMMEDIATE WO (i.e. requestedCompletionDate is a prior date), the CSDLs are executed in the sequence received by SARM.
The SARM behaviour is different in the above two scenarios because FUTURE WOs are fetched from the DB, and the Stored Procedure retrieves the CSDL data using ORDER BY provisioning sequence number, effectively re-ordering the list of CSDLs loaded into memory.
Is the behavior of the immediate WO correct?
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