FF.004.1 Perform AM Interface Processing (Project Archive)
User Acceptance Test Overview
The Asset Management module provides a centralized repository of asset data, allowing colleges to add, transfer, manage depreciation, retire assets and this module integrates with another PeopleSoft module, Purchasing, to seamlessly account for newly acquired assets. Now that you are viewing this first steps in the high level (Tier 1) flow [FF.004 - Asset Management to GL, you will have noted that this test set allows testers to start in 2 distinct places. This first step FF.004.1 - Perform AM Interface focuses on bringing data from the Purchasing module to establish an asset. You may choose to start here, at FF.004.2 - Review/Create Asset. Both start locations on the high level flow must be tested to complete the UAT test set.
The guide below [FF.004.1] contains a business process flow diagram outlining the steps [FF.004.1.1 through FF.004.1.4] needed to complete the test activities. The steps to Consolidate Assets [FF.004.1.3] and Unitize Assets [FF.004.1.4 ] are shown as optional, but are list as such to denote that they are an alternate way to process through this flow. There are three paths that must be tested through this Tier 2 flow diagram.
For example:
Test Path 1: Execute the steps FF.004.1.1 and FF.004.1.2 as the first test path.
Test Path 2: Execute the steps FF.004.1.1, FF.004.1.3 and FF.004.1.2 as the second test path.
The information in this set of test materials 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, for example, in order to fully test Asset Management integration to Purchasing, you will likely need to establish data in that upstream test to fully test Asset Management. Depending on how your institution is organized, coordination with other colleagues in advance of commencing testing is key to success as you will want to plan who needs to be involved in executing these test steps to accurately represent who will do this work once on PeopleSoft tomorrow. In the same way that it doesn't take a single individual to operate the business of running a college it will require coordination across departments to successfully test a business flow from beginning to end.
Self-Paced Training Materials (Advanced Prep)
To prepare yourself in advance for the richest testing experience below are required Canvas Courses. Successful course completion is a prerequisite to participate in all UAT activities.
- AM100 Asset Management
To register for these required courses visit the ctcLink Training Registration Page.
Additional Resources
Instructor-Led Training Materials and Recordings
Instructor-Led Training Materials
Training Session Recordings
Links to Quick Reference Guides - Steps in the Test Process
Minimum Test Case (Data) Scenarios:
Scenarios for FF.004.1.1 - Retrieve Info from AP/PO
- Create an asset with the Interface Accounts Payable (AP)/ Purchase Order (PO) to Asset Management.
- Change the Dept when interfacing with AP/PO.
- Create a CIP (Consolidated) asset.
- Create a CIP (Consolidated) asset that crosses fiscal years.
- Create an asset with multiple Funds.
Scenarios for FF.004.1.2 - Load into Asset Management
- Unitize POs with quantity greater than 1 [Qty > 1] into separate assets.
Recommended Error Test Conditions:
FF.004.1.2 - Load into Asset Management (AM):
-
Error Condition: Load an Asset with Incorrect Department or Fund from Requisition.
- Note: In FF.001.1 - Requisition Processing/Review (Part of FF.001 - Procure to Pay to GL): Create a requisition with invalid information (e.g. wrong department or wrong fund) and test to understand behavior in Asset Management when any part of the asset information does not come across correctly.
- Expected Behavior: Asset will load. (See error condition/expected behavior in Step 004.2.1 for handling.)
-
Error Condition: Load an Asset with Incorrect Department or Fund from Purchase Order.
- Note: In FF.001.2 - Purchase Order Processing/Review (Part of FF.001 - Procure to Pay to GL): Create a Purchase Order with invalid information (e.g. wrong department or wrong fund) and test to understand behavior in Asset Management when any part of the asset information does not come across correctly.
- Expected Behavior:Asset will load. (See error condition/expected behavior in Step 004.2.1 for handling.)
FF.004.1.3 - Consolidate Assets:
-
Error Condition: Choose the wrong profile, essentially any profile other than Construction in Progress (CIP - 0200) when consolidating an asset.
- Expected Behavior: CIP asset does not reflect correctly, or depreciate.
-
Error Condition: Choose the wrong profile, any profile not associated with Small and Attractive Assets (ends in SA), when consolidating an asset.
- Expected Behavior: Small and Attractive assets will depreciate when they should not.
The High Level UAT Framework:
Next Step in the High Level UAT Framework:
Links to User Acceptance Test 'How To' and UAT Environment URL Information:
Security Matrix Mapping Information
The information below provides those completing the Security Matrix Mapping templates with the Menus, Pages and Role names needed to execute the User Acceptance Testing relevant to this UAT guide.
FF.004.1.1 - Retrieve Info from AP/PO:
MENU: Asset Management > Send/Receive Information > Preview AP/PO Information
ROLE NAME: ZZ AM Interface Processing, ZZ Receipt Entry and ZZ Voucher Processing
FF.004.1.2 - Load into Asset Management (AM):
MENU: Asset Management >Send/Receive Information > Interface Transactions > Review
MENU: Asset Management > Send/Receive Information > Interface Transactions > Load into AM
ROLENAME: ZZ AM Interface Processing
FF.004.1.3 - Consolidate Assets:
MENU: Asset Management > Send/Receive Information > Interface Transactions > Consolidate
ROLENAME: ZZ AM Interface Processing
FF.004.1.4 - Unitize Assets:
MENU: Asset Management > Send/Receive Information > Interface Transactions > Unitize
ROLENAME: ZZ AM Interface Processing
0 Comments
Add your comment