PeopleSoft Requisitions are designed so system users without detailed purchasing knowledge can still help in the procurement process. Requisitions require less data to be submitted on the front-end (compared to a Purchase Order) and allows for more flexibility in editing. This lets a wider range of users submit data that can be finalized and eventually used to create Purchase Orders. It adds an extra layer to solidify the purchasing process. Requisition’s final goal is to be turned into a Purchase Order.

The information below is intended to provide colleges guidance on performing a User Acceptance Test on this business process. The business process shown in the flow diagrams below may be only part of what is needed to complete an end-to-end test of a full business cycle.

To use this UAT guide first review the business process flow diagram below, which outlines the various steps to complete the test activities. Note that the business process flow diagram has distinct places where one can start testing this process, noted by a green 'Start' circle. Use the diagram, following the arrows to each step that must be executed. Use the Quick Reference Guide (QRGs) links, also below, to find the instructions on how to execute each step. The Quick Reference Guides are numbered to match each box on the flow diagram to assistant testers with following the flow of the business process. Once testing is complete for each box on the flow diagram, click the link in the Next Step (Tier 2) in the High Level UAT Framework section to access the next UAT Guide.

Printable View of FF.001.1 Requisition Processing/Review

Creating Requisition:

• FF.001.1.1 Create Requisition
  • Create Requisition / 9.2 Requisition
  • Create Requisition by Copying
• FF.001.1.2 Perform Requisition Budget Pre-Check
  • Perform Requisition Budget Pre-Check
• FF.001.1.3 Submit Requisition for Approval
  • Submit Requisition for Approval
• FF.1.1.4 Process Requisition Approvals
  • Process Requisition Approvals
  • Create Delegation Request
• FF.001.1.5 Perform Requisition Budget Check
  • Perform Requisition Budget Check

Search for an Existing Requisition:

• FF.001.1.6 Search for an Existing Requisition
  • Search for an Existing Requisition
• FF.001.1.7 Review Requisition Information
  • Review and Update Existing Requisition
• FF.001.1.8 Update Existing Requisition
  • Review and Update Existing Requisition
• FF.001.1.3 Submit Requisition for Approval (if approval required)
• FF.001.1.5 Perform Requisition Budget Check (if no approval required yet requires budget check)
  • Perform Requisition Budget Check

• FF.001.1.1 through FF.001.1.3 Create Requisition, Budget Pre-Check Requisition, and Submit for approval:
  • Copy Requisition
  • Requestor Creates Requisition
  • Once Requisition is created, Budget Pre-check, then Submit Req for approval
  • Create two or more requisition lines with multiple schedules and distribution lines.
  • Create req that requires multiple approver to approve
  • Create req using a Withholding eligible Vendor/Supplier
  • Create req that is capitalized (Asset)
• FF.001.1.4 Process Requisition Approvals:
  • Approver Denies Req and enters comments for Requestor to see
  • Approver Approvers Req
• FF.001.1.5 Perform Requisition Budget Check:
  • Budget Check Requisition Ad-Hoc
  • Run Budget Check Batch Process
• FF.001.1.6 Search for Existing Requisition:
  • Search for Requisition using an existing Requisition ID.
• FF.001.1.7 Review Requisition Information:
  • Review an Existing Requisition ID.
• FF.001.1.8 Update Existing Requisition:
  • Update an Existing Requisition ID.

• FF.001.1.1 through FF.001.1.3 Create Requisition, Budget Pre-Check Requisition, and Submit for approval:
  • Error Condition: Enter invalid chartfield combo and run Pre-Budget Check
    • Expected Behavior: Pre-Budget Check results in error
  • Error Condition: Enter different price in Line and different in Schedule page.
    • Expected Behavior: Requisition does not calculate correctly and shows error.
• FF.001.1.4 Process Requisition Approvals:
  • Error Condition: Select a Requisition with a Status not equal to Pending.
    • Expected Behavior: Approval process will only allow Requisition Status of Pending.
• FF.001.1.5 Perform Requisition Budget Check:
  • Error Condition: Perform Budget Check on a requisition before Budget Pre-Check.
    • Expected Behavior: Budget Check process does not run.
• FF.001.1.6 Search for Existing Requisition
  • Error Condition: Search for a Requisition ID that is not an Existing Value.
    • Expected Behavior: Search results will come back as No Matching Values Found.
• FF.001.1.7 Review Requisition Information
  • Error Condition: Review a Requisition ID that is not an Existing Value.
    • Expected Behavior: Search results will come back as No Matching Values Found.
• FF.001.1.8 Update Existing Requisition
  • Error Condition: Search for a Requisition ID that is not an Existing Value.
    • Expected Behavior: Search results will come back as No Matching Values Found.

UAT - FF.001 - Procure to Pay thru General Ledger

FF.001.2 Purchase Order