-
Monthly Actuals - Admin is a standard calendar view of actuals posted by a user on each day of the selected month. Actuals also includes timesheets that haven’t been submitted/posted yet. Actual hours on the report are tied to user's availability i.e. when user has 0 availability (Saturday/Sunday/Holiday) then actuals are also greyed out. -
Monthly Actuals -User View is a standard calendar view of actuals posted by logged in user on each day of the selected month. Actuals also includes timesheets that haven’t been submitted/posted yet. Actual hours on the report are tied to user's availability i.e. when user has 0 availability (Saturday/Sunday/Holiday) then actuals are greyed out. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
The Cost Type field was introduced in CA PPM 13.3, but had some limitations because it wasn’t available in certain financial areas. The CA PPM 14.3 release includes the addition of Cost Type in the Cost/Rate Matrix, Chargebacks, Transactions and WIP Adjustments. This Technical Trick assists you in moving from Charge Code to Cost Type. -
This is a standalone process that can be run by an admin to change the ownership of MUX views from a specified user to another specified user. The process contains a single custom script, which has the following parameters that must be updated prior to running the process:- currentOwnerId (required): Resource ID for the current Owner (unique_name from srm_resources table)
- newOwnerId (required): Resource ID for the new Owner (unique_name from srm_resources table)
- viewCode (optional): Code for the specific view to update - leave blank if you want to transfer ownership for all views (odf_ui_views.code)
- Navigate to the process called Admin - MUX Views - Change Ownership.
- Navigate to the Start Step tab, Click on the Update Owner action, and click the Custom Script Parameters tab.
- Enter the Resource ID for the current view owner into the currentOwnerId parameter.
- Enter the Resource ID for the new owner into the newOwnerId parameter.
- If you want to update a specific view only, enter that in the viewCode parameter.
- Run the process via Organizer in Classic.
-
The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants. This will display both active and inactive projects. -
The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants. This will display both active and inactive projects. -
The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants. This will display both active and inactive projects.

