Orchestration Order Component Dependency Not Getting Resolved In Revision Order (Doc ID 2166621.1)

Last updated on AUGUST 02, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : OSM 7.3.0.0.0 version, Orchestration Plan Generation

ACTUAL BEHAVIOR
---------------
OSM:Orchestration Order Component dependency not getting resolved in Revision Order

Base Order consists of one Bundle{Voice Bundle}. Base Order is in Progress and Design Service Function process is getting executed. OSM receives a revision Order. Revision Order contains 2 bundles. 1 Bundle{Voice} is same as base Order and a new bundle{Access}.

The orchestration plan in Revised Order such that there is dependency exist between Design Service Component for Access and Design Service Component of Voice.

Revised Order process access Design Service Component in amending mode{as expected} and voice Design Service Component and comes in In Progress state.

But the next function for access Bundle{Plan Delivery function} is not executed and the bundle execution is stuck after Design Service Component. The voice Bundle execution works fine.

The Access Bundle should also not get stuck. This is only happening in revision order.

EXPECTED BEHAVIOR
-----------------------
The Access Bundle should also not get stuck. This is only happening in revision order.


Cause

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