Create WIP Adjustment Transfer does not generate information about each transaction that was not successfully transferred

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Create WIP Adjustment to Transfer to another project/task, does not generate information about each transaction that was not successfully transferred. When processing a few records, this may not matter, but when processing larger amounts of records, it may be confusing to the end user because they may not realize that some of the transactions were not processed as they expected.

Steps to Reproduce:

1. Create a new Project, "Project 1".
2. Create a task "Project 1 Task" and assign "Resource 1" to the task
3. Financially enable this project, associating a Rate Matrix that will have a valid Matrix Row for this project's transactions logged for "Resource 1"
   Admin Tool, Manage Matrix, "My Cost/Rate Matrix"
   Columns = Project, Resource
   Must have a valid Matrix Row for "Project 1", "Resource 1", with rates and costs for the appropriate date range to include the date for the transaction entered in the next step.
4. Create any type of financial transaction for "Project 1" , "Project 1 Task", "Resource 1" on May 1, 2016 and post the transaction to WIP
5. Create a second new Project, "Project 2"
6. Create a task "Project 2 Task" and assign "Resource 2" to the task
7. Financially enable this project, associating a Rate Matrix that will NOT have a valid Matrix Row for this project's transactions logged for any resources
   Admin Tool > Manage Matrix, "My Cost/Rate Matrix"
   Columns = Project, Resource
   Must **NOT** have a valid Matrix Row for "Project 2", "Resource 2", with rates and costs for the appropriate date range to include the date for the transaction entered in step 4.
   (do not have a matrix row that will apply to 'All' transactions)
8. Go to 'Create WIP Adjustment Page'
9. Filter for the following criteria (note: it is important to filter on the project)
   From Date : 5/1/16
   To Date: = 5/1/16
   Project id = "Project 1"
   Resource ID = "Resource 1"
   Click 'Filter' button
   Expected to see the transaction created in step 4
10. Select the checkbox next to this transaction, Click 'Transfer' button
11. Three 'required' fields appear: enter the following information
    Project Id = "Project 2"
    Task Id = "Project 2 Task"
    Resource Id = "Resource 2"
    select the checkbox for the option to "Calculate New Rate(s)"
12. Click 'Submit' button
    Expected : Transfer Transactions listing page showing the transaction details and a message "Transfer Unsuccessful - No Rate Found" for each unsuccessful transaction transfer attempt where the rate is not found.
    Actual : Transfer Transactions listing page - "No results found."

When a transfer is unsuccessful, the transaction will remain in the "Create WIP Adjustment" listing as expected. If the end-user has a filter set of only a few transactions, the unsuccessful transfer is evident immediately upon returning to the "Create WIP Adjustment" page because the transaction does not disappear from this view and move to the "Approve WIP Adjustment" page. This becomes an issue when the end-user is processing a larger number of records ; the end-user may not realize that some transactions were not processed as expected. Listing the "Transfer Unsuccessful" transactions on the Transfer Transactions listing page helps the customer to manage their WIP Adjustments more effectively. Indicating a message of an unsuccessful transfer also assists the end-user in determining why the transfer action is unsuccessful.

 

Environment

Release: Clarity 16.1.2, 16.1.3, 16.2.2, 16.2.3, 16.3.0

Resolution

• Transfer only a few transactions at one time.
• Keep track of the number of records in the result set on the "Create WIP Adjustment" page.
• Keep track of the number of records selected for the "Transfer" process.
• Keep track of the number of "Transfer Successful" result set.
• Compare the result sets and attempt the transfer again on transactions that remain in the "Create WIP Adjustment" listing page.
• Because the end-user will not know the cause of the unsuccessful transfer, future attempts to transfer this transaction as described in this case scenario will not be successful and the end-user will not know what configuration is required to resolve the issue.