Last updated on JUNE 03, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.
We are having a problem running a build / alter script on PS_AUDIT_SCH_TBL in that I have entries that have differences that are outside the primary key structure only, so I get: cannot CREATE UNIQUE INDEX;
The first five have an ‘A’ in the SCH_PRIM_ALT_IND column (not in the key). There is only one other entry with an ‘A’, the rest of the table’s entries are all ‘P’s in that column.
I am questioning why this audit record was delivered in PUM 17 with unique keys. In our current production release this record does not have keys and works. Should we remove the keys and make it more consistent with other delivered AUDIT_RECORDS?
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