Today, I had my first 'Data Integrity Error (124,85)' in PeopleSoft.
It occured while I was trying to run a QA external check on the careers page for my client. I was not the only consultant who received this error - one of the others who I work alongside received the same error.
I researched the error, the supervisor opened a service request ticket, and it was resolved earlier today, but I am still curious as to what caused the error..
It makes me wonder about the quality/ source of the errors I work on in this database - some are clearly liked to administrative privileges, some are linked to missing fields of data - but others, like the (124,85), are mysterious in origin.
I realize that I am a small piece in a huge puzzle, but does resolving these errors contribute significantly to the greater picture of the project?
Title | Under | Posted on |
---|---|---|
Component interface Error: no rows exist for the specified keys | PeopleSoft Technical | 03/15/2019 - 3:54am |
ADD 24 months starting from current month.(peoplesoft) | PeopleSoft Functional | 07/29/2018 - 8:44pm |
TRC values dropdown | PeopleSoft Technical | 04/04/2018 - 12:54am |
how to find missing sequence in GRID and print the mising sequence number while saving through peoplecode | PeopleSoft Technical | 09/11/2017 - 4:49am |
Comments
Peoplesoft data Integrity Error occurs when a user is making some transaction in a page at the same time some other consultants may change the design of the page through application designer. Even a single dot of change will results to the error. Whenever the changes in application designer's page the system will try to connect through the 2 tier mode to update the changes in PIA.