Setting Up Approver Authorization

To set up approver authorizations, use the Authorize Approvers (EOAW_AUTH) component.

This topic provides an overview of approver authorizations.

Pages Used to Set Up Approver Authorizations

Page Name	Definition Name	Navigation	Usage
Approval Authorization	EOAW_AUTH	Enterprise Components, Approvals, Approvals, Authorize Approvers	Authorize roles and approvers for dynamic paths.
Criteria Definition	EOAW_CRITERIA	Click theCriteria link on the Approval Authorization page.	Define criteria for the workflow approver.
Setup Process Definitions	EOAW_PRCS_MAIN	Enterprise Components, Approvals, Approvals, Approval Process Setup	Define approval process stages.
Approval Path Definition	EOAW_PATH_SEC	Enterprise Components, Approvals, Approvals, Approval Process Setup Click the Path Details button or the Details link on the Setup Process Definitions page.	Set up workflow approval paths.
User List Definition	EOAW_USER_LIST	Enterprise Components, Approvals, Approvals, User List Setup	Set up list of users for workflow approval.
User Profile	USER_GENERAL	select PeopleTools, then select Security, then select User Profiles, then select User Profiles	Set up user IDs and assign roles.

Understanding Approver Authorizations

You can identify the approval authorization by role or user in conjunction with a dynamic step. To accomplish this, the Approval Framework selects the appropriate supervisory approver from the user list and verifies that the approver meets the criteria for authorization.

You establish approval authorizations for each transaction. The authorization can accommodate approvals by role or user ID.

You can set authorization across Definition IDs, which are defined on the Setup Process Definition page.

For each authorization, the system checks the specific user ID to see if that individual can authorize the transaction. If found, it checks the authorization criteria. If criteria are met, the user has authorization.

If no authorization is found for a specific user ID, then the system looks for role-based authorizations using the approval hierarchy.

For approval hierarchy, the system first looks for authorization by Definition ID. If no authorization is found, the system then seeks authorization for rows without a Definition ID. If no authorization approval criteria is matched, the system process is deemed Not Authorized.

You can establish dynamic authorizations for either the header or line level, but not both.

When workflow is initiated for a change order or requisition, the system compares the approval authorization data to the user list to verify the approval process. To verify the approval, the system:

Checks the user list and assigns the first approver to the first user that is returned.
Looks at the roles that are established for the user ID.
Identifies the approval limits that are set for that user ID.
Routes the requisition status to the first approver if the amount is satisfied for the requisition and the approver list is complete.
Continues to look for additional approvers until all conditions are met.
Routes the approval to the administrator if the approver criteria is never met.