Defining and Using Promotions Management Approval Workflow

This chapter provides an overview of the approval framework and discusses how to:

Click to jump to parent topicUnderstanding the Approval Framework Process

Workflow is the process of routing transactions or documents to groups of users that are required to respond to a task notification message. The Promotions Management application manages the approval workflow process using the PeopleSoft Approval Framework. The framework requires the setup of an approval process. The approval workflow process is the framework that enables three levels of users, from technical to end users, to develop and configure transaction approvals that meet their organizational requirements. Approval workflow formalizes the process used to notify approvers of pending tasks requiring action to approve or deny transactions or documents.

Promotions Management uses the approval framework in conjunction with customer promotions, customer claims, and payment authorizations. Using the approval framework, you can route promotions management transactions for approval, monitor the approval process from person to person, log who approved or denied transactions, reference comments made during the approval process, and finally update the transaction to an approved status.

In Promotions Management, you can route workflow approval notification messages to an individual or group of approvers to authorize customer promotions, claims, or payment authorizations. The approval process starts with the transaction originator who selects to initiate the workflow authorization process. Approvers receive a notification on their worklist or through email to review the transaction and are presented with options to:

Click to jump to top of pageClick to jump to parent topicImplementing Promotions Management Approval Workflow

This section describes implementing Promotions Management approval workflow. It describes tasks that application developers and business analysts perform to make approval workflow available. Other sections, later in this chapter, describe the steps for users to approve and deny approval of promotions, claims, and payments.

Note. Setting up the PeopleSoft Approval Framework requires a technical knowledge of PeopleSoft application development. This chapter highlights the approvals as they relate to Promotions Management. The PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook provides more detailed information about approval workflow.

See PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

To implement Promotions Management approval framework:

  1. Register information with the approval framework by using the Approval Transaction Registry page.

    As part of defining the registry, application developers create a record and table in which to store cross-reference information and set up notification templates for events. This determines the pending approval framework process and specifies to an application which transaction is being approved or denied.

  2. Set up approval process definitions for use with claims, payments, and promotions.

    See Establishing Approval Framework Processes.

  3. Configure the transaction component.

    You use the Configure Transaction page in the Approval component to perform this step. You select and define elements that determine what triggers a notification, who receives the notification, and the content of the notification. Notifications are mapped to work with the approval transaction registry and include menus and components and SQL definitions.

    See PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

  4. Set up Promotions Management options to use workflow.

    See Defining General Options.

  5. Establish roles and user-list definitions.

    A role is a list of users who perform the same type of work, such as buyers or managers. You use user-list definitions to associate roles with user lists that define user sources for use with steps in the approval process. Each role has a set of parameters that determine the limits of the role in the organization and in the workflow process.

    See Defining Users for Approval Workflow, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

  6. Establish a customer tree if you want to route approvals in conjunction with a tree structure.

    The approval workflow engine routes promotion transactions through the approval process using the customer tree hierarchy. Transactions flow up the tree to the appropriate approvers until their final approval and then notifications are routed back to the originator.

    Note. As a default value, Promotions Management approvals are set up to use the Promotions Management Customer Tree to determine the approval chain. However, you can set up the approval workflow engine to use any valid approval chain.

    See Defining Tree Options.

  7. Users manage an approval through its life cycle.

    After you set up approval workflow, the system uses the setup information to process promotion, claim, and payment approvals. This is when requesters and approvers perform approval tasks that apply the setup features you defined. During the life cycle:

    1. Requesters submit a promotion, claim, or payment for approval.

      This launches the approval process. The approval workflow engine reads the approval process definition and queues the transaction for approvers. The system queues an approval task to an approver or reviewer using an email, a worklist entry, or both. The URL encoded in the worklist entry points to the corresponding approval component.

    2. Approvers take action on transactions.

      Approvers can approve, deny, or pushback approvals. Use the next links to view more detailed steps for approving promotions, claims, and payments.

    3. Administrators monitor approvals.

      When an error or violation of criteria or rules occur during the approval process, the system notifies the administrator who can then interact to resolve the issue.

      See Approving Customer Promotions.

      See Approving Payment Authorizations.

      See Approving Customer Claims.

      See Monitoring Approvals.

See Defining Users for Approval Workflow, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

See Defining the Approval Transaction Registry, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to parent topicSetting Up Promotions Management Approval Framework

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicPages Used to Set Up Promotions Management Workflow

Page Name

Definition Name

Navigation

Usage

General Options

TD_SETID_PREF

Set Up Financials/Supply Chain, Business Unit Related, Promotions Management, Promotions Options

Define general options for the approval framework which includes basic setup and default options for using the approval workflow in Promotions Management.

Transaction Registry

EOAW_TXN

Enterprise Components , Approvals, Approvals, Transaction Registry

Register the approval transaction. The transaction definition is the metadata that describes the transaction make-up to the approval workflow engine.

Setup Process Definitions

EOAW_PRCS_MAIN

Enterprise Components , Approvals, Approvals, Approval Process Setup

Define basic approval process details and approval workflow process stages.

Criteria Definition

EOAW_CRITERIA

Click the Alert Criteria link on the Setup Process Definitionspage.

Define alert criteria for the approval framework.

Approval Path Definition

EOAW_PATH_SEC

Click the Path Details link on the Setup Process Definitions page.

Set up approval framework paths.

Approval Step Definition

EOAW_STEP_SEC

Click the Step Details link on the Setup Process Definitions page.

Define steps for the approval framework.

User List Definition

EOAW_USER_LIST

Enterprise Components, Approvals, Approvals, User List Setup

Define user-list definitions.

Approval Authorization

EOAW_AUTH

Enterprise Components, Approvals, Approvals, Approval Authorization

Authorize Promotions Management approvers.

Criteria Definition

EOAW_CRITERIA

Click the Self-Approval Criteria link on the Approval Authorizationpage.

Define self-approval criteria.

Generic Template Definition

WL_TEMPLATE_GEN

PeopleTools, Workflow, Notifications, Generic Templates

Enter generic template definitions.

Click to jump to top of pageClick to jump to parent topicDefine General Options for the Approval Framework

Access the Promotions Options - General Options page (Set Up Financials/Supply Chain, Business Unit Related, Promotions Management, Promotions Options).

Use this page to select one or more check boxes to activate the approval framework for customer promotions, customer claims, and payment authorizations. You can activate one or more workflow approvals for use in Promotions Management. The workflow approvals check box for promotions, for claims, or for payments must be enabled on the Promotions Options - General Options page to use the workflow approval process.

Select the active approval tree on the Promotions Options - Tree Options page to determine the group of reviewers that you will use to approve these promotion transactions. The approval framework will be determined by the customer tree hierarchy and the assigned approver designation. A user or role is considered to be an approver for promotion transactions if the Promotions, Payments, or Claims check box is checked in the Can Approve group box on the active approval tree.

See Defining General Options.

See Also

Defining General Options

Click to jump to top of pageClick to jump to parent topicDefining the Transaction Registry

Access the Register Transactions page (Enterprise Components , Approvals, Approvals, Transaction Registry).

Use this page to register the Promotions Management application with the approval workflow engine. Using the page, you can define how the system interacts with portions of the application that you have defined for approvals. The registry links the components, event handler, records, and classes that you created in the approval process for an application transaction such as a promotion, claim or payment authorization. Application developers register the main records and components that make up the transaction, then functional business analysts select the approval transaction on which to base the approval process definition.

PeopleSoft Promotions Management is delivered with predefined transaction registries for Promotions, Claims, and Payments. You can use these as templates to build registers for other approval framework workflows that you might want to develop or you can modify the templates. Remember that establishing and updating registries requires PeopleSoft application development knowledge.

See Defining the Approval Transaction Registry, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to top of pageClick to jump to parent topicEstablishing Approval Framework Processes

Access the Setup Process Definitions page (Enterprise Components , Approvals, Approvals, Approval Process Setup).

Use this page to define an approval process definition. The process is made up of stages, path criteria, and approver requirements. The approval steps that you place on the approval path represent the approval levels that are required for an approval framework transaction.

Each PeopleSoft application has a top-level record (known as a header) with keys that uniquely identify a single transaction in an application such as a promotion, claim, or payment request. The application itself typically has other records, but they are children (line-level records) of the header record.

Note. Promotion approvals are processed only at the header level.

Note. A sample approval process definition is provided for each of the promotion transactions (TD_CLAIM, TD_PAYMENT, and TD_PROMOTION). You can change any of the settings to meet business needs.

See Setting Up Approval Framework Process Definitions, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook

Click to jump to top of pageClick to jump to parent topicDefining Alert Criteria for Approval Workflows

Access the Criteria Definition page (click the Alert Criteria link on the Setup Process Definitionspage).

Use this page to define the different types of criteria that you want to apply to a workflow approval process. You can create definitions consisting of a field with a logical operator and a value or definition consisting of an application class that takes in transaction data to process the approval.

Criteria is an entity that evaluates to true or false. Criteria programs the approval workflow engine, using transaction-specific information to change, for example, routing paths. To set the context for the criteria, the engine provides the transaction keys as bind values.

See Setting Up Approval Framework Process Definitions, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to top of pageClick to jump to parent topicSetting Up Approval Framework Paths

Access the Approval Path Definition page (click the Path Details link on the Setup Process Definitions page).

Use this page to set up additional parameters that determine how the system processes an approval path. A path contains a sequence of steps for a specific stage. Within a stage, paths are processed in sequence. The path entry criteria determines whether a path is processed for a given transaction or transaction line.

Use the escalations feature to define time elements for when an approver takes too long to approve or deny a pending request.

See Setting Up Approval Framework Process Definitions, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to top of pageClick to jump to parent topicDefining Steps for the Approval Framework

Access the Approval Step Definition page (click the Step Details link on the Setup Process Definitions page).

Use this page to define steps for the approval workflow. A step represents one or more approvers or reviewers. Steps within a path are processed in sequence. Separate criteria for each step determines whether that step is performed. Each step can also have a set of reviewers, who are notified about transaction pending approval by email, if configured, and through the worklist. Workflow will proceed without waiting for a reviewer or approver to take action.

Note. The pre-defined approval process definitions for the promotion transactions are set up to only require one approver, but this can be changed to meet the business needs.

See Setting Up Approval Framework Process Definitions, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to top of pageClick to jump to parent topicMaintain User-List Definitions

Access the User List Definition page (Enterprise Components, Approvals, Approvals, User List Setup).

Use this page to define user sources for use with steps in the customer promotion, claims, or payment processes. Promotions Management uses a user list as a means to map users to certain functional roles; thereby reducing source search time. PeopleSoft delivers a set of default user-list roles corresponding to the roles within an organization. These roles are intended primarily for use with routing controls.

See Defining Users for Approval Framework, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Promotions Management is delivered with samples of users for each of the promotion transactions. They include Customer Claim Approvers, Customer Payment Approvers, and Customer Promotion Approvers. You can use the sample data to help define workflow user lists. The list is set up to retrieve the user list from a SQL definition that pulls users and roles from the active approval tree defined on the Promotions Options - Tree Options page. You can change the user list to meet organizational needs.

Role

Select to use a role as the source for this user list. A role is a list of users who perform the same type of work, such as claim or payment administrators. Each role has a set of parameters that determine what the roles can and cannot do in the organization and in the workflow process.

Note. The SQL definition, Query, and Application Class user-list sources are dynamic, and can use input values to help identify users.

SQL Definition (structured query language definition)

Select to use a SQL definition as the source for this user list.

Query

Select to use a query as the source for this user list. When a source is defined as a query, the system determines who should receive a work item based on the field values on the page that triggers the routing.

Application Class

Select to use an application class as the source for this user list. When you select to use an application class, the system passes in the originator of the transaction and then determines the approver for that originator. For subsequent approval steps, the system passes in the approver from the previous step.

Include Users as Input

Select to use the originator of a transaction as the first step in each path. For subsequent steps in each path, the system uses the approver from the previous step.

Transaction Keys as Input

Select to have the system base the approval routing on transaction keys. Transaction keys are key fields in a database table. System actions depend on the approval level at which a user list is being used. If the approval is at the header level, the system uses transaction record keys from the header record.

See Defining Dynamic Approvals, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to top of pageClick to jump to parent topicAuthorizing Promotions Management Approvers

Access the Authorize Approvers page (Enterprise Components, Approvals, Approvals, Approval Authorization).

Use this page to define approvers and their approval authorization criteria for use in an approval process.

Approval Process ID

Select an approval process for which you want to authorize approvers. The approval processes are those designed by application developers. Applications that are integrated with the approval framework use the approval process IDs.

Role Name

Select a role that you want authorized as an approver when this approval process is used for promotions, claims, or payment authorizations. You can select a role name or a user ID for each row, but not both.

User ID

Select a user that you want to authorize as an approver when this approval process is used for promotions, claims, or payment authorizations.

Criteria

Select to access the Criteria Definition page where you can set up approval criteria for each user or user role you select.

Self-Approval Criteria

Select to access the Self Criteria Definition page, where you can set up criteria that defines the conditions when users or user roles can approve their own contract documents.

Click to jump to top of pageClick to jump to parent topicDefining Self-Approval Criteria

Access the Criteria Definition page (click the Self-Approval Criteria link on the Approval Authorization page).

Use this link to enable the check box for self-approvals. If self-approval is enabled, the requester's approval is assumed, and the process continues; however, you can establish criteria that helps control the requester's approval authority. For example, you can place a limit on the monetary amount for the requester so that if the transaction is over that amount, the requester is not used as an approver.

If self-approval is not enabled, then the system does not consider the requester an approver for that transaction. If the transaction requester is an approver on a step in any path in the process, then all prior steps in that path are omitted. Also, if self-approvals are enabled, and the self-approval criteria is met, then that step is omitted.

See Setting Up Approval Framework Process Definitions, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to parent topicApproving Customer Promotions

This section discusses the workflow approval process for customer promotions in Promotions Management.

Click to jump to top of pageClick to jump to parent topicPage Used to Approve Customer Promotions

Page Name

Definition Name

Navigation

Usage

Promotion Details

TD_PROMO_CUST_DTL

Promotions, Manage Promotions, Create Customer-Specific Promo, Customer Promotions

Click the Submit button to initiate the approval framework process for customer promotions.

Click the Approve button to review and approve the customer promotion and notify the originator.

Click the Deny button to reject the customer promotion and notify the originator.

Click the Pushback button to return the customer promotion to the previous approver on the workflow approval list.

Note. You must have previous approvers on the workflow approval list for the Pushback button to display.

Enter notes in the Comments box when you select the approve, deny or pushback button.

Click the Approval Status Monitor link to review approval status and comments, and to include ad hoc or secondary workflow approval processes.

Click to jump to top of pageClick to jump to parent topicApproving Customer Promotions

Access the Create Customer-Specific Promo - Promotions Detail page (Promotions, Manage Promotions, Create Customer-Specific Promo, Customer Promotions).

This page illustrates the Submit button that you use to initiate the approval framework process for customer promotions. After you click Submit, the system updates the page to indicate that the promotion is pending approval as shown in this example:

This page illustrates the Approve, Deny, and Pushback buttons that you use to accept or reject a promotion during the approval process:

After an approver approves a promotion, the system updates the Promotion Details page to indicate that the promotion has been approved. You can click the Approval Status Monitor link to view the approval details:

This page illustrates the promotion status after all approvals have been accepted for the customer promotion.

These steps describe the customer promotion approval process:

  1. The promotion initiator adds a new customer promotion.

    The system sets the initial approval status to Planned and displays the Promotion Details page.

  2. The originator clicks the Submit button to initiate the workflow approval process.

    The system routes the promotion up the customer tree and creates worklist entries for the approvers and reviewers.

    Note. This button will only display if you activate the For Customer Promotions check box on the Promotions Options - General Options page.

  3. Approvers access the system and use one of these methods to determine whether an approval is pending:

    The notification provides details about the promotion and a link to access the Create Customer-Specific Promo component for the promotion that requires approval.

  4. Approvers access the Promotion Details page.

    The system displays the promotion with a Promotion Status of Pending Approval. The page will also present the Approve, Deny, and Pushback buttons. Using this page, approvers can preview the transaction and, if they have the authority, edit it.

    Note. The Pushback button will only display from the second approver forward so that an existing approver is available to accept the pushback.

  5. The Approval Status Monitor link displays so that you can review the approval history and comments for the promotion. Ad hoc approvers or simultaneous workflow approvals can also be initiated from the approval monitor.

  6. (Optional). Approver clicks the Approve button.

    The system displays the Approval Comment page where you can enter any necessary comments about the approval. The system will send a workflow message back to the originator when the final approver approves the transaction and will set the Promotion Status to Management Approved.

  7. (Optional). Approver clicks the Deny button.

    The system displays the Denial Comment page where you can enter any necessary comments about the denial. The system will send a workflow message back to the originator and will set the Promotion Status to Management Rejected.

  8. (Optional). Approver clicks the Pushback button.

    The system displays the Approval Pushback Comment page where you can enter any necessary comments about the pushback. The system will send a workflow message to the previous approver to make updates to the customer promotion and re-submit it for approval.

    Note. The Pushback button will only display if this is the second approver or higher, indicating that an existing approver is available to accept the pushback.

    Note. The Approve, Deny, and Pushback buttons will only display if the Submit button was previously selected.

  9. Click the OK button.

    The system updates the approval status for the current approver and sends the notification to the next approver in the group, to the originator on final approval or denial of the transaction, or to the previous approver on pushback.

  10. The originator accesses the Promotion Details page and clicks the Approval Status Monitor link to review status and comments about the approval.

  11. Once all reviewers have approved the promotion, the Promotion Status will be updated to Management Approved.

Click to jump to parent topicApproving Payment Authorizations

This section discusses the workflow approval process for payment authorizations in Promotions Management.

Click to jump to top of pageClick to jump to parent topicPages Used to Authorize Payments

Page Name

Definition Name

Navigation

Usage

Payment Authorization

TD_PAYMENT_INFO

Promotions, Payments, Authorize Payments, Payment Authorization

Click the Submit button to initiate the approval framework process for payment authorizations.

Click the Approve button to review and approve the payment authorization and notify the originator.

Click the Deny button to reject the payment authorization and notify the originator.

Click the Pushback button to return the payment authorization to the previous approver on the workflow approval list.

Note. You must have previous approvers on the workflow approval list for the Pushback button to display.

Enter notes in the Comments box when you select the approve, deny or pushback button.

Click the Approval Status Monitor link to review approval status and comments, and to include ad hoc or secondary workflow approval processes.

Click to jump to top of pageClick to jump to parent topicApproving Payment Authorizations

Access the Payment Authorization page (Promotions, Payments, Authorize Payments, Payment Authorization).

This page illustrates how the page appears after the payment has been submitted for approval.

These steps describe the payment authorization approval process:

  1. The payment processor uses the Payment Search page to locate the payment authorization.

  2. The payment processor selects Maintain from the Action field to update the payment authorization.

    The system sets the initial approval status to Not Authorized and displays the Payment Authorization page.

  3. The payment processor clicks the Submit button to initiate the workflow approval process.

    The system routes the payment authorization up the customer tree and creates worklist entries for the approvers and reviewers.

    Note. This button will only display if you activate the For Payments check box on the Promotion Options - General Options page.

  4. Approvers access the system and use one of these methods to determine whether an approval is pending:

    The notification provides details about the pending payment authorization and a link to access the Payment Authorization component.

  5. Approvers access the Payment Authorization page.

    The system displays the payment authorization with a Status of Pending Approval. The page will also present the Approve, Deny, and Pushback buttons. Using this page, approvers can preview the transaction and, if they have the authority, edit it.

    Note. The Pushback button will only display from the second approver forward so that an existing approver is available to accept the pushback.

  6. The Approval Status Monitor link displays so that you can review the approval history and comments for the payment authorization. Ad hoc approvers or simultaneous workflow approvals can also be initiated from the approval monitor.

  7. (Optional). Approver clicks the Approve button.

    The system displays the Approval Comment page where you can enter any necessary comments about the approval. The system will send a workflow message back to the originator when the final approver approves the transaction and will set the Status to Authorized.

  8. (Optional). Approver clicks the Deny button.

    The system displays the Denial Comment page where you can enter any necessary comments about the denial. The system will send a workflow message back to the originator and will set the Status to Rejected.

  9. (Optional). Approver clicks the Pushback button.

    The system displays the Approval Pushback Comment page where you can enter any necessary comments about the pushback. The system will send a workflow message to the previous approver to make updates to the payment authorization and re-submit it for approval.

    Note. The Pushback button will only display if this is the second approver or higher, indicating that an existing approver is available to accept the pushback.

    Note. The Approve, Deny, and Pushback button will only display if the Submit button was previously selected.

  10. Click the OK button.

    The system updates the approval status for the current approver and sends the notification to the next approver on the workflow list, to the originator on final approval or denial of the transaction, or to the previous approver on pushback.

  11. The originator accesses the Payment Authorization page and clicks the Approval Status Monitor link to review status and comments about the approval.

  12. After all reviewers have approved the payment authorization transaction, the Status will be updated to Authorized.

Click to jump to parent topicApproving Customer Claims

This section discusses the workflow approval process for customer claims in Promotions Management.

Click to jump to top of pageClick to jump to parent topicPages Used to Approve Customer Claims

Page Name

Definition Name

Navigation

Usage

Claim Entry

TD_CLAIMS

Promotions, Payments, Authorize Payments, Claim Entry

Click the Submit button to initiate the approval framework process for customer claims.

Click the Approve button to review and approve the customer claim.

Click the Deny button to reject the customer claim and notify the originator.

Click the Pushback button to return the customer claim to the previous approver on the workflow approval list.

Note. You must have previous approvers on the workflow approval list for the Pushback button to display.

Enter notes in the Comments box when you select the Approve, Deny, or Pushback button.

Click the Approval Status Monitor link to review approval status and comments, and to include ad hoc or secondary workflow approval processes.

Customer Claims

TD_CLAIMS_CUST

Promotions, Payments, Create Customer Claim, Customer Claims

Click the Submit button to initiate the workflow approval process for customer claims.

Click the Approve button to review and approve the customer claim.

Click the Deny button to reject the customer claim and notify the originator.

Click the Pushback button to return the customer claim to the previous approver on the workflow approval list.

Note. You must have previous approvers on the workflow approval list for the Pushback button to display.

Enter notes in the Comments box when you select the approve, deny or pushback button.

Click the Approval Status Monitor link to review approval status and comments, and to include ad hoc or secondary workflow approval processes.

See Approving Customer Claims.

Click to jump to top of pageClick to jump to parent topicApproving Customer Claims

Access the Claim Entry or Customer Claims page (Promotions, Payments, Authorize Payments, Claim Entry).

Customer claim pages are similar to customer promotion approval pages. These steps describe the claims approval process:

  1. The claim processor creates a claim using the Claim Entry or Customer Claims page.

    The system sets the Status to Initial on the Claim Entry or Customer Claims page.

  2. The claim processor clicks the Submit button to initiate the workflow approval process.

    The system routes the customer claim up the customer tree and creates worklist entries for the approvers and reviewers.

    Note. This button will only display if you activate the For Claims check box on the Promotion Options - General Options page.

  3. Approvers access the system and use one of these methods to determine whether an approval is pending:

    The notification provides details about the pending claim and a link to access the Customer Claim component for the claim that requires approval.

  4. Approvers access the Claim Entry or Customer Claims page.

    The system displays the claim with a Status of Pending. The page will also present the Approve, Deny, and Pushback buttons. Using this page, approvers can preview the transaction and, if they have the authority, edit it.

    Note. The Pushback button will only display from the second approver forward so that an existing approver is available to accept the pushback.

  5. The Approval Status Monitor link displays so that you can review the approval history and comments for the customer claim. Ad hoc approvers or simultaneous workflow approvals can also be initiated from the approval monitor.

  6. (Optional). Approver clicks the Approve button.

    The system displays the Approval Comment page where you can enter any necessary comments about the approval. The system will send a workflow message back to the originator when the final approver approves the transaction and will set the Status to Approved.

  7. (Optional). Approver clicks the Deny button.

    The system displays the Denial Comment page where you can enter any necessary comments about the denial. The system will send a workflow message back to the originator and will set the Status to Rejected.

  8. (Optional). Approver clicks the Pushback button.

    The system displays the Approval Pushback Comment page where you can enter any necessary comments about the pushback. The system will send a workflow message to the previous approver to make updates to the customer claim and re-submit it for approval.

    Note. The Pushback button will only display if this is the second approver or higher, indicating that an existing approver is available to accept the pushback.

    Note. The Approve, Deny, and Pushback button will only display if the Submit button was previously selected.

  9. Click the OK button.

    The system updates the approval status for the current approver and sends the notification to the next approver in the workflow list, to the originator on final approval or denial of the transaction, or to the previous approver on pushback.

  10. The originator accesses the Claim Entry or Customer Claims page and clicks the Approval Status Monitor link to review the status and comments about the approval.

  11. After all reviewers have approved the customer claim transaction, the Status will be updated to Approved.

Click to jump to parent topicInserting Ad Hoc Users

Access the Approval Status Monitor page from the Customer Promotion, Claim Entry, Customer Claim, or Payment Authorization page.

Click to jump to top of pageClick to jump to parent topicPages Used to Enter Ad Hoc Users

Page Name

Definition Name

Navigation

Usage

Approval Status Monitor

TD_APPR_MONITOR

Promotions, Manage Promotions, Create Customer-Specific Promo, Promotion Details

Promotions, Payments, Authorize Payments, Payment Authorization

Promotions, Payments, Authorize Payments, Claim Entry

Promotions, Payments, Create Customer Claim, Customer Claim Entry

Enter ad hoc approvers or simultaneous workflow approvals can be initiated from the approval monitor.

Click to jump to top of pageClick to jump to parent topicInserting Ad Hoc Users

Access the Approval Status Monitor page from the Promotion Details, Claim Entry, Customer Claim, or Payment Authorization page.

To add ad hoc approvers and reviewers, click the plus (+) symbol for a pending approval. Another page appears for you to select the user ID and whether the person is an ad hoc approver or reviewer for this path of the Promotions Management transaction.

The symbol appears on both sides of the approver or reviewer, enabling you to place the additional approver or reviewer before or after an existing approver or reviewer. When you add an approver, the system inserts the name and indicates that the user was inserted into the approval process.

You cannot change ad hoc approvers or reviewers; however, you can delete and add them again to update whether they are approvers or reviewers. To delete an approver or reviewer, click the minus (-) symbol. You can remove only approvers or reviewers that you add. A confirmation message appears when you make the selection.

To add a new workflow approval to simultaneously route a second workflow approval for a promotion transaction, click the (+) Start New Path link. Add a new user ID to initiate the approver or reviewer process for the Promotions Management transaction.

See PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Click to jump to parent topicMonitoring Approvals

This section discusses how to monitor approvals.

Click to jump to top of pageClick to jump to parent topicPage Used to Monitor Approvals

Page Name

Definition Name

Navigation

Usage

Monitor Approvals

EOAW_ADM_MON_ACT

Enterprise Components, Approvals, Approvals, Monitor Approvals

Monitor approvals.

Click to jump to top of pageClick to jump to parent topicMonitoring Approvals

Access the Monitor Approvals page (Enterprise Components, Approvals, Approvals, Monitor Approvals).

The promotions manager uses this page to review a list of customer promotion, claim, or payment authorization transactions occurring in Promotions Management. The manager can also administer approvals by reassigning those that do not have alternates defined for their approval. You can enter criteria to limit the number of approvals that the system displays.

After you perform the search, you can reassign multiple approvals at once. Depending on the criteria that you use for the search, you might be able to reassign all approvals that appear in the search results. To select all approvals for reassignment, click the Select All link in the search results section of the page.

If you decide not to reassign all approvals at once, click the Deselect All link.

See Using the Approval Monitor, PeopleSoft Enterprise Components: Approval Framework 9.1 PeopleBook.

Search Criteria

Use this grid to define search criteria for reviewing customer promotion, claim, and payment authorization transactions. If you do not enter search criteria, all promotion transactions appear when you click the Search button. You can limit the search to specific criteria, such as the approver or originator. You can also search for specific approval processes and statuses. The Approval Process IDs for customer promotions, payment authorizations and claims are TD_PROMOTION, TD_PAYMENT and TD_CLAIM respectively.

Mass Reassignment

Use this group box to reassign an approval when an approver does not have and alternate approver assigned. You can assign a single or multiple approvals.

Approver

Select a user who is defined as the initial approver and for whom you want to reassign an approval.

 

Reassign

Select the user to which you want to reassign an approval.

 

Allow Auto Approval

Select to enable the system to remember an approver's action for a process. The next time this approval process is presented to the approver, the system automatically applies the approver's selections. The automatic application of steps in the process is left in place until you clear the User Auto Approval check box.

 

Allow Self-Approval

Select to indicate transaction originators can also approve their own transactions. This applies only if the originator also appears as an approver. You can establish criteria that controls the transaction originator's approval authority by using the Self-Approval Criteria link. If the associated criteria evaluate to true, then self-approval is acceptable. For example, you can place a limit on the monetary amount for the requestor so that if the transaction is over that amount, the requester is not used as an approver.

Comments

Enter a description or narrative you have concerning the reassignment of the reassignment of the approvals.

 

Reassign Selected

Click to perform the reassignment of the approval. If you want to reassign multiple approvals, use the promotions, claims, and payments lists in the upper part of the page to select the approvals for reassignment. When you click the Reassign Selected button, the system reassigns the approvals to the new approver.