RegoXchange
  • This workflow is run as a scheduled or immediate Job to populate Project Cost Plans.  It can be configured to run on any desired set of projects.  It can be configured to populate the Cost Plan of Record based on Allocations or based on Assignments.
  • A process creating a new Cost Plan. Cost Plan properties:
    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)
    Pre-conditions:
    • 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.
  • A process creating a new Cost Plan. Cost Plan properties:
    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)
    Pre-conditions:
    • 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.
  • A process creating a new Cost Plan. Cost Plan properties:
    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)
    Pre-conditions:
    • 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.
  • Have you experimented with the modern UX channels, links and new page functionality?  Our technical experts have unlocked these capabilities to allow you to be creative in what you can do within the modern UX.  Come and learn how in this session.
  • The Creating Dependent Lookups Based On Other Fields On The Same Page document provides the steps needed to allow a user to create lookups whose values are dependent on other fields on the same page. Having the ability to use a lookup field whose list of values change based on other fields values on the same page can help reduce the number of fields that might be required and provide more relevant options to the user based on other data selections.
  • PMOs/EPMOs are feeling some pressure from Agile disruptors in their organizations. Some Agile purists insist that they can do everything with an Agile tool and no PMO governance, but this really isn’t the case. If you belong to a PMO or EPMO, this session will help you to better collaborate with your Agile counterparts in finding better and more holistic solutions to value delivery. Tips on how to use Agile principles in your talking points will also be shared.
  • The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active.  The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
  • The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active.  The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
  • The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active.  The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
  • The Custom Attributes in System portlet displays all of the custom attributes present in the system and the lookup (if applicable) associated with each. This portlet is useful finding a custom attribute on an object, auditing, or for documentation purposes. The user may narrow the results by object, data type, and last updated date.
  • The Custom License Count portlet displays the license type and number of users with each type of license. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA.  For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
Go to Top