Fund Assignment refers to how funds are to be consumed as spends type business processes (e.g., invoices and payment applications) come in against the base commit that is being funded.
Initial assignment rules are defined in the Assignment tab on the commitment funding Properties window. Additional details can be defined in the Fund Assignment window. To access the fund assignment window, click the Fund Assignment button on the commitment funding sheet or SOV sheet for the base commit. The Fund Assignment window is not accessible until the SOV sheet has been created.
These are defined in more detail below.
The assignment levels and rules are defined on the Assignments tab in the Properties window of the commitment funding sheet. This step is mandatory in order to do commitment level funding.
The Assignment tab lists the spends business processes that are linked to base commits enabled for commitment level funding. For each listed business process, you define how fund assignment will be done when these spends records come in against the base commit:
| • | Commitment Level - Manual: Funds are manually assigned at runtime. As spends business processes are routed and reach specified status, the amounts to be funded are collected under the Unassigned total on the commitment funding sheet, similar to project/shell level manual funding. You can then select each line of the spends BP and assign funds at runtime. This can be done on transient records or in terminal status (depending on design). Consumed funds roll up to the commitment funding sheet and the project funding sheet. |
| • | Commitment Level - Auto Ratio: Funds are assigned automatically when the spends business process reaches a specified status. Funds are assigned based on the fund ratio, which is calculated based on the current fund levels, and is managed and tracked on the commitment funding sheet. If all funds are consumed, any remaining spends amounts are collected under Unassigned. |
You can define these assignment rules on the commitment funding template. When you create a commitment funding structure in a project or shell, these assignment rules will be copied to it, and when you create new sheets from the structure, they will be copied to the sheets. If you need to, you can modify these rules on individual structures and sheets.
This is an optional step that allows you to provide details about fund assignment or consumption for each line on the base commit or any change commits. You access the Fund Assignment window by clicking the Fund Assignment button on the commitment funding sheet or the SOV sheet associated with the base commit.
| • | If you do not define any assignment options in this window, then All Funds is the default selection. This means that all funds that have been allocated to the base commit on the commitment funding sheet will be available for funding each line of the spends business process created against it (either manually or by auto ratio, as defined by the assignment rules). When this is chosen, funding information is captured on the commitment funding sheet in columns using data sources referencing “across all funds.” |
| • | There may be times when you need to specify that a specific fund must be used to fund a specific WBS code on the base commit or a change commit. You can select a specific fund (or “discrete fund”) to fund selected SOV lines. When this is chosen, funding information is captured on the commitment funding sheet in columns using data sources referencing “by discrete fund.” |
Once the commitment funding sheet is created, you can add rows and allocate funds to it.
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.