Revisions - Base Order Values Retained When The Revision Comes Down As Blank (Doc ID 2148195.1)

Last updated on JUNE 20, 2016

Applies to:

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

Goal

To describe OSM behavior when a base order contains a significant data element that is initially blank,  then a value is provide during processing and then the order is revised with another blank value.

 

1. Create an Order with a significant data element that is not set. (eg DueDate)

2. When the function is in-progress a value is added to the data element (eg. DueDate=26-07-2016).  All tasks are set to "redo" mode 

3. A revision order is received where the DueDate value is again not set or blank.

4. The expected behavior is that upon revision OSM would unset the value but in fact OSM is setting the DueDate to 26-07-2016

 


 

Solution

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