Order Creation Failure In OSM Due To "invalid Date Value : Wrong Type"
Last updated on SEPTEMBER 26, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 to 7.2.4 [Release 7.2]
Information in this document applies to any platform.
On : 184.108.40.206.2 version, AIA Cartridge
Order creation failure in OSM due to "invalid date value : wrong type"
Few orders are failing during creation in OSM throwing the following error; "
However, upon re-firing the same order XML through SOAP-UI, order is successfully created and is completed without any manual intervention.
There is no alterations/modifications made to the order request XML during re-firing it through SOAP-UI.
BEA-000000 : "Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: encountered error starting orchestration caused by:Invalid date value: wrong type: "
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