Last updated on APRIL 01, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
After submitting a future dated order on OSM 126.96.36.199.7, orders are in In progress state and we have upgraded from OSM 188.8.131.52.7 to OSM 184.108.40.206.0.
After the upgrade to OSM 220.127.116.11.0, Orders are stuck at CommunicationsProvisioningOrderFulfillmentPIPProcess with task name as ServiceProvisioningFunction_ServiceProvisioningSubProcess
The very same order completes end to end when processed on OSM 18.104.22.168.7.
There are many in progress orders in production environment. Upgrade activity will result in many of the in progress orders stuck at this subprocess after the upgrade
Expected OOTB behaviour:
Order should complete end to end on the request delivery date
Order is stuck at subprocess ServiceProvisioningFunction_ServiceProvisioningSubProcess
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms