Order Goes To Amending State On Revision

(Doc ID 2036640.1)

Last updated on JULY 21, 2017

Applies to:

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


If the Orchestration Plan of a base order does not contain any Data Change Dependencies and the Orchestration Plan of the revision order adds new Data Change Dependencies, then OSM fails to process the revision order.

This was identified in OSM and also OSM build 594.

Error message :
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
<Jul 8, 2015 6:43:08 PM EDT> <Error> <oms> <BEA-000000> <amendorder.AmendOrderMDB: Failed to process amendment for order ID [592] amendment order ID [593]
  at oracle.communications.ordermanagement.orchestration.execution.OrchestrationPlan.findDataChangeDependency(OrchestrationPlan.java:821)
  at oracle.communications.ordermanagement.orchestration.execution.impl.OrchestrationManagerImpl.convertDataChangedDependencies(OrchestrationManagerImpl.java:1129)
  at oracle.communications.ordermanagement.orchestration.execution.impl.OrchestrationManagerImpl.convertDependencies(OrchestrationManagerImpl.java:961)
  at oracle.communications.ordermanagement.orchestration.execution.impl.OrchestrationManagerImpl.convertOrchestrationPlan(OrchestrationManagerImpl.java:785)
  at oracle.communications.ordermanagement.orchestration.execution.impl.OrchestrationManagerImpl.importOrchestrationPlan(OrchestrationManagerImpl.java:536)
  Truncated. see log file for complete stacktrace



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