Update the Precision for the Market Message Data Field to Align with Other XML Data Type Fields
(Doc ID 3052451.1)
Last updated on NOVEMBER 06, 2024
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.8.0.0.0 to 2.9.0.1.1 [Release 2.8 to 2.9]Oracle Utilities Framework - Version 4.4.0.3.0 to 4.5.0.1.1 [Release 4.4 to 4.5]
Information in this document applies to any platform.
Symptoms
The field used for storing market message data is an XML data type, which should allow a large amount of data. However, the metadata for the field defines a precision of 2000, which causes validation in the system preventing messages from getting stored if they are more than that.
Steps To Recreate
Define a business object for either the Inbound Market Message or Outbound Market Message maintenance object and include the corresponding Market Message Data table in the definition.
Try to add a record through the UI or via a web service for that business object, where the content of the MKT_MSG_DATA column is more than 2000 bytes. You get an error.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |