Clarity - Reversal of Transactions
search cancel

Clarity - Reversal of Transactions

book

Article ID: 145485

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

There are two types of voucher entries that can be done. Labour and Expense. Each of these entries will create transactions that can then be used to populate "Actuals" in Team/Task and "Actual Cost" in Financial Plans. A need can arise to delete incorrectly entered voucher entries. This process is called "WIP Adjustment" in Clarity, and it results in reversal of transactions.

But the way the application handles each of these voucher entry types is different. Reversal of Expense and Labour transactions work differently.

Example of how it works for labour:

  1. Quantity1 - 9th Aug - same resource = 100
  2. Quantity2 - 9th Aug - same resource = -100
  3. Reverse both transactions (Create and Approve WIP Adjustments)
  4. Run "Import Financial Actuals" job
  5. Result: Actuals in project  = 0

Example of how it works for Expense:

  1. Quantity1 - 9th Aug - same resource = 100
  2. Quantity2 - 9th Aug - same resource = -100
  3. Reverse both transactions
  4. Run "Import Financial Actuals" job
  5. Result: Actuals in project = 100 (derived from reversal of negative transaction)

Resolution

Fix for both labour and expense:

  1. Put in a negative transaction to cancel out the actuals already in place
    • Quantity3 - 9th Aug - same resource = -100 (Do not reverse!)
  2. Import Financial Actuals.

For labour resources:

  • Negative transactions can be reversed

For expense resources:

  • Negative transactions cannot be reversed

Incorrectly entered positive actuals can be reversed by just putting in negative actuals. When transactions are in status = 0, quantities cancel out without any issues.

Additional Information

Simple query for DB, with only required columns for these cases.

select pw.transdate, pw.status, pw.quantity,
pw.project_code, pw.resource_code, pw.lastupdatedate
from ppa_wip pw
order by lastupdatedate desc
;