Compensation Cycle Workflow Level 1 & 2 Approvals Not Working
Last updated on FEBRUARY 15, 2018
Applies to:PeopleSoft Enterprise HRMS eCompensation Manager Desktop - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
When attempting to process compensation cycle that requires approval by highest node on tree, the following occurs: Approval process skips two levels of approvals and then shows the transaction pending approval for multiple approvers. Instead of the transaction, should have been routed to the Compensation Administrator when top node on tree submits the cycle.
Consider scenario in which Supervisor A reports to Supervisor B.
1. Set up and build Compensation Cycle.
2. Log in as Supervisor A and submit the cycle.
3. Check Approval Monitor and note that two approvals are skipped, and last step is pending by multiple approvers.
(It should have gone to Supervisor B and then to Compensation Administrator, since Supervisor A reports to B, and B is top node on tree.
Due to this issue, cycles that require approval by top node on tree cannot be completed.
Approval Workflow Engine (AWE) works unpredictably for Level 1 and Level 2 workflow when root node submits compensation proposals for his direct reports because the system is not designed to handle where the proposals should go for approval. These approvals should go to Compensation Administrator.
Compensation has delivered two definition IDs in release 9.1; ByTreeNode1Lvl and ByTreeNode2Lvl.
The ByTreeNode1Lvl AWE process definition is linked to the WCSGetNextHighestSubmitter approver user list. Select this process definition in compensation cycles where you want to have one step approvals.
Select this process definition in compensation cycles where you want AWE to make the submitter/user of the parent group or tree node to be the one step approver.
The ByTreeNode2Lv1 AWE process definition is linked to the WCSGetNextHighestSubmitter and WCSGetNextHighestAdmin approver user lists.
Select this process definition in compensation cycles where you want to have two step approvals.
Select this process definition in compensation cycles where you want AWE to make the submitter/user of the parent group or tree node to be the one step approver and the administrator/user of the parent group or tree node to be the two step approver.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms