Expenditure Business Unit for Joint Venture Transactions

The Identify Joint Venture Transactions process has been updated to retrieve the expenditure business unit from the expenditure item in Oracle Project Costing for joint venture transactions with project attributes.

If the process identifies a subledger accounting transaction that’s associated with a project number, it retrieves the expenditure item for the transaction from Project Costing. If the expenditure item is available, the process copies the expenditure business unit on the expenditure item to the joint venture transaction. If the expenditure item isn’t available, the process sets the status of the transaction to Missing Expenditure Business Unit.

Business Benefits:

Helps to ensure:

  • The accuracy of the expenditure business unit on the joint venture transaction based on the Project Costing configurations. In Project Costing, the expenditure business unit is identified during the creation of the expenditure item. 
  • The expenditure items exist in Project Costing so that joint venture project costing adjustments aren’t made to nonexistent expenditure items.
  • Accurate reconciliation of joint venture distributions and project costing expenditures. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Transactions that are in Missing Expenditure Business Unit status won’t be further processed by Joint Venture Management processes until the status is cleared. You must analyze the subledger accounting transactions to determine the reason for the missing expenditure item in these transactions in Project Costing. After you complete your analysis, you must take the appropriate action to either reprocess or stop the processing of these transactions in Joint Venture Management.

Here are some possible reasons for the missing expenditure item:

  1. The process to import the subledger accounting transactions into Project Costing was not completed prior to identifying joint venture transactions.  

  1. A setup in subledger accounting has attached project attributes to transactions that were not meant to be imported into Project Costing.

  2. A Payables invoice was canceled prior to the import into Project Costing.

Key Resources

  • For more information, refer to
    • Implementing Joint Venture Management guide and
    • Using Joint Venture Management guide.
  • For information on how to recover from this status, refer to the Oracle support knowledge document - KB168732

Access Requirements

  • Joint Venture Accountant