Prepare to Implement Joint Venture Management

What You Need to Know About Oracle Financials

Understanding the business process model in Oracle Fusion Applications will help you understand how to set up Joint Venture Management to identify the accounts that contain your joint venture transactions. The following table provides an overview of the parts of the business process model that pertain to the identification and processing of transactions through Joint Venture Management:

Business Process Model Components	Relationship to Joint Venture Management
Business unit	In Oracle Fusion Applications, business units define many business functions that can be rolled up in a management hierarchy. A business unit can process transactions on behalf of many legal entities and has the responsibility for its profit and loss. In Joint Venture Management, you specify the business unit in Oracle Financials in which your joint venture financials are managed. Selecting a business unit automatically identifies the chart of accounts (COA) in the primary ledger of the business unit.
Chart of accounts	The chart of accounts enables tracking of cost center, account, and other segment levels. The key piece of financial information that links financial transactions to a joint venture is the cost center. In the Financials chart of accounts, this is the segment that's designated with the Cost Center segment label.
Ledgers	Oracle Fusion Applications reflect the traditional segregation between the general ledger and associated subledgers. Transactions are captured in the subledgers and periodically posted in detail to the primary ledger in subledger accounting. Transactions are posted in summary or in detail from the primary ledger in subledger accounting to the general ledger. As part of the day-to-day business of managing the operations of a joint venture, the managing partner pays expenses and receives revenue. These transactions are entered in the appropriate subledger such as Payable Invoices, Receivable Invoices, just to name a few. All transactions entered into these subledgers are eventually posted in detail to subledger accounting. Typically, these types of transactions are directly related to a specific joint venture. The second source of transactions for Joint Venture Management is the general ledger. Joint Venture Management only identifies transactions in the general ledger that did not originate from subledger accounting. These transactions typically are indirect charges or allocated amounts to a joint venture.

Business Process Model Components

Relationship to Joint Venture Management

Business unit

In Oracle Fusion Applications, business units define many business functions that can be rolled up in a management hierarchy. A business unit can process transactions on behalf of many legal entities and has the responsibility for its profit and loss. In Joint Venture Management, you specify the business unit in Oracle Financials in which your joint venture financials are managed. Selecting a business unit automatically identifies the chart of accounts (COA) in the primary ledger of the business unit.

Chart of accounts

The chart of accounts enables tracking of cost center, account, and other segment levels. The key piece of financial information that links financial transactions to a joint venture is the cost center. In the Financials chart of accounts, this is the segment that's designated with the Cost Center segment label.

Ledgers

Oracle Fusion Applications reflect the traditional segregation between the general ledger and associated subledgers. Transactions are captured in the subledgers and periodically posted in detail to the primary ledger in subledger accounting. Transactions are posted in summary or in detail from the primary ledger in subledger accounting to the general ledger.

As part of the day-to-day business of managing the operations of a joint venture, the managing partner pays expenses and receives revenue. These transactions are entered in the appropriate subledger such as Payable Invoices, Receivable Invoices, just to name a few. All transactions entered into these subledgers are eventually posted in detail to subledger accounting. Typically, these types of transactions are directly related to a specific joint venture.

The second source of transactions for Joint Venture Management is the general ledger. Joint Venture Management only identifies transactions in the general ledger that did not originate from subledger accounting. These transactions typically are indirect charges or allocated amounts to a joint venture.

Joint Venture Management uses the details that you enter in joint venture definitions to identify the accounts in Oracle Financials that contain the transactions for your joint ventures. The following illustration shows the flow of identifying and processing expenses and revenue from Oracle Financials through Joint Venture Management:

Related information:

Prerequisites and Assumptions

Joint Venture Management is a functional area of Oracle Financials. As such, you must be using Oracle Fusion Financials to manage the financial accounts for your joint venture transactions before implementing Joint Venture Management. Each user of Joint Venture Management might require an additional subscription to Oracle ERP Cloud.

Note: If you use an accounting solution other than Oracle Financials, you can use Oracle Accounting Hub to import your joint venture transactions into Oracle Financials.

Related information:

Audience and Scope

These implementation instructions pertain to the following users with these responsibilities:

Administrator with the IT Security Manager Role

Uses the Security Console to set up Joint Venture Management users with the proper security and roles to perform actions according to the privileges in each role.

Application Implementation Consultant (Cloud Administrator)

Enables the Joint Venture Management feature under the Financials offering on the Offerings page in Functional Setup Manager (FSM).
Uses the migration services in FSM to move invoicing partner and joint venture definition data from a source to target environment.
Performs the setup tasks in subledger accounting to override the revenue account in invoice distributions for joint venture invoices.
Creates lookups for Joint Venture Management user-defined field values. (Optional)

Joint Venture Administrator

Sets up invoicing partners.
Creates joint venture definitions.
Specifies transaction date sources in the Joint Venture System Options that are used to process joint venture transactions from subledger accounting and general ledger. (Optional)
Note: In conjunction with this task, a user with the Application Implementation Consultant role needs to set up subledger accounting and the general ledger to capture a transaction date. See Identify a Transaction Date for Processing Joint Venture Transactions for more information.
Uses rapid implementation spreadsheets to set up Joint Venture Management.

Joint Venture Accounting Manager

Creates joint venture definitions.

Joint Venture Accountant

Creates joint venture definitions.
Schedules processes to automatically identify joint venture transactions, distribute the transactions, and create accounts receivable invoices to recoup joint venture costs.

Note: As you can see here, all three types of Joint Venture Management users can create joint venture definitions. This gives you the flexibility to determine who has this responsibility within your organization.