Identify Distributable Transactions by Project Values

The accounts identified as distributable for a joint venture can contain transactions related to various projects.

After you identify distributable accounts, you can add distributable project value rules to enable a joint venture definition to distribute transactions for certain projects and not others. You need this additional level of refinement if the accounts that you’ve identified as distributable for a joint venture contain project-related transactions that you don’t want distributed.

Caution: This pertains only to capital asset projects and expense-only projects defined in Oracle Fusion Cloud Project Management. Identifying transactions associated with contract projects for distribution in Oracle Joint Venture Management may result in overbilling.

In a distributable project value rule, you add the following values or combination of values to identify project-related transactions for distribution:

• Project number

• Project number, task

• Project number, task, expenditure type

• Project number, expenditure type

• Expenditure type

If you add a rule with only a project number, then all transactions associated with the project will be identified as distributable. This includes any transactions entered for the project and its associated tasks and expenditure types. In other words, if a rule includes only a project number, you don’t need additional rules for the tasks or expenditure types associated with that project. This gives you the flexibility to set up rules according to how your project-related transactions are categorized.

Note: You can’t have a rule with only a task because tasks are exclusive to projects in Oracle Project Management.