Problem Statement: While doing Field Level Audit in People Soft, we might come across below issue

“INSERT INTO PSAUDIT RESULTS IN SQL ERROR FOR VALUES LONGER THAN 65
CHARACTERS”

This issue does not exists in version 8.53 and above.

Solution:

Do impact analysis to find if PSAUDIT is been used across any modules.

Use App Designer to check the database for the use of PSAUDIT anywhere in metadata objects (Find Definition References) and SQL or peoplecode (Find In).
If PSAUDIT is not in the results, i.e. not being used at all, then the table can be dropped from the database (You will see a warning when running DDDAUDIT in the future on this though).

Vice versa, if you want to keep PSAUDIT and drop PSAUDITEXT, do the same above but search for PSAUDITEXT.

Starting in 8.52, PeopleTools internal code checks whether the tables exist before attempting to write to them, so there are no issues if one of them is
deleted.

Either way data exists in both records.
For reference, here is the actual data field definition difference between the two fields:

PSAUDITEXT
PTOLDVALUE VARCHAR2(254) NOT NULL Old Value
PTNEWVALUE VARCHAR2(254) NOT NULL New Value
PSAUDIT
OLDVALUE VARCHAR2(65) NOT NULL Old Value
NEWVALUE VARCHAR2(65) NOT NULL New Value

Advertisements