Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
Information in this document applies to any platform.
After upgrading our EnterpriseOne release, example from XE to E900, users reported that their created customized grid formats are lost intermittently.
In F98950 (User Override Table), also found that there are corrupted UOUOTY= 'GD' records. From UTB (Universal Table Browser), a normal 'GD' record should have the EndData ending with </GridOverride>. It was noticed that for the corrupted GD records, the EndData does not end with </GridOverride>. From the User Override Application (P98950) these corrupted records cannot be seen from the screen. The user is unable to delete the corrupted records using the P98950 application.
An application that contains corrupted GD records does not allow new grid formats to be saved. Once the user logs out and logs back into web client again, the grid format that was created is lost. Errors of primary key constraints are shown in the jas.log when the user tries to save these newly created grid formats.
The following error can be seen from the jderoot.log after clicking the customize grid drop down list and being unable to see the grid format created.
Why do these errors occur after upgrade ?
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