- wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
- xogBatchSize: The XOG batch size. This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
- username: The resource name that the process uses for uploading data. The default is set to admin.
- It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
- Notes field should not be modified in Script nor should be worked upon by any other process.
- All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
-
This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched. For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below: -
A process creating a new Cost Plan. Cost Plan properties:
Pre-conditions:Name Cost Plan created on: yyyy/mm/dd hh:mm:ss Grouping attributes Charge Code, Transaction Type Start Period The earliest fiscal period with Actuals (from PPA_WIP table) or current period, if there are no actuals Finish Period The latest fiscal period with a non-zero allocation (from PRJ_BLB_SLICES table, SLICE_REQUEST_ID = 6 Period Type Monthly Plan of Record True Planned Cost For periods in the past – from Actuals (Charge Code, Transaction Type, Quantity (Units), Cost (Amount) taken from Transactions (PPA_WIP & PPA_WIP_DETAILS); For current and future periods – from Allocations (Charge Code taken from the Project, Transaction Class from the Resource, Quantity from allocation slices, Cost from the Rate Matrix (NBI_PROJ_RES_RATES_AND_COSTS table) - the Project must be financially enabled.
- if a new Team Member is added, Rate Matrix job must be run, so the rates are populated in the NBI table.
- if the Allocation changes, allow the timeslice job to finish before running the process.
- the Project should have the Charge Code set.
-
This portlet shows the project costs by Month. The information displayed includes:- Start Date for project
- End Date for project
- Budgeted Cost
- Planned Cost
- Actual Hours
-
This training document is a Rego Consulting Quick Reference Guide to assist with the entering of financial transactions in Clarity’s Classic User Experience. This doc references version 16.1.2 views. Document provides basic information on the definition of a transaction and the composition of transaction items. Detail is provided on how to create a new transaction from the Transaction Entry page of the Classic User Experience. Information is provided on how to enter detail into each individual line item for a transaction. -
Aligning work to organizational strategy is a fundamental requirement in today's ever-changing marketplace. High performing organizations are moving beyond basic connections to introduce strategic hierarchies that are tied to real measurements of business value via Clarity's Objectives and Key Results (OKRs). Join our expert guides as they present key concepts, best practices, and the evolution of strategic alignment. -
This course will focus on the financial setup and processing in Clarity. We'll discuss topics such as financial entities, fiscal periods, financial attributes, and how they all tie back to a labor rate matrix. These components are crucial for calculating labor costs within Clarity and enabling project managers to make financially sound decisions.

