Error 103136 is a relatively uncommon issue that users encounter when updating deployment dates within Cezanne. This occurs when a manager’s deployment date is moved to an earlier time, but their subordinates’ reporting relationships are set to begin after that date. These conflicting relationships prevent the system from processing the deployment update, resulting in Error 103136.
Understanding the Cause
Error 103136 is triggered when a manager is assigned a deployment start date that predates the established reporting relationships of their subordinates. For instance, consider a scenario where a manager, Bob, is being reassigned from his current role as Manager to a new role as General Manager, with a retroactive deployment date of 01/02/2023. However, one of Bob’s direct reports, Greg, began reporting to him under the Manager role on 01/01/2023. In this case, the system identifies a conflict because Greg’s reporting relationship is tied to Bob’s earlier deployment (Manager), and cannot be backdated to accommodate the new deployment (General Manager).
This issue happens because reporting relationships in the system are linked to deployment entries. When the deployment dates and reporting relationships are misaligned, as in this example, the system is unable to process the update due to the chronological inconsistency. This conflict is particularly common when making retrospective deployment changes in employee profiles.
Steps to Resolve Error 103136
Step 1: Identify the Impacted Profiles
Start by identifying the profiles mentioned in the error message. These will typically be the subordinates or direct reports of the manager whose deployment you are trying to update. Navigate to each of these profiles to begin the process.
Step 2: Access the Deployment Section
Once you’ve located the impacted profiles, go to the Deployment section. Next, navigate to Org Units / Positions and review the current deployment entry. This allows you to understand the existing reporting relationships and how they relate to the manager's deployment change.
Step 3: Temporarily Adjust Reporting Relationships
In each impacted profile, go to the Reports to section. Temporarily change the reporting relationship to another individual, such as an HR professional or a manager not involved in the current deployment change. This adjustment will break the conflicting reporting link, allowing the system to process the manager’s deployment update without any errors.
Step 4: Proceed with the Deployment Change
Once you have made temporary adjustments to the reporting relationships, proceed with updating the manager’s deployment. Use the system’s Move and Replace tool, or manually navigate to Deployments > Org Units / Positions to update the manager's new deployment information. Make sure that the deployment date and other fields are updated correctly to reflect the new position.
Step 5: Reassign Reporting Relationships
After the manager’s deployment update is successfully completed, go back to the profiles of the impacted employees. Restore their original reporting relationships by assigning them back to the correct manager.
Step 6: Save Changes
Once all the profiles have been updated and reporting relationships have been restored, save the changes. At this point, Error 103136 should no longer appear, and the deployment update should be processed successfully.
Additional Considerations
Proactive Updates: Regularly updating deployment and reporting structures can help avoid retrospective changes, reducing the likelihood of triggering Error 103136.
Handling Large Teams: For larger teams with complex reporting hierarchies, it may be useful to assign temporary placeholders (e.g., HR professionals) to multiple profiles at once before finalising deployment updates.