How Can Reverse Dependencies Be Configured? (Doc ID 1595032.1)

Last updated on OCTOBER 18, 2016

Applies to:

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

Symptoms

User is receiving the following errors when they are trying to configure reverse dependenices. 

Sample Scenario: 

If Action Code is ADD - Function A --> Function B
If Action Code is DELETE - Function B --> Function A

Fulfillment Mode is DELIVER for both the scenarios with just different Action Codes.

configured the above 2 required dependencies in a Product Spec using Property Correlation Order Item Dependency. The xqueries of those dependencies are such that only one of them will return <osm:dependency/> nodes. The cartridge was built successfully with warnings. And cartridge was deployed successfully. However, on submission of order, OSM threw a circular dependency error. In order to rule out possibility of erroneous xqueries, So technically none of the dependencies will be created in the final orchestration plan.


Caused By: oracle.communications.ordermanagement.orchestration.generation.OrchestrationPlanGeneratorRuntimeException: Circular Dependency detected.
ProductSpecification : Service.Circular.Dependency
FulfillmentMode : DELIVER
FulfillBillingFunction->ProvisionOrderFunction->FulfillBillingFunction
at oracle.communications.ordermanagement.orchestration.generation.w.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.w.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.w.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.w.h(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.w.d(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.w.(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.k.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.af.a(Unknown Source)
at oracle.communications.ordermanagement.xmlmetadata.a.b(Unknown Source)
at oracle.communications.ordermanagement.xmlmetadata.a.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.o.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.generation.o.b(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.cache.jboss.impl.d.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.cache.jboss.impl.b.c(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.impl.j.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.impl.h.b(Unknown Source)
at com.mslv.oms.handler.util.e.a(Unknown Source)
at com.mslv.oms.handler.util.e.a(Unknown Source)
at com.mslv.oms.handler.util.e.a(Unknown Source)
at oracle.communications.ordermanagement.handler.failorder.FailOrderHandler.a(Unknown Source)
at oracle.communications.ordermanagement.handler.failorder.FailOrderHandler.process(Unknown Source)
at com.mslv.oms.handler.a.processRequest(Unknown Source)
at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)

 

 

 

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