Authorizing and Approving Personnel Actions Using Fluid
Once a PAR request is submitted, the request is routed to the designated authorizers for approvals.
Using Fluid Approvals, the approvers can approve and authorize requests that cover many possible actions involving hire, return to duty, leave with or without pay, suspension, promotion, bonus, award, change in pay, and others. They can also return a request and ask for more information from the requester/ originator or disapprove the request so that it will not be processed further.
Note: Oracle PeopleSoft delivers Notification Composer Framework to manage the setup and administration of all notifications in one central location.
Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications.
Notifications delivered with HCM Image 48 or later must use Notification Composer.
For more information about Notification Composer Framework, see Understanding Notification Composer.
This topic discusses on how to take action on PAR requests using Fluid Approvals.
Note: It is recommended not to use full screen mode to open a new window while using iOS devices.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
EOAWMA_TXNHDTL_FL |
Review and take action on a Personnel Action Request using Fluid Approvals. |
The common Approval Framework is used for defining the approvers for the different transactions. For more information, see Understanding Approvals.
The following navigation options provide direct access to the fluid Pending Approvals page:
Click the Approvals tile on the Manager Self Service home page.
Click the Notifications icon in the banner that appears across the top of PeopleSoft pages, then click an approval notification.
Note: There can be multiple Approvers/ Authorizers for reviewing and approving a PAR request. All the Approvers can access the PAR approval request using their respective Pending Approvals page. Based on the role of Approvers, the field/links available in the Approvals page may vary.
PAR Administrators can configure users as 1st authorizer, 2nd authorizer, Position Administrator and the Final HR for approving a Personnel Action Request. There is also the provision to route the approval request through the Approve and Sign authority, based on the configuration made in the PAR Approving Officials Table Page
For more information on approving transaction as a Position Administrator see Approving Transaction as a Position Administrator
Note: If you enable delegation for approval, approvers can delegate approval authority to proxies for specified amounts of time. The system gives the proxy access to the Pending Approvals component.
Approvals can also be enabled for Cancellation/ Correction request based on requirement. Only the users with PAR Specialist role can Approve, Deny or Pushback the Cancellation/Correction request. For more information on enabling Approvals, see Enabling Approvals for Canceling/Correcting a PAR
Use the Pending Approvals - Personnel Action Request page (EOAWMA_TXNHDTL_FL) to review and take action on a PAR transaction using Fluid Approvals.
Navigation:
Click the Approvals tile on the Manager Self-Service home page or the Notifications button in the banner to access the Pending Approvals page. Click Personnel Action Request from the left panel and select a PAR entry from the Pending Approvals page.
This example illustrates the fields and controls on the Pending Approvals - Personnel Action Request page (As a Final HR Approver)
This example illustrates the fields and controls on the Pending Approvals - Personnel Action Request page (As a Final HR Approver)
The approval options on this page are common to all fluid approval transactions, as described in the documentation for the Pending Approvals - <Transaction Details> Page.
Field or Control |
Description |
|---|---|
Approve, Deny and Pushback |
Use these buttons to take action on the requested approval.
|
Effective Date |
Displays the effective date for the transaction (not the date that the transaction was submitted). |
Action |
Displays the action for which the Personnel Action Request is raised. |
Action Reason |
Displays the action reason specified in the Personnel Action Request. |
Nature of Action Code |
Displays the Nature of Action code corresponding to the action as specified in PAR. |
Employee Status and Approval Status |
Displays the status of the employee and the status of the approval request. |
Summary of Changes
This section show the proposed changes to the employee’s record. The grid lists the specific data changes that are being requested and the existing data.
View Job Information
Click the View Job Information link to open the Job Information Page. You can view the details such as Action, Action Reason, Nature of Action Code, Status of the request, and Approval Chain details.
This example illustrates the View Job Information page
Field or Control |
Description |
|---|---|
|
Click this icon to view PAR transaction details. The data from Create Personnel Action Page is displayed here with the changes highlighted. |
View Edit Errors
Click the View Edit Errors link to view the errors that are generated. The result on this page is based on the validation process that is run while creating PAR.
Edit Details
Click the Edit Details link to open the Create PAR page and make required changes.
Note: This link is available only for Final HR Approver.
CI Exceptions
When the Final HR Approver click the Approve button, system saves the changes and updates all the relevant tables with the new data. The system uses a series of Component Interfaces (CIs) to make these updates.
Use the CI Exceptions link to view the warning/error messages generated while CI Interface is used. If the CIs encounter an Error, the personnel action update will stop and roll back to the original state and thus no updates will be saved until you address the Error.
Note: This link is available only for Final HR Approver.
Approver Comments and Approval Chain Sections
Field or Control |
Description |
|---|---|
Approver Comments |
Enter any comments related to the approval action you take. |
Approval Chain |
Click this link to open the Approval Chain page, where you can review information about all approvers for the transaction |
Using the PeopleSoft Fluid User Interface, a Position Administrator can be added as an approver for approving a Personnel Action Request.
While configuring a nature of action, a Federal HR Administrator can configure whether the PAR for that action requires approval from Position Administrator.
For more information on configuring NOA codes, see Nature of Actions USF Page
On submitting such PAR for approval, the position administrator will be able to view the approval request in his/her Pending Approvals page.
Note: It is up to the PAR Administrator to decide if position administrator's approval is required for a specific action request.
This example illustrates the Personnel Action Request page for a Position Administrator.
Field or Control |
Description |
|---|---|
View Job Information |
Click the View Job Information link to open the Job Information Page. You can view the details such as Action, Action Reason, Nature of Action Code, Status of the request, and Approval Chain details. |
View Edit Errors |
Click the View Edit Errors link to view the errors that are generated. The result on this page is based on the validation process that is run while creating PAR. |
Add/Update Position Info |
As a position administrator, you can use the link to access the Add/Update Position Info component, make necessary position related changes, save and approve the PAR. For more information, seeUpdating Position Data |
Approver Comments |
Enter any comments related to the approval action you take. |
Approval Chain |
Click this link to open the Approval Chain page, where you can review information about all approvers for the transaction |
Once a PAR request is submitted, the request is routed to the approval queue. There can be multiple Approvers for reviewing and approving a PAR request. PAR Administrators can also configure users as 1st approver, 2nd approver, and so on, based on their business requirements. When one level of approval process is complete, system automatically routes the request to the next level.
As an administrator, you can opt not to automatically route the request to next approver and give the approver the option to select the next level approver.
This topic discuss on how to enable Route to Next feature using Fluid Approvals.
Use the Approval Flow (USF) page (GVT_WIP_ACTVTY4) to associate WIP statuses with steps in the approval process for federal self-service transactions. You can also enable Route to Next feature using this page.
Navigation:
This example illustrates the fields and controls on the Approval Flow (USF) page.
Field or Control |
Description |
|---|---|
Step Number |
Enter a number that identifies the order that the approval process will follow. The numbering of the approval steps must be sequential and begin with the number 1. Step 1 must represent the initial request, and subsequent steps must represent the approval steps as defined in the Approval Framework. |
Step Name, Description and Short Description |
Enter a name for this approval step and appropriate descriptions. |
On Action Of |
Add or modify the action for which you are defining a WIP status. Valid actions are:
|
Set Status To |
Select the WIP status to assign to the transaction when the selected action takes place. Options in the field include all the delivered Work-in-Progress (WIP) status types. |
Prompts for Route to Next |
Select this check box if you want to allow the approver to specify the next level approver, rather than automatic routing. For a example, select the Prompts for Route to Next check box for theApprove action, with the WIP status as Second Authorizer. In this transaction, when the second authorizer completes and submits the approval request, he/she will be prompted to select the next level Approver. |
This example illustrates the Route to Next Approver page.
Field or Control |
Description |
|---|---|
Route to |
Select the next level approver. The data is routed to the selected employee for approval. Look up options are listed based on the approval user list defined for the next level. |
Note: To use this functionality, no changes to Approval Flow configuration is required.