Showing posts with label HR. Show all posts
Showing posts with label HR. Show all posts
Friday, January 15, 2016
R12.1 Oracle HR: Receiving FRM-40654 error when trying to modify name
You will not believe the root cause of the MOS article "FRM-40654: Record has been updated. Requery block to see change Error When Updating a Person's Name" from note ID 2096800.1 but it sure is a good reminder to add data checks like this to your testing suites!!
Tuesday, December 3, 2013
R12: HR report API error
When we were validating our application after going to R12, we received this curious error message when running a report which would go over database links to the PeopleSoft HR application:
DECLARE
*
ERROR at line 1:
ORA-20000: Error encountered -20000 ORA-20000: Error encountered -20001 ORA-20001: The HR object is invalid
Cause: The HR object which is attempted to be locked is inconsistent with the corresponding object in the HR Schema.
Action: Retry the action with the correct o
ORA-06512: at line 247
Was the problem on our side, in the HR schema locally, or in the PSHR application? A developer that looked into the problem commented this was a message from the API indicating that an update call validation failed due to the record being updated, as opposed to any actual object invalidation. While we had not received anything like that in 11i, we were in the brave new world of R12 and anything is possible!
We followed the recommendation to try again, and this time the report did not fail when it was run. Was the employee data on our side, or PSHR, no longer locked? Did a DBA recompile invalid objects in the interim? We will never know, but I want to share this one in the hopes that it may help you down the road when you are upgrading and to get feedback if you have encountered this behavior too.
DECLARE
*
ERROR at line 1:
ORA-20000: Error encountered -20000 ORA-20000: Error encountered -20001 ORA-20001: The HR object is invalid
Cause: The HR object which is attempted to be locked is inconsistent with the corresponding object in the HR Schema.
Action: Retry the action with the correct o
ORA-06512: at line 247
Was the problem on our side, in the HR schema locally, or in the PSHR application? A developer that looked into the problem commented this was a message from the API indicating that an update call validation failed due to the record being updated, as opposed to any actual object invalidation. While we had not received anything like that in 11i, we were in the brave new world of R12 and anything is possible!
We followed the recommendation to try again, and this time the report did not fail when it was run. Was the employee data on our side, or PSHR, no longer locked? Did a DBA recompile invalid objects in the interim? We will never know, but I want to share this one in the hopes that it may help you down the road when you are upgrading and to get feedback if you have encountered this behavior too.
Subscribe to:
Posts (Atom)