Unable To Revise Order By Changing A Line Item When Other Line Item Has Reached PoNR
(Doc ID 2133964.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.
OSM version 126.96.36.199.5 654
O2A version 188.8.131.52.0
A new Order is placed by Siebel to OSM and it contains the following product bundle. Order flows to the point where PONR has been reached for Shipping but not for Activation and the milestone/PONR is updated in Siebel. At this instant the order is revised and RDD(Requested Delivery Date) for Activation Broadband is modified and sent to OSM.
The problem in Provisioning Function RootParentSalesOrderLineId has been inherited as Significant as per OOTB cartridge (OracleComms_OSM_O2A_COM_Base).
So in case of revision as Siebel is sending new value of RootParentSalesOrderLineId to OSM for all the line items (Shipping and Activation), OSM is identifying RootParentSalesOrderLineId as significant element (significant under provisioning function structure).
As this is identified as significant change for line item reached PONR as well, this is resulting in Order getting rejected with the PONR already reached error even when Shipping Item from Siebel came without any data modification.
- Modify OracleComms_OSM_O2A_COM_Base
- Make RootParentSalesOrderLineId under Provision Function as not Significant in Order Template
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