OBJ558 Error Generated when Using a Date Field as the Key for a Child Object
(Doc ID 2291114.1)
Last updated on APRIL 02, 2021
Applies to:Oracle Healthcare Master Person Index - Version 188.8.131.52 and later
Information in this document applies to any platform.
On Oracle Healthcare Master Person Index (OHMPI) 184.108.40.206 version,
When attempting to create a child object in the object model that has a date field as the key (actually, a date/time),
users can create and save new child objects, but when trying to look at the transaction history, the following error is generated in the server log:
2. Build the project, create the appropriate database tables, and go into the GUI.
3. Use the Edit function in the GUI to add a comment to an EUID.
4. Try to view the transaction just created in the Transaction tab.
It will not display correctly, and the error message described will appear in the server log.
The key type of 6 indicates a date field. There is no documentation that indicates a date field can't be used as a key field.
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