OSM Fails To Process Amendment For Partial Orders.
(Doc ID 1491861.1)
Last updated on JANUARY 12, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.
OSM fails to process amendment, throws NullPointerException.
Step to reproduce:
1. Sample order used for reproducing the defect is available under the folder ColtSalesOrderFulfillment\samples in attached XXX.zip file.
2. Fire the sales order 5-1.xml. I will create three orders in PIP cartridge (COM, LF and Product cartridge). The order will work only if fired from the design studio. If you want to use SOAP UI, please add the SOAP header with proper OSM credentials.
3. Fire the amendment order 5-2.xml.
4. The amendment will not happen.
a. OSM will through the following error in the design studio.
Invalid Order Specification Fault
Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.handler.InternalErrorException: Failed to start order : null caused by:null
b. OSM will also throw NullPointerException in the weblogic log. See attached AdminServer.log for the full exception.
c. Also Domain log is attached.
At step 4, the amendment should happen properly. OSM is not expected to throw NullPointerException in the background.
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