Component doesn't start in a scenario where the order flow is changed during a revision.
Last updated on DECEMBER 30, 2014
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
We are facing an issues with a few orders in production, where the OSM COM orders are not progressing, and are getting stuck at Sub Process tasks.
The orchestration plan is Sync Customer->Initiate Billing->PlanNetwork->Construct Site->Provisioning->Fulfill Biling->Fulfill Service Design.
We have observed this issue to occur during revisions, and when there are fallouts on this order in the past. For some reason, the subsequent order component does not progress to the SI Tasks, after the previous order component is completed. We have the right dependency set-up. This is working for other orders in the system .We also notice that, the fallout recovery task was completed by 'oms-internal' during such scenarios.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms