Future Dated Order in Waiting State is Not Getting Amended During Revision
(Doc ID 2329058.1)
Last updated on MAY 10, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.3.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
OSM 7.3.1.0.6
Revision Order does not amend a future dated Base Order and raised exception "Unable to enrich orchestration plan".
Expected Outcome: The above revision order should amend the existing base order and base order should start immediately since its amended with current date.
Steps to replicate:
1. Create Base Order with a future date. Order has not progressed in OSM and Order is in Waiting state.
2. Revise the same order with Current date and add an additional bundle to the order.
3. Revision Order is created and completed. There is a change in orchestration plan.
4. Base Order still shows as "Waiting" and it is not amended.
5. Once the future date is reached, base order progresses and remains stuck at SyncCustomerSIEntryPoint in "Received " state.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |