AME Pahse2

TEST OUTLINE
AME Phase II
ORACLE IPROCUREMENT
Prepared by Oracle Corporation Applications Release: Author: Creation Date: Last Updated: Version: Status: R12 Cynthia Goh 14/06/2005 22:16:00 6/15/2005 12:30:00 AM 1.0 Draft
NOTE: The following information is confidential and is for internal use only. There is no commitment on content or scheduling for the functionality contained within this document. Copyright 2004 Oracle Corporation All Rights Reserved
Oracle iProcurement
AME Phase II Test Outline
Change Record Name Cynthia Goh Position QA Date May 27, 2005 Version 1.0 Initial Document Change Reference
Document Reviewers and Approval History Name Lee-Hian Quek Sonia Hunt David Chan Prabakar Paulsami QA PM Dev Dev Position Date Reviewed Comments Incorporated
Projects Covered in Test Outline Project AME Integration Phase II Project Description AME Position and Position Hierarchy
References Document Name AME R12 Functional Design Document Type FD Document Location FOL: Procurement Development > 00 iProcurement > 03 Functional Design > Release 12 > AME Integration Phase II
6/15/2005 12:30:00 AM
Oracle Confidential - For internal use only Page 2 of 47
Table of Contents
Change Record.........................................................................................................................................2 Document Reviewers and Approval History............................................................................................2 Projects Covered in Test Outline.............................................................................................................2 References................................................................................................................................................2 1. TRACEABILITY MATRIX......................................................................................................................4 1.1 AME PHASE II..........................................................................................................................................4 Features / Sub Features...........................................................................................................................4 Upgrade Requirement..............................................................................................................................5 Translation Requirement..........................................................................................................................6 Performance Requirement........................................................................................................................6 Multi-User Requirement...........................................................................................................................6 Multi-Language Requirement..................................................................................................................6 Public API Requirement...........................................................................................................................6 Dependency on Other Projects / Existing Feature...................................................................................6 Dependency on Other Products...............................................................................................................6 UI Impact..................................................................................................................................................6 1.2 TESTS CASES NOT INCLUDED........................................................................................................................7 PLEASE NOTE:.............................................................................................................................................7 FOR EVERY TEST SCRIPT MENTIONED IN THIS DOCUMENT, TWO ROUNDS OF TEST ARE REQUIRED...........................................................................................................................................7 ONE ROUND WILL BE TESTING THE GRAPHICAL VIEW OF THE APPROVAL LIST.............7 ANOTHER ROUND WILL BE TESTING THE TABLE VIEW OF THE APPROVAL LIST............7 2. SETUPS......................................................................................................................................................9 TEST OUTLINES........................................................................................................................................13 [TEST CASE ID: ICXAMEXX01] [APPROVING AND REJECTING REQUISITION RECOMMENDATION]......................13 [TEST CASE ID: ICXAMEXX02] [APPROVAL PARALLELISM AND VOTING REGIME].........................................32 [TEST CASE ID: ICXAMEXX03] [NO APPROVALS AND OAM ERROR]........................................................44 4. EFFORT ESTIMATES............................................................................................................................47
6/15/2005 12:30:00 AM
Oracle Confidential - For internal use only Page 3 of 47
1. TRACEABILITY MATRIX
1.1 AME Phase II
* This section should trace each requirement in the projects considered in this Test Outline to a Test Case (New or existing test cases to be modified). Map the feature/sub feature to a RDD_ID (ID in Requirement Definitions Document), FD_ID (ID in Functional Design Document), TD_ID (ID in Technical Design Document), and one or more Test Case IDs. The purpose is to make sure that each feature/ sub feature is covered by a test case unless it is deliberately excluded in the test coverage. Note that feature list should include all Must Have features as identified in RDD. Note the following: Performance Requirements as identified in this matrix needs to be copied to the Performance Test document for the respective products. Upgrade Requirements as identified in this matrix need to be copied to the Upgrade Test Document for the respective product / module Multi-User Test Scenarios as identified in this matrix need to be copied to the Team Drill Document for the respective product. Create a link to the document updated in the Comments field for each of the above requirements
ICXAMEXX01
ICXAMEXX02
Functions Test Script Type (N-New, E-Exist) Features / Sub Features Support for Positions & Position Hierarchy based Approval HR Position HR Position Hierarchy No holders for position Multiple holders hold the position Support for Parallel Approver Path/View Parallel Approvers Allow multiple approvers the ability to receive and respond to notification at the same time Asynchronous Parallel Approvers Allow different approver types that are in parallel to take action against a particular notification Updated User Interface Displaying Approval list Graphical View Checkout: Approvals and Notes page Notification Detail Page Approval History Page
ICXAMEXX03
TD_ID
FD_ID
Comments
6/15/2005 12:30:00 AM
Oracle Confidential - For internal use only
Page 4 of 47
ICXAMEXX01
ICXAMEXX02
Functions Table View Checkout: Approvals and Notes page Notification Detail Page Approval History Page Manage Approval Actions Manage Approval Button Change Managerial Approver Insert Approver Insert Viewer Delete Approver Delete Viewer Reset Approval List Approval Actions Approve Reject Request More Information Reassign No Approvals needed A requester proceeding to the checkout process and there are no approvals required. This user interface update displayed in graphical and table format Support for AME Voting Regime Options Serial Consensus First Responder Wins Order Number Support for Viewers(FYI) A person that receives the requisition as an FYI only and does not take any action against the requisition Upgrade Requirement None
ICXAMEXX03
TD_ID
FD_ID
Comments
6/15/2005 12:30:00 AM
Page 5 of 47
ICXAMEXX01
ICXAMEXX02
Functions Translation Requirement None Performance Requirement None Multi-User Requirement None Multi-Language Requirement None Public API Requirement None Dependency on Other Projects / Existing Feature None Dependency on Other Products None UI Impact None
ICXAMEXX03
TD_ID
FD_ID
Comments
6/15/2005 12:30:00 AM
Page 6 of 47
1.2 Tests Cases not Included

* Reason is required for not covering in this project. If the test is covered elsewhere, please provide the test script ID. The following test is not covered in this project: Existing AME Employee-Supervisor testing will not be mentioned here. (Existing Feature) Existing PO-Based Approval testing will not be mentioned here. (Existing Feature)
Please Note:
Test Verification
For every test script mentioned in this document, two rounds of test are required. One round will be testing the Graphical View of the Approval List o To test Graphical View, set system profile POR: Display Graphical Approval List = Yes
o
o
Hereafter, Graphical View test will be labeled as GVT Verifications prefix with GVT indicates that the verification is specific to Graphical View test
Another round will be testing the Table View of the Approval List o To test Table View, set system profile POR: Display Graphical Approval List = No
o
o
Hereafter, Table View test will be labeled as TVT Verifications prefix with TVT indicates that the verification is specific to Table View test
Otherwise mentioned, all verifications and flows mentioned within the test scripts are mandatory to both GVT and TVT executions.
User Interface (UI) Representation

Actual UI representation will not be shown here. A simplified diagram will be represented as close to the actual UI as possible. Following Symbol Icons will be verified as displayed in the center of the approver/viewer box:
{Q: Are you including the icons next to the
bullet points?} A: I will take the icons from the UIX.

Approver Icon Approval Group Icon Viewer Icon
Following Action Icons mentioned in the test scripts will be verified as displayed at the top left corner of the approver/viewer box: :
including the icons next to the bullet points?}

Pending Status Icon Approved Status Icon
{Q: Are you
6/15/2005 12:30:00 AM
Page 7 of 47
Rejected Status Icon Request Information Status Icon
6/15/2005 12:30:00 AM
Page 8 of 47
2.
SETUPS
* This section should describe all setups that are used or required in the test cases outlined below. Consider user setups, items setups, profile options needed etc. OU Security Profile Settings Security Profile List of Operating Units (OU) Vision France Vision Operations Vision Sweden Vision UK <TBD> Vision France Type (New/ Exist) New Notes
QASecurityProfile-ALL
Indicates that user has access to negotiations created in listed OU
{Q: Why negotiations?} A: Will be removed

New Indicates that user has access to negotiation created in Vision France only {Q: Why
QASecurityProfile-VF
negotiations?} A: Will be removed

QASecurityProfile-VO Vision Operations New Indicates that user has access to negotiation created in Vision Operations only {Q: Why
negotiations?} A: Will be removed
User Requirement User Responsibility Security Profile Assignment QASecurityProfile-VO Type (New / Exist) New Exist QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO QASecurityProfile-VO New New New New New New New New New New New No position assigned Notes
USER01
iProcurement Approval Management Application Administrator
USER13 USER21 USER22 USER23 USER24 USER25 USER26 USER27 USER28 USER29 USER30
iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement iProcurement
System Profile Settings Profile MO: Default Operating Unit MO: Security Profile POR: Display Graphical Approval List POR : System Approvers are Mandatory 3/22/2013 Controlled By (Site/User) Responsibility Responsibility User User Default Value Vision Operations QASecurityProfile-ALL Yes No Page 9 of 47
Setup: Purchasing On Document Types page, set Default Hierarchy = Position Hierarchy #1
3/22/2013
Page 10 of 47
Human Resource Position & Position Hierarchy Setup Position Hierarchy #1 ( denotes report to) Summary: BUY500.BUYER1 MM400.MATERIALS MANAGER Approver Assignment: USER01 USER21, USER28 USER22 Position Hierarchy #2 ( denotes report to) Summary: ENG490.ENGINEER IS110.INFORMATION SYSTEMS MANAGER Approver Assignment: USER24 USER25 AME Groups Setup Group #1 (QAApprovalGroup1). Members: USER28 USER30 Group #2 (QAApprovalGroup2). Members: USER29 AME Setup AME Action Definition Order Number Rule Name
AME Rule 0
PDR810.PRODUCTION DIRECTOR USER23, USER30
VPM200.VP MATERIALS
DIR001.DIRECTOR USER 26
AME Rule Definition
Type
Absolute Job Level
Order
Unique 1
Chain-ofAuthority Ordering Mode

Serial
Voting Regime
Serial
Condition(s)
0 < REQUISITION_AMOUNT <= 1,000
Action(s) Require approvals up to at least level 1.

Chains of authority based on a
AME Rule 1
HR Position
Unique
Serial
Serial
1,000 < REQUISITION_AMOUNT <= 5,000 ITEM_CATEGORY=MISC.MISC PO_COST_CENTER=01-740-7330-0000-00
{Q: HR Level or Position?} A: Description as per AME

particular HR Requires approval up to at least position 3
AME Rule 2A
HR Position Hierarchy
Unique
Serial
Serial
0 < REQUISITION_AMOUNT <= 5,000 ITEM_CATEGORY=CATHRC.CATHRC
AME Rule 2B
Approval Group (QAApprovalGroup1)
Unique
Serial
Consensus
5,000 < REQUISITION_AMOUNT <= 10,000
Chains of authority includes an approval group
3/22/2013
Page 11 of 47
AME Action Definition Order Number Rule Name

AME Rule 2C AME Rule 3A AME Rule 3B AME Rule 3C
AME Rule Definition
Type
HR Position Hierarchy HR Position Hierarchy Pre-Approval Group (QAApprovalGroup1) Post-Approval Group (QAApprovalGroup2)
Order
Unique Unique Unique Unique 1 1 1 1
Chain-ofAuthority Ordering Mode

Serial Serial -
Voting Regime
Serial Serial -
Condition(s)
5,000 < REQUISITION_AMOUNT <= 10,000 10,000 < REQUISITION_AMOUNT <= 15,000 10,000 < REQUISITION_AMOUNT <= 15,000 10,000 < REQUISITION_AMOUNT <= 15,000
Action(s)
Requires approval up to at least position 3 Requires approval up to at least position 2 Group approvals before the chain of approvers Group approvals after the chain of approvers
{Q: Are you setting up an Approval Group with Voting Regime=First Responder Wins?}A: Above shows the default setting when creating the rules. Any specific test that requires different setting will be mentioned in the test scenario below. Voting Regime=First Responder Wins is covered in ICXAMEXX02
Attributes Only the following Header Attributes will be tested: REQUISITION_TOTAL NON_DEFAULT_STARTING_POINT_POSITION_ID (By default, it is set to null) TOP_POSITION_ID (By default, it is set to null)
Only the following Line/Distribution Item Attribute will be tested: ITEM_CATEGORY PO_COST_CENTER
3/22/2013
Page 12 of 47
TEST OUTLINES
[Test Case ID: ICXAMEXX01] [Approving and Rejecting Requisition Recommendation]
Setups:
As defined above.
Test Objectives: To test HR Position approval flow To test HR Position Hierarchy approval flow To test Manage Approvals functionality To test Pre- and Post-Approvers Group To test Reassignment feature on Notification To test Requisition that does not require approvals To test Viewer Process Flow: Scenario A USER01 USER01 USER21 USER01 Scenario B USER01 USER01 USER01 USER21 USER01 USER01 USER01 USER01 USER10 USER11 USER25 USER24 USER11 USER25 USER26 USER25 USER01 Scenario C USER01 USER01 USER01 USER24 USER10 USER25 USER01 USER01 USER01 Scenario D USER01 USER01 USER28 USER30 USER01 USER21 USER22 USER01 USER23 USER29 3/22/2013
: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :
Create Requisition Approval List Verification; Submit for Approval Approve Requisition Approval Approval History Verification AME Setup Create Requisition Approval List Verification; Submit for Approval Reject Requisition Approval Approval History Verification AME Setup Purchasing Setup Approval List Verification; Re-submit for Approval Notification Verification Notification Verification Notification Verification Approve Requisition Approval Notification Verification Notification Verification Reject Requisition Approval Notification Verification Approval History Verification AME Setup Purchasing Setup Approval List Verification; Re-submit for Approval Approve Requisition Approval Approve Requisition Approval Approve Requisition Approval Approval History Verification AME Setup Purchasing Setup Create Requisition Approval List Verification; Submit for Approval Approve Requisition Approval Approve Requisition Approval Requisition Status Verification Approve Requisition Approval Reassign Requisition Approval Approval History Verification Approve Requisition Approval Approve Requisition Approval Oracle Confidential - For internal use only Page 13 of 47
USER01
: Approval History Verification
Test Outline: User Scenario A: To Test HR Position using Default Hierarchy definition USER01 Create Requisition Create Requisition REQ_A1 o o o USER01 REQUISITION_AMOUNT ITEM_CATEGORY PO_COST_CENTER = USD$4,000 = MISC.MISC = 01-740-7330-0000-00 New New Action Flow Type (New/Exist)
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Scenario Note: AME Approval Rule #1 is triggered using Position Hierarchy #1) GVT Verification: o Verify that Approver Icon is displayed in the box for Authority Approver USER21
USER21
REQ
TVT Verification:
Name USER21
USER01
Approval List Verification Navigate to Manage Approvals page Select Change Managerial Approver option o Verify that First Managerial Approver = USER21 Change Managerial Approver to USER24 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that Approver Icon is displayed in the box for Authority Approver USER21
USER24
New
REQ
TVT Verification:
Name USER24
USER01
Approval List Verification Navigate to Manage Approvals page Delete Authority Approver to USER24 (Note: When deleting the first approver which is previously changed, the approveral list will be reset.) At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER21
New
3/22/2013
Page 14 of 47
User
Action
Flow Type (New/Exist) TVT Verification:

Name USER21
USER01 USER21
Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_A1 for approval
New New
Approve Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification: o o Verify that Pending Icon is displayed in the box for Authority Approver USER21 Verify that the Graphical Display is above the Approval Sequence Table
USER21
REQ
At Approval Sequence Table, verify that the sequence is displayed as follows:

Num 1 2 3 Name USER01 USER01 USER21 Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted
USER01
Enter Note = USER21_Approved Approve Requisition REQ_A1 New Navigate to IProcurement Home Page, and search for requisition REQ_A1 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification: o o Verify that Approved Icon is displayed in the box for Authority Approver USER21 Verify that the Graphical Display is above the Approval Sequence Table
USER21 Approved
Approval History Verification
REQ

Num 1 2 3 Name USER01 USER01 USER21 Action Submitted Forwarded Approved Action Date <Date> <Date> <Date> USER21_Approved Note USER01_Submitted
Scenario B: 3/22/2013 Oracle Confidential - For internal use only Page 15 of 47
User
Action
Flow Type (New/Exist)
To Test HR Position Hierarchy when NON_DEFAULT_STARTING_POINT_POSITION_ID is not assigned USER01 USER01 AME Setup Set NON_DEFAULT_STARTING_POINT_POSITION_ID = NULL New = USD$3000 = CATHRC.CATHRC New Create Requisition REQ_A2 o o USER01 REQUISITION_AMOUNT ITEM_CATEGORY Create Requisition New
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2A is triggered using Position Hierarchy #1) GVT Verification: o Verify that Approver Icon is displayed in the box for Authority Approver USER21, USER22 and USER23
USER21 USER22 USER23
REQ
TVT Verification:
Name USER21 USER22 USER23
USER01 USER21
Enter Note to Buyer = USER01_Submitted1 Submit Requisition REQ_A2 for approval
New New
Reject Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification: o o Verify that Approver Icon is displayed in the box for Authority Approver USER21 Verify there is no Action Icon is displayed for Authority Approver USER22 and USER23
REQ

Num 1 2 3 4 5 Name USER01 USER01 USER21 USER22 USER23 Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted1
USER01 3/22/2013
Enter Note = USER21_Rejected1 Reject Requisition REQ_A2 New Page 16 of 47
Approval History Verification Oracle Confidential - For internal use only
User
Action Navigate to IProcurement Home Page, and search for requisition REQ_A2 in My Requisition table. o Verify that the status is Rejected Click on the status link to navigate to Approval History page GVT Verification: o Verify that Rejected Icon is displayed in the box for Authority Approver USER21
USER21 Rejected
REQ

Num 1 2 3 Name USER01 USER01 USER21 Action Submitted Forwarded Rejected Action Date <Date> <Date> <Date> USER21_Rejected1 Note USER01_Submitted1
USER01
AME Setup Set NON_DEFAULT_STARTING_POINT_POSITION_ID = <POSITION_ID> Note: Execute the following query to get the ID: SELECT POSITION_ID FROM PER_POSITIONS WHERE NAME = ENG490.ENGINEER '
New
USER01
{I would call this Profile Setup, rather than Purchasing Setup}. A: Will change
Purchasing Setup Set system profile POR : System Approvers are Mandatory = No Scenario Note: This means that generated authority approver(s) can be deleted.
USER01
Approval List Verification Navigate to IProcurement Home Page, and search for Requisition REQ_A2 Re-checkout Requisition REQ_A2 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2A is triggered using Position Hierarchy #2)
New
{Q: When the requester re-submits the req, why isnt the approval chain User 21 User 22 User 23?} A: Refer to AME Setup above, the starting point has been changed. Thus, the approval chain will change accordingly.
GVT Verification:
REQ USER24 USER25 USER26
TVT Verification:
USER01 3/22/2013
Approval List Verification Oracle Confidential - For internal use only
New Page 17 of 47
User
Action Navigate to Manage Approvals page Delete Authority Approver USER26 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER24 USER25
TVT Verification:
Name USER24 USER25
USER01
Approval List Verification Navigate to Manage Approvals page Add Ad-Hoc Viewer USER10 before Authority Approver USER24 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that Viewer Icon is displayed in the box for Ad-Hoc Viewer USER10
New
REQ
TVT Verification:
Name USER10 (Viewer) USER24 USER25
USER01
Approval List Verification Navigate to Manage Approvals page Add Ad-Hoc Approver USER11 after Authority Approver USER24 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER10 USER24 USER11 USER25
New
TVT Verification:
Name USER10 (Viewer) USER24 USER11 USER25
USER01
Approval List Verification Navigate to Manage Approvals page Select Change Managerial Approver option Oracle Confidential - For internal use only
New
3/22/2013
Page 18 of 47
User
Action o Verify that First Managerial Approver = USER24
{Q: I couldnt find Position Hierarchy #3 in the Setups. Can you show me where this is?} A: Will add Hierarchy #3
Change Managerial Approval to USER13 Verify that an error message is displayed (Note: USER13 belongs to Position Hierarchy #3, but there is only one level of position in this hierarchy. Thus, unable to complete the 2 levels of position which is required for this award recommendation.)
{Q: I couldnt find User #27 in the Setups. Can you show me where this is?} A: USER27 is just an employee in HR, refer to USER Setup
Change Managerial Approval to USER27 Verify that an error message is displayed (Note: USER27 is a employee in the Human Resources but there is no position associated with this user. Thus, unable to generate the position hierarchy.)
USER01
Change Managerial Approval to USER21 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: By changing first approver to USER24, Position Hierarchy #1 is used. The position of the Ad Hoc should remain the same.) GVT Verification:
REQ USER10 USER21 USER11 USER22 USER23
New
TVT Verification:
Name USER10 (Viewer) USER21 USER11 USER22 USER23
USER01
Approval List Verification Navigate to Manage Approvals page Delete Ad-Hoc Viewer USER10 o Verify that Viewer can be deleted At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
Name USER21 USER11 USER22 USER23
USER01 3/22/2013
Navigate to Manage Approvals page Oracle Confidential - For internal use only
New Page 19 of 47
User
Action Delete Authority Approver USER21 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
TVT Verification:
Name USER24 USER11 USER25 USER26
USER01
Navigate to Manage Approvals page Reset Approvers List At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
USER01
Approval List Verification Navigate to Manage Approvals page Add Ad-Hoc Viewer USER10 before Authority Approver USER24 Add Ad-Hoc Viewer USER11 before Authority Approver USER26
New
{Q: Not sure if I understand this step and the next. Why are you deleting User 25 as the authority approver and then adding him back as aViewer?} A: This is to ensure that the previously generated approver USER25 when added as Viewer will be treated as Viewer and not as authority approver
Delete Authority Approver USER25 Add Ad-Hoc Viewer USER25 after Authority Approver USER26 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that Viewer Icon is displayed in the box for Ad-Hoc Viewer USER10, USER11 and USER25
USER24 USER11 USER26 USER25
REQ USER10
TVT Verification:
Name
3/22/2013
Page 20 of 47
User
Action

USER10 (Viewer) USER24 USER11 (Viewer) USER26 USER25 (Viewer)
USER01 USER10
Enter Note to Buyer = USER01_Submitted2 Submit Requisition REQ_A2 for approval
New New
Notification Verification Navigate to Notification Summary page Verify that the FYI notification is found
{Q: Can we add here that they need to verify that they cannot approve the notification they should see an OK button on the notification} A: Will add
USER11 Notification Verification Navigate to Notification Summary page Verify that the FYI notification is not found New
{Q: Can you explain why these viewers do not get a notification? Im a little lost here.} A: This is because
USER24 has not responded. USER25 Notification Verification Navigate to Notification Summary page Verify that the FYI notification is not found New
{Q: Can you explain why these viewers do not get a notification? Im a little lost here.} A: As above
USER24 Approve Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification: o Verify that viewer information is not displayed
USER24 USER26 REQ
New

Num 1 2 3 4 5 6 7 Name USER01 USER01 USER21 USER01 USER01 USER24 USER26 Action Submitted Forwarded Rejected Submitted Forwarded Pending Action Date <Date> <Date> <Date> <Date> <Date> USER21_Rejected1 USER01_Submitted2 Note USER01_Submitted1
USER11 3/22/2013
Enter Note = USER24_Approved2 Approve Requisition REQ_A2 New Page 21 of 47
Notification Verification Oracle Confidential - For internal use only
User
Action Navigate to Notification Summary page Verify that the FYI notification is found
USER25
Notification Verification Navigate to Notification Summary page Verify that the FYI notification is not found Reject Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification: o o Verify that the USER24 is not displayed in the graphical sequence since s/he has already responded Verify that viewer information is not displayed
USER24 USER26
New
USER26
New
REQ

Num 1 2 3 4 5 6 7 Name USER01 USER01 USER21 USER01 USER01 USER24 USER26 Action Submitted Forwarded Rejected Submitted Forwarded Approved Pending Action Date <Date> <Date> <Date> <Date> <Date> <Date> USER24_Approved2 USER21_Rejected1 USER01_Submitted2 Note USER01_Submitted1
USER25
Enter Note = USER26_Rejected2 Reject Requisition REQ_A2 New
Notification Verification Navigate to Notification Summary page Verify that the FYI notification is found Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_A2 in My Requisition table. o Verify that the status is Rejected Click on the status link to navigate to Approval History page GVT Verification: o Verify that viewer information is not displayed
USER24 USER26 Rejected REQ
USER01
New

Num 1 2 3 4 Name USER01 USER01 USER21 USER01 Action Submitted Forwarded Rejected Submitted Action Date <Date> <Date> <Date> <Date> USER21_Rejected1 USER01_Submitted2 Note USER01_Submitted1
3/22/2013
Page 22 of 47
User
Action
5 6 USER01 USER10 Forwarded <Date> -
{We wont show viewers in the table}

Viewer
A: Will change
7 8 9 10 USER24 USER11 USER26 USER25 Viewer Rejected
Approved
<Date> <Date> -
USER24_Approved2
USER26_Rejected2
{We wont show viewers in the table}

Viewer
A: Will change Scenario C: To Test HR Position Hierarchy when NON_DEFAULT_STARTING_POINT_POSITION_ID and TOP_POSITION_ID are assigned USER01 AME Setup New
Set TOP_POSITION_ID = <POSITION_ID> Note: Execute the following query to get the ID: SELECT POSITION_ID FROM PER_POSITIONS WHERE NAME = 'IS110.INFORMATION SYSTEMS MANAGER '
USER01
Purchasing Setup Set system profile POR : System Approvers are Mandatory = Yes Scenario Note: This means that generated authority approver(s) cannot be deleted.
New
USER01
Approval List Verification Navigate to IProcurement Home Page, and search for Requisition REQ_A2 Re-checkout Requisition REQ_A2 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: Approval Rule #2A is triggered using Position Hierarchy #2. But since TOP_POSITION_ID is IS110.INFORMATION SYSTEMS MANAGER, only 2 (instead of 3) levels of position is required here.) GVT Verification:
REQ USER24 USER25
New
TVT Verification:
Name USER24 USER25
USER01 3/22/2013
Approval List Verification Oracle Confidential - For internal use only
New Page 23 of 47
User
Action Navigate to Manage Approvals page Delete Authority Approver USER24 o o Verify that an error message is displayed Verify that an error message is displayed Delete Authority Approver USER25
USER01
Approval List Verification Navigate to Manage Approvals page Add Ad-Hoc Approver USER11 after Authority Approver USER25 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
USER01
Navigate to Manage Approvals page Delete Ad-Hoc Approver USER11 o Verify that ad-hoc approver can be deleted At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER24 USER25
New
TVT Verification:
Name USER24 USER25
USER01
Navigate to Manage Approvals page Add Ad-Hoc Approver USER10 before Authority Approver USER25 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
USER01 3/22/2013
Enter Note to Buyer = USER01_Submitted3 Oracle Confidential - For internal use only
New Page 24 of 47
User
Action Submit Requisition REQ_A2 for approval
USER24
Approve Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification:
New

Num 1 2 3 4 5 6 Name USER01 USER01 USER21 USER01 USER01 USER10 Action Submitted Forwarded Rejected Submitted Forwarded Viewer A: Action Date <Date> <Date> <Date> <Date> <Date> USER21_Rejected1 USER01_Submitted2 Note USER01_Submitted1
Will change
7 8 9 10 USER24 USER11 USER26 USER25 Viewer Rejected
Approved
<Date> <Date> -
USER24_Approved2
USER26_Rejected2
Viewer A:
Will change
11 12 13 14 15 USER01 USER01 USER24 USER10 USER25 Submitted Forwarded Pending <Date> <Date> USER01_Submitted3
USER10
Enter Note = USER24_Approved3 Approve Requisition REQ_A2 New Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification:
Approve Requisition Approval

3/22/2013
Page 25 of 47
User
Action Will change

7 8 USER24 USER11 Approved Viewer A: <Date> USER24_Approved2
Will change
9 10 USER26 USER25 Rejected
<Date> -
USER26_Rejected2
Viewer A:
Will change
11 12 13 14 15 USER01 USER01 USER24 USER10 USER25 Submitted Forwarded Approved Pending <Date> <Date> <Date> USER24_Approved3 USER01_Submitted3
USER25
Enter Note = USER10_Approved3 Approve Requisition REQ_A2 New Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification:

Will change
7 8 USER24 USER11
Approved Viewer A:
<Date> -
USER24_Approved2
Will change
9 10 USER26 USER25 Rejected Viewer A: <Date> USER26_Rejected2
Will change
11 12 13 14 15 USER01 USER01 USER24 USER10 USER25
Submitted Forwarded Approved Approved Pending
<Date> <Date> <Date> <Date>
USER01_Submitted3
USER24_Approved3 USER10_Approved3
3/22/2013
Page 26 of 47
User
Action Enter Note = USER25_Approved3 Approve Requisition REQ_A2
USER01
Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_A2 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification:
REQ USER24 USER10 USER25 Approved
New

Will change
7 8 USER24 USER11 Approved Viewer A: <Date> USER24_Approved2
Will change
9 10 USER26 USER25 Rejected
<Date> -
USER26_Rejected2
Viewer A:
Will change
11 12 13 14 15 USER01 USER01 USER24 USER10 USER25 Submitted Forwarded Approved Approved Approved <Date> <Date> <Date> <Date> <Date> USER24_Approved3 USER10_Approved3 USER25_Approved3 USER01_Submitted3
USER01
AME Setup
New
USER01 Scenario D:
Set TOP_POSITION_ID = null New
Purchasing Setup Set system profile POR : System Approvers are Mandatory = No
To Test HR Position Hierarchy with Pre- and Post-Approvers Group; and Reassignment Flow USER01 Create Requisition USER01 Create Requisition REQ_A3 o REQUISITION_AMOUNT = USD$13,000 New New
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #3A, #3B and #3C are Oracle Confidential - For internal use only
3/22/2013
Page 27 of 47
User
Action triggered using Position Hierarchy #1) GVT Verification: o Verify that Approver Approval Group Icon is displayed in the box for Approver Approval Group QAApprovalGroup1 and QAApprovalGroup2 Verify that Approver Approval Icon is displayed in the box for Authority Approver USER28 and USER29
o o
{The Approval Groups should be hyperlinked in both the graphical and table formats} A:
Will change
QAAppro valGroup 1
REQ
USER21
USER22
QAApprova lGroup2
TVT Verification:
Name QAApprovalGroup1 USER21 USER22 QAApprovalGroup2
USER01 USER28
Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_A3 for approval
New New
Approve Requisition Approval Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: GVT Verification: o o Verify that the Approval Group are now broken to the members Verify that Approver Icon is displayed in the box for all Approvers
USER29

Num 1 2 3 4 5 6 7 Name USER01 USER01 USER28 USER30 USER21 USER22 USER29 Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted
USER30 3/22/2013
Enter Note = USER28_Approved Approve Requisition REQ_A3 New Navigate to Notification Summary page At Notification page, verify that the generated Approval List is as follows: Oracle Confidential - For internal use only Page 28 of 47
User
Action GVT Verification:


Num 1 2 3 4 5 6 7 Name USER01 USER01 USER28 USER30 USER21 USER22 USER29 Action Submitted Forwarded Approved Pending Action Date <Date> <Date> <Date> USER28_Approved Note USER01_Submitted
USER01
Enter Note = USER30_Approved Approve Requisition REQ_A3 New Navigate to IProcurement Home Page, and search for requisition REQ_A3 in My Requisition table. o Verify that the status is Pending New
Requisition Status Verification
USER21
Approve Requisition Approval Navigate to Notification Summary page Enter Note = USER21_Approved Approve Requisition REQ_A3
USER22
Reassign Requisition Approval Navigate to Notification Summary page Enter Note = USER22_Reassigned
New
{We should note that this is just for delegate, not transfer} A: Noted.
Reassign Requisition REQ_A3 to USER23 New Navigate to IProcurement Home Page, and search for requisition REQ_A3 in My Requisition table. o Verify that the status is Pending Click on the status link to navigate to Approval History page GVT Verification: o o o o o Verify that the original Approver USER22 is now reassigned to USER23 Verify that Approver Group Icon is displayed in the box for Approver Group QAApprovalGroup1 and QAApprovalGroup2 Verify that Approver Icon is displayed in the box for Authority Approver USER28 and USER29 Verify that Approved Icon is displayed for QAApprovalGroup1, USER21 and USER23 Verify that Pending Icon is displayed for QAApprovalGroup2
QAApprov alGroup1 QAApproval Group2
USER01
REQ
USER21
USER23
3/22/2013
At Approval Sequence Table, verify that the sequence is displayed as Oracle Confidential - For internal use only Page 29 of 47
User
Action follows:
Num 1 2 3 4 5 6 Name USER01 USER01 USER28 USER30 USER21 USER22 Action Submitted Forwarded Approved Approved Approved Reassigned Forwarded Action Date <Date> <Date> <Date> <Date> <Date> <Dated> USER28_Approved USER30_Approved USER21_Approved USER22_Reassigned Forwarded {Im pretty sure this says Forwarded} Note USER01_Submitted
A: Will change
7 8 USER23 USER29 Pending
A: Will change
USER23
REQ USER23 USER29
New

Num 1 2 3 4 5 6 Name USER01 USER01 USER28 USER30 USER21 USER22 Action Submitted Forwarded Approved Approved Approved Reassigned Forwarded Action Date <Date> <Date> <Date> <Date> <Date> <Dated> USER28_Approved USER30_Approved USER21_Approved USER22_Reassigned Forwarded A: Will Note USER01_Submitted
A: Will change
7 8 USER23 USER29 Pending
change
USER29 USER01
Enter Note = USER23_Approved Approve Requisition REQ_A3 New Navigate to Notification Summary page Enter Note = USER29_Approved Approve Requisition REQ_A3 New Navigate to IProcurement Home Page, and search for requisition REQ_A3 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification:
3/22/2013
Page 30 of 47
User
Action
QAApprov QAApprov REQ USER21 USER23 alGroup1 alGroup2

Approved

Num 1 2 3 4 5 6 Name USER01 USER01 USER28 USER30 USER21 USER22 Action Submitted Forwarded Approved Approved Approved Reassigned Forwarded Action Date <Date> <Date> <Date> <Date> <Date> <Dated> USER28_Approved USER30_Approved USER21_Approved USER22_Reassigned Forwarded A: Will Note USER01_Submitted
A: Will change
6 7 USER23 USER29
change
<Date> <Date> USER23_Approved USER29_Approved
Approved Approved
End of Test Script
3/22/2013
Page 31 of 47
[Test Case ID: ICXAMEXX02] [Approval Parallelism and Voting Regime]

Setups:
As defined above.
Test Objectives: To test when Voting Regime is set to Consensus To test when Voting Regime is set to First Responder Wins To test Request Information on Notification To test Viewer Process Flow: Scenario A USER01 USER01 USER01 USER22 USER10 USER11 USER23 USER10 USER01 USER22 USER11 USER22 USER01 Scenario B USER01 USER01 USER01 USER21 USER22 USER23 USER01 USER21 USER22 USER01 Scenario C USER01 USER01 USER01 USER22 USER23 USER28 USER01 USER28 USER21 USER22 USER01 USER22 USER23 USER01 USER30 USER01 USER01 Test Outline: User
: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :
AME Setup Create Requisition Approval List Verification; Submit for Approval Notification Verification Notification Verification Notification Verification Approve Requisition Approval Approve Requisition Approval Approval History Verification Notification Verification Approve Requisition Approval Approve Requisition Approval Approval History Verification AME Setup Create Requisition Approval List Verification; Submit for Approval Notification Verification Notification Verification Approve Requisition Approval Approval History Verification Reject Requisition Approval (Email) Reject Requisition Approval (Email) Approval History Verification AME Setup Create Requisition Approval List Verification; Submit for Approval Notification Verification Notification Verification Request Information on Requisition Approval Submit Information on Requisition Approval Approve Requisition Approval Approve Requisition Approval Request Information on Requisition Approval Submit Information on Requisition Approval Approve Requisition Approval Approve Requisition Approval Approval History Verification Approve Requisition Approval Approval History Verification AME Setup
Action
Scenario A: To Test when Voting Regime=Consensus 3/22/2013 Oracle Confidential - For internal use only Page 32 of 47
User USER01
Action AME Setup
Flow Type (New/Exist) New
For Action Approval Group (?) HR Position Hierarchy, set Voting Regime=Consensus{NOTE: When you have an approval group in your rule, during req checkout you will not see the individuals unless the requester clicks on the hyperlink. So the graphical display should be: o Req Approval Group
A: Will change Approval Group to Action Group to minimize confusion. This is in accordance to AME. USER01 Create Requisition Create Requisition REQ_B1 o REQUISITION_AMOUNT o o USER01 ITEM_CATEGORY PO_COST_CENTER New = USD$3,000 = CATHRC.CATHRC = 01-520-7530-0000-00 New
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2A is triggered using Position Hierarchy #1) GVT Verification: o Verify that Approver Icon is displayed in the box for all Approvers {See note above}
REQ
TVT Verification:
Name USER21; USER22; USER23
USER01
Navigate to Manage Approvals page Delete Authority Approver USER22 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: {Note: If this is a group, you cannot delete one member of the group. You can only delete the entire group. Can you confirm please. } A: Not an approval group. GVT Verification:
REQ USER21 USER23
New
TVT Verification:
Name USER21; USER23
USER01
Navigate to Manage Approvals page Delete Authority Approver USER23 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER21
New
3/22/2013
Page 33 of 47
User
Action TVT Verification:

Name USER21
USER01
Navigate to Manage Approvals page Delete Authority Approver USER21 o Verify that USER21 cannot be deleted since s/he is the last approver Reset Approval List At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
USER01
Navigate to Manage Approvals page Delete Authority Approver USER21 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER22 USER23
New
TVT Verification:
Name USER22; USER23
USER01
Navigate to Manage Approvals page Add Ad-Hoc Approver USER10 after USER23 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
New
TVT Verification:
Name USER22; USER23 USER10
USER01
Navigate to Manage Approvals page Add Ad-Hoc Approver USER11 before USER22 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification:
REQ USER11 USER22
New
3/22/2013
Page 34 of 47
User
Action
USER23 USER10
TVT Verification:
Name USER11; USER23 USER22; USER10
USER01 USER22
Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_B1 for approval
New New
Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found Notification Verification Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o o o Verify that the parallel approval thread is not displayed Verify that Pending Icon is displayed in the box for USER22 Verify that no Action Icon is displayed in the box for USER11
USER11 USER22
USER10
New
USER11
New
REQ

Num 1 2 3 4 Name USER01 USER01 USER11 USER22 Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted
USER23
Approve Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o o o Verify that the parallel approval thread is not displayed Verify that Pending Icon is displayed in the box for USER23 Verify that no Action Icon is displayed in the box for USER10
USER23 USER10
New
REQ

3/22/2013
Page 35 of 47
User
Action Enter Note = USER23_Approved Approve Requisition REQ_B1
USER10
Approve Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o o Verify that the parallel approval thread is not displayed Verify that Pending Icon is displayed in the box for USER10
USER10
New
REQ

Num 1 2 3 4 Name USER01 USER01 USER23 USER10 Action Submitted Forwarded Approved Pending Action Date <Date> <Date> <Date> USER23_Approved Note USER01_Submitted
USER01
Enter Note = USER10_Approved Approve Requisition REQ_B1 New
Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B1 in My Requisition table. o Verify that the status is Pending Click on the status link to navigate to Approval History page GVT Verification: o o o Verify that Approved Icon is displayed in the box for USER23 and USER10 Verify that Pending Icon is displayed in the box for USER11 Verify that no Action icon is displayed in the box for USER22
USER11 USER23 USER22 USER10
REQ

Num 1 2 3 4 5 6 Name USER01 USER01 USER11 USER22 USER23 USER10 Approved Approved <Date> <Date> USER23_Approved USER10_Approved Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted
USER22
Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found Approve Requisition Approval Navigate to Notification Summary page Enter Note = USER11_Approved Oracle Confidential - For internal use only
New
USER11
New
3/22/2013
Page 36 of 47
User
Action Approve Requisition REQ_B1
USER22
Approve Requisition Approval Navigate to Notification Summary page Enter Note = USER22_Approved Approve Requisition REQ_B1
USER01
Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B1 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification:
REQ USER11 USER23 USER22 USER10 Approved
New

Num 1 2 3 4 5 6 Name USER01 USER01 USER11 USER23 USER10 USER22 Action Submitted Forwarded Approved Approved Approved Approved Action Date <Date> <Date> <Date> <Date> <Date> <Date> USER11_Approved USER23_Approved USER10_Approved USER22_Approved Note USER01_Submitted
Scenario B: To Test when Voting Regime=First Responder Wins USER01 AME Setup For Action Approval Group HR Position Hierarchy, set Voting Regime=First Responder Wins Create Requisition Create Requisition REQ_B2 o REQUISITION_AMOUNT o o USER01 ITEM_CATEGORY PO_COST_CENTER New
USER01
New = USD$3,000 = CATHRC.CATHRC = 01-520-7530-0000-00 New
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2A is triggered using Position Hierarchy #1) GVT Verification:
TVT Verification:
USER01 USER21 3/22/2013
New New Page 37 of 47
Notification Verification Oracle Confidential - For internal use only
User
Action Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that parallel approval threads are not displayed
REQ USER21

Num 1 2 3 4 5 Name USER01 USER01 USER21 USER22 USER23 Action Submitted Forwarded Pending Pending Pending Action Date <Date> <Date> Note USER01_Submitted
USER22
Notification Verification Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that parallel approval threads are not displayed
REQ USER22
New

USER23
Approve Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that parallel approval threads are not displayed
REQ USER23
New

USER01 3/22/2013
Enter Note = USER23_Approved Approve Requisition REQ_B2 New Page 38 of 47
Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B2 Oracle Confidential - For internal use only
User
Action in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification: o Verify that parallel approvers who have not responded will not be displayed
REQ USER23 Approved

USER21
Reject Requisition Approval (Email) Navigate to Approval Required Email Enter Note = USER21_Rejected Reject Requisition REQ_B2 Reject Requisition Approval (Email) Navigate to Approval Required Email Enter Note = USER22_Rejected Reject Requisition REQ_B2 Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B2 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification: o Verify that parallel approvers USER21 and USER22 who responded later will not be recorded
REQ USER23 Approved
New
USER22
New
USER01
New

Scenario C: To Test when Voting Regime=Serial with Action Group order number not unique USER01 AME Setup For Action Approval Group HR Position Hierarchy, set Voting Regime=Serial; Order Number=Not unique, 1 For Action Approval Group Approval Group, set Voting Regime=Serial; Order Number=Not unique, 1 Create Requisition Create Requisition REQ_B3 o REQUISITION_AMOUNT Approval List Verification 3/22/2013 At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2B and #2C are triggered) Oracle Confidential - For internal use only Page 39 of 47 New
USER01
New = USD$7,000 New
USER01
User
Action GVT Verification: {Groups are hyperlinked in both the graphical and table formats} A: Will change
REQ QAApprov alGroup1 USER21 USER22 USER23
TVT Verification:
Name QAApprovalGroup1; USER21; USER22 USER23
USER01 USER22
New New
Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found {Q: Do we need to test these steps?} A: Yes Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found {Q: Do we need to test these steps?} A: Yes Request Information on Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that the parallel approval thread is not displayed
USER30 REQ USER28
USER23
New
USER28
New
{In the setup, you have in your rule 2B that the Voting Regime = Consensus, but in this case, the Voting Regime you are testing is Serial. Im a little confused.} A: Refer to the AME Setup above At Approval Sequence Table, verify that the sequence is displayed as follows:
USER01
Enter Note = USER28_Request Request Information on Requisition REQ_B3 New
Submit Information on Requisition Approval Navigate to Notification Summary page Verify that the Information Required notification is not found Enter Note = USER01_SubmitInfo Submit Information on Requisition REQ_B3 Approve Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that the parallel approval thread is not displayed Oracle Confidential - For internal use only
USER28
New
3/22/2013
Page 40 of 47
User
Action
REQ USER28 USER30

Num 1 2 3 4 Name USER01 USER01 USER28 USER01 Action Submitted Forwarded Request Information Submit Information This action is called something else we need to ask David. Action Date <Date> <Date> <Date> <Date> USER28_Request USER01_SubmitInfo Note USER01_Submitted
A: OK
5 6 USER28 USER30
Pending
USER21
Approve Requisition Approval Navigate to Notification Summary page At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: GVT Verification: o Verify that the parallel approval thread is not displayed
USER21 USER22 USER23 REQ

Num 1 2 3 4 5 Name USER01 USER01 USER21 USER22 USER23 Action Submitted Forwarded Pending Action Date <Date> <Date> Note USER01_Submitted
USER22
Request Information on Requisition Approval Navigate to Notification Summary page Enter Note = USER22_Request Request Information on Requisition REQ_B3 Submit Information on Requisition Approval Navigate to Notification Summary page Verify that the Information Required notification is not found Enter Note = USER01_SubmitInfo Submit Information on Requisition REQ_B3 Approve Requisition Approval Navigate to Notification Summary page Enter Note = USER22_Approved Approve Requisition REQ_B3 Oracle Confidential - For internal use only
USER22
New
USER22
New
3/22/2013
Page 41 of 47
User USER23
Action Approved Requisition Approval Navigate to Notification Summary page Enter Note = USER23_Approved Approve Requisition REQ_B3 Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B3 in My Requisition table. o Verify that the status is Pending Click on the status link to navigate to Approval History page GVT Verification: o o Verify that Pending Icon is displayed in the box for QAApprovalGroup1 Verify that Approved Icon is displayed in the box for USER21, USER22 and USER23
QAApprova lGroup1 USER21 USER22 USER23
USER01
New
REQ

Num 1 1 2 2 3 3 4 4 5 5 6 6 7 3 8 4 9 7 10 8 11 9 Name USER01 USER01 USER28 USER01 USER28 USER21 USER22 USER01 USER22 USER23 USER30 Action Submitted Forwarded Request Information Submit Information Approved Approved Request Information Submit Information Approved Approved Pending Action Date <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> USER28_Request USER01_SubmitInfo USER28_Approved USER21_Approved USER22_Request USER01_SubmitInfo USER22_Approved USER23_Approved Note USER01_Submitted
USER30
Approve Requisition Approval Navigate to Notification Summary page Enter Note = USER30_Approved Approve Requisition REQ_B3 Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_B3 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification: o Verify that Approved Icon is displayed in the box for all Approvers Oracle Confidential - For internal use only
New
USER01
New
3/22/2013
Page 42 of 47
User
Action
REQ QAApprov alGroup1 USER21 USER22 USER23 Approved

Num 1 1 2 2 3 3 4 4 5 5 6 6 7 3 8 4 9 7 10 8 11 9 Name USER01 USER01 USER28 USER01 USER28 USER21 USER22 USER01 USER22 USER23 USER30 Action Submitted Forwarded Request Information Submit Information Approved Approved Request Information Submit Information Approved Approved Approved Action Date <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> <Date> USER28_Request USER01_SubmitInfo USER28_Approved USER21_Approved USER22_Request USER01_SubmitInfo USER22_Approved USER23_Approved USER30_Approved Note USER01_Submitted
USER01
AME Setup For Action Approval Group HR Position Hierarchy, set Voting Regime=Serial End of Test Script
New
3/22/2013
Page 43 of 47
[Test Case ID: ICXAMEXX03] [No Approvals and OAM Error]

Setups:
As defined above.
Test Objectives: To test Requisition that does not require approvals To test when approval list cannot be completed Process Flow: Scenario A: USER01 USER01 USER01 Scenario B: USER01 USER01 USER01 USER21 USER22 USER01 Test Outline: User Scenario A: To Test when No Approvals are required USER01 Create Requisition USER01 Create Requisition REQ_C1 o REQUISITION_AMOUNT = USD$500 New New
: Create Requisition : Approval List Verification; Submit : Approval History Verification : : : : : : Create Requisition Approval List Verification; Submit Human Resource Setup Approve Requisition Approval Notification Verification Approval History Verification
Action
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Scenario Note: AME Approval Rule #0 is triggered.) GVT Verification:
REQ No Approvals Required
TVT Verification:
Name No Approvals Required
USER01
Navigate to Manage Approvals page Select Delete Approver/Viewer o Verify that no list is generated for deletion Navigate back to Checkout: Approvals and Notes page Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_C1
New
USER01 USER01
New New
Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_C1 in My Requisition table. o Verify that the status is Approved Click on the status link to navigate to Approval History page GVT Verification:
3/22/2013
Page 44 of 47
User
Action o
REQ No Approvals Required

Num 1 2 Name USER01 USER01 Action Submitted Approved Action Date <Date> <Date> Note USER01_Submitted
Scenario B: To Test Approval Flow with no employee assigned to the position (OAM Error) USER01 Create Requisition Create Requisition REQ_C2 o o USER01 REQUISITION_AMOUNT ITEM_CATEGORY = USD$3,000 = CATHRC.CATHRC New New
Approval List Verification At Checkout: Approvals and Notes page, verify that the generated Approval List is as follows: (Note: AME Approval Rule #2A is triggered using Position Hierarchy #1) GVT Verification:
TVT Verification:
USER01 USER01
Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_C2 for approval Navigate to Human Resources, Vision Operations Remove the position (PDR810.PRODUCTION DIRECTOR) from USER22
New
Human Resource Setup
USER21
New

3/22/2013
Page 45 of 47
User
Action
5 USER23
USER22
Enter Note = USER21_Approved2 Approve Requisition REQ_C2 New
Notification Verification Navigate to Notification Summary page Verify that the Approval Required notification is not found Scenario Note: By removing USER22 from the position PDR810.PRODUCTION DIRECTOR, there is no one associated with this position. Thus, the approval list is not able to be completed. Approval History Verification Navigate to IProcurement Home Page, and search for requisition REQ_C2 in My Requisition table. o Verify that the status is Incomplete Click on the status link to navigate to Approval History page GVT Verification: o Verify that viewer information is not displayed
USER21 TBD REQ
USER01
New
{Is TBD a question you have?} A: Will replace with Approval List could not be generated. At Approval Sequence Table, verify that the sequence is displayed as follows:
USER01
Human Resource Setup Navigate to Human Resources, Vision Operations Assign the position (PDR810.PRODUCTION DIRECTOR) to USER22
End of Test Script
3/22/2013
Page 46 of 47
4.
EFFORT ESTIMATES
* Indicate Effort Required in man-days * Test Case Priority: H Must be executed successfully for the completion of System Test. The test must be run every time a test environment is made available to QA (certification, xbuild, etc). in every round of testing. The test case is a primary candidate to be automated. M Must be executed at least once in System Test, Certification, and Release Testing. The test case is also a candidate to be automated. L The test case is low priority. The test case must be executed at least once during a release. The test case is not a candidate to be automated.
Test Case
Test Case
Priorit y (H,M, L)
Effort Required for Test Script Writin g (days )
Effort Required for Manu al Execu tion (days)
Effort Required for Auto mated Script s Creati on / Updat e (days)
Setup Updates Existing Test Cases ICXAMEXX01 ICXAMEXX02 ICXAMEXX03 Total Effort Estimate
1.5 1.5 0.5 3.5
1 1 0.5 2.5
3 3 1 7
3/22/2013
Page 47 of 47

AME Pahse2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AME Pahse2

Uploaded by

Copyright:

Available Formats

TEST OUTLINE

AME Phase II Test Outline

Oracle Confidential - For internal use only Page 2 of 47

AME Phase II Test Outline

Oracle Confidential - For internal use only Page 3 of 47

AME Phase II Test Outline

Oracle Confidential - For internal use only

AME Phase II Test Outline

Oracle Confidential - For internal use only

AME Phase II Test Outline

Oracle Confidential - For internal use only

AME Phase II Test Outline

1.2 Tests Cases not Included

User Interface (UI) Representation

{Q: Are you including the icons next to the

bullet points?} A: I will take the icons from the UIX.

including the icons next to the bullet points?}

{Q: Are you

Oracle Confidential - For internal use only

AME Phase II Test Outline

Rejected Status Icon Request Information Status Icon

Oracle Confidential - For internal use only

AME Phase II Test Outline

Indicates that user has access to negotiations created in listed OU

{Q: Why negotiations?} A: Will be removed

negotiations?} A: Will be removed

negotiations?} A: Will be removed

iProcurement Approval Management Application Administrator

Oracle Confidential - For internal use only

AME Phase II Test Outline

Oracle Confidential - For internal use only

AME Phase II Test Outline

PDR810.PRODUCTION DIRECTOR USER23, USER30

AME Rule Definition

Chain-ofAuthority Ordering Mode

Action(s) Require approvals up to at least level 1.

1,000 < REQUISITION_AMOUNT <= 5,000 ITEM_CATEGORY=MISC.MISC PO_COST_CENTER=01-740-7330-0000-00

{Q: HR Level or Position?} A: Description as per AME

0 < REQUISITION_AMOUNT <= 5,000 ITEM_CATEGORY=CATHRC.CATHRC

Approval Group (QAApprovalGroup1)

5,000 < REQUISITION_AMOUNT <= 10,000

Chains of authority includes an approval group

Oracle Confidential - For internal use only

AME Phase II Test Outline

AME Action Definition Order Number Rule Name

AME Rule Definition

Chain-ofAuthority Ordering Mode

Oracle Confidential - For internal use only

AME Phase II Test Outline

AME Phase II Test Outline

: Approval History Verification

Oracle Confidential - For internal use only

AME Phase II Test Outline

Flow Type (New/Exist) TVT Verification:

Enter Note to Buyer = USER01_Submitted Submit Requisition REQ_A1 for approval

At Approval Sequence Table, verify that the sequence is displayed as follows:

Approval History Verification

At Approval Sequence Table, verify that the sequence is displayed as follows:

Scenario B: 3/22/2013 Oracle Confidential - For internal use only Page 15 of 47

AME Phase II Test Outline

Flow Type (New/Exist)

Enter Note to Buyer = USER01_Submitted1 Submit Requisition REQ_A2 for approval

At Approval Sequence Table, verify that the sequence is displayed as follows: