Position Management Error Updating Incumbent with Employee ID xx, Employee Record number 0, (1000,1358)

Posted on by

Position Management Error: “Error Updating Incumbent with Employee ID xx, Employee Record number 0

Position Management Error: “Error Updating Incumbent with Employee ID xx, Employee Record #0, (1000,1358)”. Error updating incumbent record when Position data is updated online or through a CI

SYMPTOMS

When you update the Position Record, and the “Update Incumbents” check box is checked, after saving the record, the system returns message (1000,1358) stating that an error occurred when updating one or more incumbents. The incumbent’s job record is not updated as expected. Performing the same task with other positions does not give this warning and incumbent records are updated. If the position has more than one active incumbent, some incumbents may be updated.

STEPS TO REPLICATE:
————————–
1. Navigate to Organizational Development > Position Management > Maintain Positions/Budgets > Add/Update Position. Open a position and change data on the position.
2. Verify the “Update Incumbents” box is checked on the Specific Information tab.
3. Click Save.

ERROR:
———
Error updating incumbent with Employee ID xx, Employee Record #0, (1000,1358).
An error occurred when updating one or more incumbent(s) through the update incumbent function.
Check the CI log for more information.

CAUSE

Multiple

Solution 1 – Check Job Data Setup

  1. Go to the Job Data page for the specified emplid
  2. Try doing similar changes in Job Data page by overriding the position data in a new row or existing row(as per requirement)
  3. Now save the Job data page and correct all the error messages that comes up. In this process the error message which caused the position data CI to error out will also appear.
  4. Try correcting this data condition and update data through position data page or CI and the data would get saved.
  5. If this does not help, go to customer connection and check for bundles.

Solution 2

2.1 Check Job Data Setup

This error is most often caused by data in the employee’s job record that triggers a warning when Position Management attempts to update the job record. The purpose of the message is to inform the user thathuman interaction with the system is required to save the job record for those incumbents.  The automated process cannot correct the data or select OK for warnings.

  1. Navigate to Workforce Administration > Job Information > Job Data. Open the employee’s Job Record that is mentioned in the message.
  2. Insert a new row in Job Data and change the same data which you were trying to change on the Position Data record, e.g. Location, Business Unit, etc.
  3. Save the record.
  4. Respond appropriate to all warnings and errors until the Job record is saved.

Note:  If there is a high volume of job records that require manual intervention in order for Update Incumbent’s process to update them, then you might want to track and analyze those responses that are needed to save the records.  Before making large organizational changes that will require lots of position updates, you might want to perform a sample of these changes in a copy of production.  You might identify data conditions in your Job Records that should/could be corrected before updating the positions, in order to reduce the number of human interventions that are required.

If the issue is not resolved by correcting data deficiencies in the Job Records, then please review the list of bugs below that have caused this error in the past.

2.2 – Check for Action Reason

Another cause of this issue is not having an Action Reason in the Position data while adding a row.  This will cause the error as the Action Reason is used to populate Job Data when adding a new row.

2.3 – Check for Possible Known Bugs

When setup has been ruled out as a possible root cause, it is often good to investigate bugs to see if any problems have been reported with this error. The table below lists bugs that have been reported as of the last update date for this note which cause this symptom.

 

ref 1 : https://www.shyamsblog.com/2009/09/error-updating-incumbent-record-when.html
ref 2: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=605401030017149&id=858370.1&_afrWindowMode=0&_adf.ctrl-state=in0pcdjt4_4

Posted in PeopleSoft.