My Oracle Support Banner

OSM Order State Not Changing To Complete After All Order Component Completes (Doc ID 2762916.1)

Last updated on FEBRUARY 01, 2024

Applies to:

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

Symptoms

In customer environment they are facing intermittent issues for many orders where OSM order state remain in-progress even after all the orchestration order components completes for that order.
Also please note there is no change management functionality (undo, redo etc.) is implemented in the current solution.

Error:

<com.mslv.oms.handler.completeorder.CompleteOrderHandlerEJB> <BEA-000000> <Unable to complete order [xxxxxx]. This is not necessarily an error if uncompleted tasks exist for completed subprocesses. This can happen in some cases when compensation is undo-then-do for a completed sub-process.>


OSM order state not changing to complete after all order component completes

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.