Management Cloud Oracle Joint Venture€¦ · Joint Venture Management uses the information in the ownership denition to calculate the split of transactions and create distributions

Oracle Joint VentureManagement Cloud

Implementing Joint VentureManagement

20B

Oracle Joint Venture Management CloudImplementing Joint Venture Management

20B

Part Number: F26224-02

Copyright © 2020, Oracle and/or its aliates.

Authors: Joint Venture Management Information Development

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protectedby intellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please reportthem to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, thenthe following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed oractivated on delivered hardware, and modications of such programs) and Oracle computer documentation or other Oracle data delivered to oraccessed by U.S. Government end users are "commercial computer software" or “commercial computer software documentation” pursuant tothe applicable Federal Acquisition Regulation and agency-specic supplemental regulations. As such, the use, reproduction, duplication, release,display, disclosure, modication, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system,integrated software, any programs embedded, installed or activated on delivered hardware, and modications of such programs), ii) Oracle computerdocumentation and/or iii) other Oracle data, is subject to the rights and limitations specied in the license contained in the applicable contract. Theterms governing the U.S. Government’s use of Oracle cloud services are dened by the applicable contract for such services. No other rights aregranted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended foruse in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardwarein dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safeuse. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle Corporation and/or its aliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarksor registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced MicroDevices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. OracleCorporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicableagreement between you and Oracle.

The business names used in this documentation are ctitious, and are not intended to identify any real companies currently or previously in existence.


Contents

Preface .................................................................................................................................. i

1 Introduction to Joint Venture Management 1Introduction to Joint Venture Management ............................................................................................................................. 1

2 Prepare to Implement Joint Venture Management 5Prepare to Implement Joint Venture Management ................................................................................................................ 5

3 Enable Joint Venture Management 9Enable Joint Venture Management ............................................................................................................................................ 9

4 Set Up Joint Venture Management Users and Security 11Set Up Joint Venture Management Users and Security ....................................................................................................... 11

5 Set Up Invoicing Partners 15Set Up Invoicing Partners ........................................................................................................................................................... 15

6 Create Joint Venture Denitions 17Create Joint Venture Denitions ............................................................................................................................................... 17

7 Schedule or Run ESS Processes for Joint Venture Management 33Schedule or Run Joint Venture Management ESS Processes ............................................................................................ 33

8 Migrate Joint Venture Setup Data to Production 35Migrate Joint Venture Setup Data to Production .................................................................................................................. 35

9 Manage Joint Venture Management Lookups 39Manage Joint Venture Management Lookups ...................................................................................................................... 39


10 Integrate and Extend Joint Venture Management 41Integrate and Extend Joint Venture Management ................................................................................................................ 41


Preface

PrefaceThis preface introduces information sources that can help you use the application and this guide.

Oracle Cloud Applications GuidesTo nd guides for Oracle Applications, go to the Oracle Help Center at hp://docs.oracle.com/.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at hp://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Oracle customers that have purchased support have access to electronic support through My Oracle Support. Forinformation, visit hp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit hp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

i

http://docs.oracle.com/

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs


Preface

ii


Chapter 1Introduction to Joint Venture Management

1 Introduction to Joint Venture Management

Introduction to Joint Venture Management Joint Venture Management enables a managing partner of a single joint venture or thousands of joint ventures tomanage the distribution of costs and revenue among joint venture partners. It enables you to manage amounts toinvoice to partners, both external partners to the managing partner’s organization and any internal partners thatoperate as a separate business entity within the organization. It also supports posting journals with the managingpartner’s share to the managing partner’s ledger.

Joint Venture Management automatically:

• Identies joint venture transactions in Oracle Financials.

• Splits transactions based on each partner's percentage of ownership in the joint venture.

• Generates distribution records that contain each partner's share in the transaction.

Joint Venture Management gives you the exibility to adjust for changes in a joint operating agreement (JOA) duringthe life cycle of a joint venture. You can add or remove partners and adjust for changes in their ownership percentages.Joint Venture Management also supports direct billing, which gives you the option to apply a full transaction amount toan individual partner.

For auditing and tracking purposes, Joint Venture Management retains important information about processedtransactions to help you resolve any partner disputes over distributed amounts. It enables you to readily accessimportant details, such as:

• Original transaction information including the transaction date, amount, and the account in which thetransaction was initially recorded.

• Partner information including all partners with distributions and each partner’s percentage of ownership.

• The date the split was calculated and distribution amounts were generated.

Joint Venture Management also provides:

• Visual indicators to alert users if the setup of a joint venture isn't complete.

• The ability to set up partners once in the system and add them to multiple joint ventures.

• Rounding support to handle the distribution of costs or revenue that remain to ensure the total of the splitcalculations equals the original transaction amount.

How Joint Venture Management Works Joint Venture Management processes transactions from Oracle Financials Cloud. It also supports processingtransactions from third-party nancial systems, as long as those transactions are rst imported into Oracle Financialsthrough Oracle Accounting Hub.

This illustration and the details that follow describe each part of the process to identify and distribute joint venturetransactions in Joint Venture Management:

1



Create Joint Venture DenitionsA joint venture accountant or accounting manager sets up a joint venture denition for each joint venture. A jointventure denition contains the information Joint Venture Management uses to identify joint venture expenses andrevenue in Oracle Financials. It also includes an ownership denition for identifying the partners in a joint venture andeach partner's percentage of ownership. Joint Venture Management uses the information in the ownership denition tocalculate the split of transactions and create distributions with each partner's share of the transaction.

Automatically Identify Joint Venture TransactionsThe Identify Joint Venture Transactions process in the Enterprise Scheduler Service (ESS) is a scheduled process thatuses the details in a joint venture denition to identify transactions for processing. You can schedule this processto identify transactions for one or all of your active joint ventures. This ESS process ensures transactions previouslyidentied and processed by Joint Venture Management aren't processed again.

The Joint Venture Transactions work area enables you to review transactions identied by the Identify Joint VentureTransactions process. You can review transaction details, such as the default ownership denition that will be applied totransactions to calculate the split. The Transactions work area gives you the option to associate a dierent ownershipdenition to a transaction. Or you can associate a direct billed partner to a transaction to distribute an entire transactionamount to a single partner.

Automatically Calculate Splits and Create DistributionsThe Create Joint Venture Distributions ESS process is a scheduled process that calculates the split of transactions andgenerates distribution records. This ESS process uses details in the joint venture denition, specically stakeholderownership percentages in the ownership denition, to calculate the split and create distributions.

An ownership denition has two requirements: the ownership percentages of all stakeholders must total 100 percentand it must have an eective date range. The eective date range enables you to set up multiple ownership denitionswith successive date ranges to account for any changes in the joint operating agreement over the life cycle of a jointventure. When processing transactions, the Create Joint Venture Distributions ESS process compares the transactiondate in each transaction against the eective dates in the ownership denitions to determine which ownershipdenition to use to calculate the split.

2



Review DistributionsThe Joint Venture Distributions work area displays distribution records generated from the Create Joint VentureDistributions ESS process. Each record contains a partner's share of costs or revenue to be invoiced. Distribution recordsalso include partner information, the original transaction amount, and the transaction date that represents the date ofservice for which the transaction was originally created. It also includes other important details to help you troubleshootany issues or resolve any disputes over distribution amounts.

3



4


Chapter 2Prepare to Implement Joint Venture Management

2 Prepare to Implement Joint VentureManagement

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 JointVenture Management to identify the accounts that contain your joint venture transactions. The following table providesan overview of the parts of the business process model that pertain to the identication and processing of transactionsthrough Joint Venture Management:

Business Process Model Components Relationship to Joint Venture Management

Business unit In Oracle Fusion Applications, business units dene many businessfunctions that can be rolled up in a management hierarchy. A businessunit can process transactions on behalf of many legal entities and hasthe responsibility for its prot and loss. In Joint Venture Management,you specify the business unit in Oracle Financials in which your jointventure nancials are managed. Selecting a business unit automaticallyidenties the chart of accounts (COA) in the primary ledger of thebusiness unit.

Chart of accounts The chart of accounts enables tracking of cost center, account, andother segment levels. The key piece of nancial information thatlinks nancial transactions to a joint venture is the cost center. In theFinancials chart of accounts, this is the segment that's designated withthe Cost Center segment label.

Ledgers Oracle Fusion Applications reect the traditional segregation betweenthe general ledger and associated subledgers. Transactions are capturedin the subledgers and periodically posted in detail to the primary ledgerin subledger accounting. Transactions are posted in summary or indetail from the primary ledger in subledger accounting to the generalledger. As part of the day-to-day business of managing the operations ofa joint venture, the managing partner pays expenses and receivesrevenue. These transactions are entered in the appropriate subledgersuch as Payable Invoices, Receivable Invoices, just to name a few. Alltransactions entered into these subledgers are eventually posted indetail to subledger accounting. Typically, these types of transactions aredirectly related to a specic joint venture. The second source of transactions for Joint Venture Management is thegeneral ledger. Joint Venture Management only identies transactionsin the general ledger that did not originate from subledger accounting.

5



Business Process Model Components Relationship to Joint Venture Management

These transactions typically are indirect charges or allocated amountsto a joint venture.

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

Related information:

• Enterprise Structure Business Process Model

• Cost Centers and Departments

• Ledgers and Subledgers

Prerequisites and Assumptions Joint Venture Management is a functional area of Oracle Financials. As such, you must be using Oracle FusionFinancials to manage the nancial accounts for your joint venture transactions before implementing Joint VentureManagement. 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 toimport your joint venture transactions into Oracle Financials.


• Get Started with Financials

• Implementing Oracle Accounting Hub

6

http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAESC166661

http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAESC172905

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAIGL49259

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FACSF882073

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAIAC924422



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 toperform actions according to the privileges in each role.

Application Implementation Consultant (Cloud Administrator)

• Enables the Joint Venture Management feature under the Financials oering on the Oerings page inFunctional Setup Manager (FSM).

• Uses the migration services in FSM to move invoicing partner and joint venture denition data from a source totarget environment.

• Creates lookups for Joint Venture Management user-dened eld values. (Optional)

Joint Venture Administrator

• Sets up invoicing partners.

• Creates joint venture denitions.

Joint Venture Accounting Manager


Joint Venture Accountant


• Schedules ESS processes to automatically identify and distribute joint venture transactions.

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

7



8


Chapter 3Enable Joint Venture Management

3 Enable Joint Venture Management

Enable Joint Venture Management To use Joint Venture Management, an administrator must rst enable Joint Venture Management in Functional SetupManager (FSM).

You must have the Application Implementation Consultant job role(ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) to perform this task. This role includes theFinancials Application Administrator (ORA_FUN_FINANCIAL_APPLICATION_ADMINISTRATOR_JOB) job role.

To enable Joint Venture Management in FSM:

1. From the Navigator, select Oerings under My Enterprise.2. Under Oerings, select Financials.3. In the right pane, click Opt In Features.

Note: You can also click New Features to view a description of the new features for the release.

4. Make sure that Financials is selected from the Opt In drop-down list at the top of the page. And then scrolldown until you see Joint Venture Management in the list and click the name.

5. Click the Enable check box next to Joint Venture Management.After enabling Joint Venture Management, you can view the setup tasks for Joint Venture Management in FSM:

1. From the Navigator, select Setup and Maintenance.2. Click the Setup drop-down list and select Financials.3. Scroll down the list until you nd Joint Venture Management and then click the name.

The system displays the Joint Venture Management tasks. Joint Venture Management users with the propersecurity can click the tasks here to access the Joint Venture Management work areas for seing up andmanaging invoicing partners and joint venture denitions.

Note: Although available, the Manage Supporting References task is currently not used in JointVenture Management.


• Manage Setup Using Functional Areas

9

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OAFSM1684917


Chapter 3Enable Joint Venture Management

10


Chapter 4Set Up Joint Venture Management Users and Security

4 Set Up Joint Venture Management Usersand Security

Set Up Joint Venture Management Users and Security

About Joint Venture Management Users and Security Set up Joint Venture Management users with access to Joint Venture Management features and data. To set up users,you apply predened roles and other security according to each user's responsibilities. Roles include privileges and datasecurity. Privileges determine what users can do in Joint Venture Management. Data security determines what datausers can access.

An administrator with the IT Security Manager (ORA_FND_IT_SECURITY_MANAGER_JOB) role can set up your JointVenture Management users, which include:

• Joint venture administrator

Set up security to enable this user to:

◦ Set up invoicing partners in the Invoicing Partners work area.

◦ Create and manage joint venture denitions in the Joint Ventures work area.

• Joint venture accounting manager

Set up security to enable this user to create and manage joint venture denitions in the Joint Ventures workarea.

• Joint venture accountant

Set up security to enable this user to:

◦ Create and manage joint venture denitions in the Joint Ventures work area.

◦ Access the Enterprise Scheduler Service (ESS) application to run the ESS processes to identify anddistribute joint venture transactions.

◦ Access the Transactions and Distributions work areas to review joint venture transactions anddistributions.

When set up as prescribed, all users can create and manage joint venture denitions. But only the joint ventureadministrator can set up invoicing partners. This separation of duties provides a level of oversight and control to thejoint venture administrator. It ensures that only partners identied in the joint operating agreement can be set up asinvoicing partners that are associated with distributed transactions for the joint venture.

If privileges in the roles do not align with the responsibilities of the users in your organization, you can create new rolesand add privileges to the new roles according to the job responsibilities of your users. You can add multiple roles to auser, so you don't need to create a custom role that includes all privileges needed for a particular user.

11



Set Up Joint Venture Management Users Set up Joint Venture Management users with the predened roles described here to enable them to perform tasksaccording to their responsibilities.

Note: In addition to assigning the predened roles, an additional security setup is required for a joint ventureadministrator user, as described in this section.

You must have the IT Security Manager (ORA_FND_IT_SECURITY_MANAGER_JOB) role to set up users.

For instructions on how to set up user accounts and provision roles for Oracle ERP users, and for more details about theJoint Venture Management roles, see these topics:

• Application Users Management

• Role Provisioning

• Assign Data Access to Users

• Security Reference for Financials Guide

Joint Venture AccountantAssign the following roles to a joint venture accountant user:

• ORA_JV_JOINT_VENTURE_ACCOUNTANT_JOB

• ORA_PER_EMPLOYEE_ABSTRACT

In addition, for the current release, you need to add the Trading Community Party data security policy to the JointVenture Accountant role (ORA_JV_JOINT_VENTURE_ACCOUNTANT_JOB).

Joint Venture Accounting ManagerAssign the following role to a joint venture accounting manager user:ORA_JV_JOINT_VENTURE_ACCOUNTING_MANAGER_JOB

In addition, for the current release, you need to add the Trading Community Party data security policy to the JointVenture Accounting Manager role (ORA_JV_JOINT_VENTURE_ACCOUNTING_MANAGER_JOB).

Joint Venture AdministratorAssign the ORA_JV_JOINT_VENTURE_APPLICATION_ADMINISTRATOR_JOB role to the joint venture administrator user.This role enables access to the Invoicing Partners work area to set up invoicing partners and to the Joint Ventures workarea to create joint venture denitions.

As part of seing up invoicing partners, a joint venture administrator species payable (supplier) and receivable(customer) entities related to a joint venture partner. To view and select from a list of available suppliers and customersin the Invoicing Partners work area, the user's prole must have permissions to access this information in ERP Cloud.Therefore, in addition to assigning the preceding role, you need to perform the following setup tasks for this user:

• Create a new role, associate the ORA_POZ_USE_REST_SERVICE_VIEW_SUPPLIER_PROFILE aggregate role tothe new role, and then assign the new role to the user.

12

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FASER2406010



https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OAFRM



• Congure customer data access for the joint venture administrator user and the new role.

To set up a joint venture administrator user:

1. Add the ORA_JV_JOINT_VENTURE_APPLICATION_ADMINISTRATOR_JOB role to the user.2. Create a new job role for a supplier prole that includes the

ORA_POZ_USE_REST_SERVICE_VIEW_SUPPLIER_PROFILE aggregate role shown here:

3. Add the new job role with the supplier prole to the joint venture administrator user.

Your joint venture administrator user prole should have both roles associated with it, as shown in the followingexample:

4. Congure customer data access for your joint venture administrator user and Joint Venture ApplicationAdministrator role:

a. On the Home page, click Setup and Maintenance.b. In the Setup drop-down list at the top of the page, select Financials.c. In the Functional Areas list, click Enterprise Prole.d. In the task list on the right, click Manage Reference Data Set Data Access for Users.e. Enter the following values to congure the data access:

- User Name- Role- Security Context. Enter Reference data set.- Security context value. Enter the name of the data set that contains the customer data, for example

Vision Operations Set.

13



This value enables the display of valid values in the Customer drop-down list in the InvoicingPartners work area.

The results should look similar to the following example:

14


Chapter 5Set Up Invoicing Partners

5 Set Up Invoicing Partners

Set Up Invoicing Partners

About Invoicing Partners As part of seing up a joint venture denition, you assign partners in a joint venture as stakeholders. In Joint VentureManagement, these partners are referred to as invoicing partners because you can invoice them for costs and revenueassociated with the joint venture. Before you can assign partners—or invoicing partners—as stakeholders, you have toadd the invoicing partners to the system. Seing up invoicing partners separately enables you to add the same partneras a stakeholder in multiple joint ventures.

Invoicing partners are typically external to the managing partner’s organization. But you can also have an invoicingpartner that's internal to the organization.

Each invoicing partner that you add must include customer information, supplier information, or both. As the managingpartner, you use the customer information to create invoices for distributing costs. You use the supplier information tocreate invoices for distributing revenue.

When you add an invoicing partner as a stakeholder in a joint venture, the customer and supplier informationassociated to the invoicing partner must be from the same business unit that's associated to the joint venture.

Add an Invoicing Partner To add invoicing partners, you must be set up as a joint venture administrator, which includes theORA_JV_JOINT_VENTURE_APPLICATION_ADMINISTRATOR_JOB role and other security setup. If customer or supplierinformation for a partner is not available on the Create Invoicing Partner page, contact your administrator to make sureyour user prole is set up correctly. See Set Up Joint Venture Management Users and Security for more information.

1. In Functional Setup Manager, access the Joint Venture Management functional area under the Financialsoering.

2. Click the Manage Invoicing Partners task.3. On Invoicing Partners, click Add (+ icon).4. On Create Invoicing Partner, enter the following details:

◦ Invoicing Partner Name. Use all upper case characters and no spaces. If you don’t, the name will beadjusted automatically according to the naming convention.

◦ Description.

◦ Status. The default is Pending. You must change it to Active in order to add the invoicing partner as astakeholder in a joint venture.

Note: You can’t change the status to Active until you add the following customer and supplierinformation.

5. Under Invoicing Information, enter customer information, supplier information, or both depending on theinvoicing partner’s role in the joint venture:

15


Chapter 5Set Up Invoicing Partners

a. Select the customer name and supplier name from the appropriate drop-down list.

You can use the search elds in the drop-down lists to rene the list of names.b. Select the customer site and supplier site, if available.

The system displays the tax registration number for the customer or supplier if available. It also displaysthe party number associated with the customer or supplier.

6. At this point, you can:

◦ Save and close the invoicing partner.

◦ Save it and create another invoicing partner.

Activate an Invoicing Partner You must activate an invoicing partner before you can add it as a stakeholder in a joint venture. The invoicing partnermust include customer or supplier information, or both, before you can activate it.

1. On the Invoicing Partners tab, open the invoicing partner that you want to activate.2. On Edit Invoicing Partner, change the Status to Active.3. Save the invoicing partner.

16


Chapter 6Create Joint Venture Denitions

6 Create Joint Venture Denitions

Create Joint Venture Denitions

What Is a Joint Venture Denition? A joint venture denition contains the information Oracle Joint Venture Management uses to calculate the costs andrevenue to distribute among partners in a joint venture. You create a joint venture denition for each joint venture thatyou manage. A joint venture denition includes:

• Identication of distributable accounts, the accounts that contain the joint venture transactions to bedistributed among partners. These accounts are typically in subledger accounting, but can also reside in thegeneral ledger.

• Stakeholders. The partners in a joint venture that share in the joint venture costs and revenue. You can alsoinclude interested parties as stakeholders, parties that don't share in costs and revenue but participate forinformation or oversight purposes.

• An ownership denition to dene each stakeholder’s percentage of ownership in the joint venture. JointVenture Management uses the ownership denition to calculate each stakeholder’s share of costs, revenue, andother expenses. You can have multiple ownership denitions, but you must designate one as the default.

• Status. When seing up a joint venture, the initial status is Initiated. When complete, you set the status toActive to enable it to identify and process transactions for distribution among stakeholders. A user with theApplication Implementation Consultant role can set up additional user-dened statuses if desired. For example,you can add an On Hold status to indicate that the current denition shouldn't be made active.

• Optional approval information. You can enter an approval of the joint venture denition if your businessprocess requires an approval before activation.

Monitor Your Progress with Alerts and Dashboards As you set up your joint venture denitions, the Joint Ventures work area provides visual indicators to alert you to jointventure denitions that aren't fully dened. You can click the Show Alerts check box to enable the alerts. Place yourcursor over the alert icon next to a joint venture denition to view the remaining tasks that need to be completed.

The following example shows an alert next to the "JONESOFNEWCASTLE" joint venture with a list of the tasks that mustbe performed to complete the joint venture denition:

17



If using approvals, you can monitor the progress of your approvals by expanding the Dashboard in the Joint Ventureswork area. The dashboard shows approval statuses and approvals by date for your joint ventures, as shown in thisexample:

18



Enter Joint Venture Details To initially create a joint venture denition, you only need to name it and save it. This gives you the option to begincreating multiple denitions and complete them at a later time.

You must be one of the following users set up with the proper roles to access the task to create a joint venture:

• Joint venture accountant

• Joint venture accounting manager

• Joint venture administrator

If you can't access the Joint Ventures work area following the steps below, contact your IT Security Manager to makesure you have been set up with the proper role.

1. From the Navigator, select Setup and Maintenance.2. In Functional Setup Manager, select Financials from the Setup drop-down list.3. Scroll down and click the Joint Venture Management functional area.

19



4. Click the Manage Joint Venture Denitions task, which takes you to the Joint Ventures work area where you canset up and manage your joint venture denitions.

5. On Joint Ventures, click Create Joint Venture (+ icon) to create a new joint venture denition.6. On Create Joint Venture, enter a name and description for the joint venture denition.7. At this point, you can:

◦ Save and close the joint venture denition.

◦ Save it and create another new joint venture denition.

◦ Save it and use the other tabs to identify the distributable accounts, stakeholders, and ownershippercentages.

Identify Distributable Accounts Each transaction entered into Oracle Financials has an identier—a code combination made up of values from dierentsegments in the COA—that associates a transaction to an account. For example, if your joint venture nancials aremanaged in two dierent cost centers, the code combination of transactions in one cost center includes the segmentvalue for that cost center. The code combination of transactions in the other cost center include the segment value forthat cost center. Other values that make up a code combination represent accounts in one or more segments, such asan account in Payables for managing a certain category of expenses.

In a joint venture denition, you specify a combination of segment values to identify the accounts in Oracle Financialsthat contain the joint venture transactions. In Joint Venture Management, these accounts are referred to as distributableaccounts because the transactions associated with these accounts will be distributed among joint venture partners.These accounts are typically in subledgers in subledger accounting, but they can also reside in the general ledger.

You set up a joint venture denition with the following details to enable it to identify distributable accounts:

• The business unit for managing the nancials for the joint venture in Oracle Financials.When you specify a business unit, the system automatically identies the COA in the primary ledger associatedwith the business unit.

• Segments in the COA.Based on the business unit selected, Joint Venture Management automatically displays a list of segments in theCOA that are used by the business unit. From this list, you select only the segments that you need to identifydistributable accounts. The segment for cost centers is selected by default because a cost center is the key toidentifying nancial transactions for a joint venture. All transactions are associated to a cost center. You mustselect at least one other segment in addition to the cost center segment.

• Combination of values from the selected segments, referred to as distributable segment values, to identify eachdistributable account.In the joint venture denition, you select a combination of segment values to identify the distributableaccounts. If a cost center and the other selected segments include only the distributable transactions for a jointventure, you can simply select the cost center segment value.

It's important to remember that the key piece of nancial information that associates transactions in Oracle Financials toa particular joint venture is the cost center. In Joint Venture Management, you can have one or more cost centers relatedto a joint venture. But you can't associate the same cost center to more than one joint venture. In this way, Joint VentureManagement prevents you from using the same combination of a COA and cost center in more than one joint venturedenition. This ensures that transactions in Oracle Financials aren't processed by more than one joint venture denition.

20



Example of Identifying Distributable Accounts A petroleum company is the managing partner of a joint venture for a drilling exploration project. For this project, a jointventure accountant created a joint venture denition named APOLLOBASIN. The following image shows the sequencethe accountant took to identify the distributable accounts for the joint venture denition, followed by a description ofthe details he entered:

On the Details page, the accountant selected Vision Operations for the business unit, which is the business unit inOracle Financials for managing the nancials for the drilling exploration project. The primary ledger for this businessunit has a COA named Operations Accounting Flex, which was automatically identied when the accountant selectedthe business unit.

Next, the accountant accessed the Distributable Segments page, which shows the available segments in the COA:Company, Department, Account, Sub-Account, and Product. The Department segment is selected by default becauseit's the segment for the cost centers, which is the key detail needed to associate nancial transactions to a joint venture.He enabled the Account segment because he knows that all transactions for the joint venture are in the accounts in theAccount segment.

On the Cost Centers page, he clicked Add (+ icon) and identied two dierent cost centers. After which, he clicked Editnext to each cost center to identify distributable segment value combinations: four for cost center 510 and four for costcenter 520. To verify the distributable segment value combinations he identied for cost center 510, he clicked Edit inthe row to review the combinations.

The edit page displays columns for segments selected on the Distributable Segments page—Department and Account.Here the accountant reviewed the distributable segment value combinations he added for the joint venture. He setup the joint venture to process all transactions identied with a combination of cost center 510 and account 7410, acombination of cost center 510 and account 7420, and so forth. The accountant can click Add (+ icon) to add rows toidentify additional accounts if necessary. Or if he specied an incorrect combination, he can delete that row.

21



Specify a Business Unit Specify the business unit in Oracle Financials that contains the joint venture nancials. You can skip these steps if youalready selected a business unit when you entered the initial joint venture denition details.

1. On Edit Joint Venture, click Details in the left navigation pane.2. Click the Business Unit drop-down list and select a business unit for the joint venture.3. Click Save.

Specify Segments with Distributable Accounts Specify the segments in the COA that contain distributable accounts.

1. On Edit Joint Venture, click Distributable Segments in the left navigation pane.

The Distributable Segments page displays the available segments based on the business unit selected on theDetails page. If you don’t see the expected segments, make sure you selected the appropriate business unit.

2. Select each segment that contains accounts you want to identify as distributable. The segment for cost centersis selected by default and can’t be deselected. You must select at least one other segment in addition to the costcenter segment.

The segment for cost centers might not be named "Cost Centers." But you can tell that it's the segment withthe cost center label because it's selected and grayed out. Here's an example of a cost center segment named"Department:"

3. Click Save on the Distributable Segments page.

Specify Distributable Segment Values Specify the code combinations, or combinations of segment values, to identify distributable accounts in OracleFinancials—the accounts that contain the transactions for the joint venture. At a minimum, each combination mustinclude a cost center segment value. You can add a value for the cost center segment and leave the other segmentvalues blank if all accounts in the other segment or segments only contain transactions for the joint venture. Ifsegments in the COA contain both distributable accounts and accounts with transactions that shouldn't be distributed,you must identify each distributable account in the joint venture denition.

1. On Edit Joint Venture, click Cost Centers in the left navigation pane.2. Click Add (+ icon), and then in the empty row in the grid, click in the rst column and select a cost center.

22



This column represents the segment with the cost center label. This column's heading reects how thissegment was named in Oracle Financials.

3. Click Save.

The system displays the description of the cost center.4. If all accounts for the cost center and other segments identied in the previous task only contain transactions

for the joint venture:

a. In the row with the cost center, click Edit.b. On Distributable Segment Values, click Add (+ icon).

The system adds a row with the cost center value. In addition to the column for the cost center, it displayscolumns based on the segments selected on the Distributable Segments page, as described in thepreceding task.

c. Leave the remaining segment or segments blank.d. Click Save.

The following example shows a row on the Distributable Segment Values page for cost center 112(East Region Resources), where the value for the Account segment is blank. This means that anyaccounts associated to cost center 112 and the accounts in the Accounts segment are distributable.

5. If a cost center contains both distributable accounts and non-distributable accounts, you must identify eachdistributable account. To do so:

a. On the Cost Centers page, click Edit in the row with the cost center.b. On Distributable Segment Values, click Add (+ icon), which adds an editable row for entering a

combination of segment values for the cost center.

The following example shows three segments for a joint venture: Department, which is the cost centersegment selected by default; Account; and Product.

23



c. To identify distributable accounts in the other segments, you can:

- Click the drop-down list and select a value.- Use the % wildcard to designate a range of accounts in the segment as distributable. For example

in the preceding image, 1% is entered for the Product segment, which means that accounts from100 to 199 contain transactions that are distributable.

- Leave a segment blank if all the accounts in the segment are distributable.d. Add additional rows to identify additional distributable accounts as needed.e. Click Save.

The system displays the descriptions for each value.f. Add additional rows to identify additional distributable accounts as needed.

6. When nished, click Save and Close.

Note: On the Cost Centers page, if you identied the wrong cost center, you can select the row withthe cost center and click Delete. This also removes any distributable segment values associated withthe cost center.

Set Up Stakeholders In Joint Venture Management, you add partners and interested parties in a joint venture as stakeholders.

Before you can add partners as stakeholders in a joint venture, you set them up separately in the system as invoicingpartners. And then you associate the invoicing partner to a stakeholder. Seing up invoicing partners separatelyenables you to add the same partner as a stakeholder in multiple joint ventures. See Set Up Invoicing Partners for moreinformation.

You can add the following types of stakeholders to a joint venture:

• External stakeholders. Joint venture partners that are external to the managing partner’s organization.

• Internal stakeholders. Partners in the joint venture that are internal to the managing partner’s organization. Youcan set up an internal stakeholder in two ways:

◦ As an invoicing partner to be invoiced as a separate line of business, so that shares in costs and revenuecan be posted to accounts receivable (AR) and accounts payable (AP) respectively.

◦ To have shares of costs and revenue posted as journals in the managing partner’s cost center.

24



You can also set up an external or internal stakeholder as an interested party for stakeholders that don't share in costsor revenue but participate for information or oversight purposes only.

Important! The invoicing partner that you associate to an external or internal stakeholder has a customer, a supplier, orboth associated with it. The customer and supplier associated to the invoicing partner must be from the same businessunit that's associated to the joint venture.

Distribution Only OptionYou can also set up external and internal stakeholders as "distribution only" for partners you don’t want to createinvoices or journal entries for. For example, internal stakeholders, such as the managing partner, may not want to beinvoiced or have funds transferred internally. Or you might select this option for a partner who is disputing the costs oris not paying their portion of the joint venture. This seing ensures that transaction amounts are still split correctly andthat the calculated distribution amounts for the stakeholders always balance to the amount on the original transaction.

Add an External Stakeholder

1. On the Joint Ventures page, locate and click the name of the joint venture denition that you want to add anexternal stakeholder to.

2. On Edit Joint Venture, click Stakeholders in the left navigation pane.3. Click Add (+ icon) to add a stakeholder.4. On Create Stakeholder, enter a name and description for the stakeholder and click Save.

Use all upper case characters and no spaces for the name. If you don’t, the system will automatically adjust itaccording to the naming convention.

A description is not required. If you leave it blank, the description for the invoicing partner will appear herewhen you select the invoicing partner.

5. For the Stakeholder Type, select External.

The status for new stakeholders is Pending. You can’t change it to Active until after you complete the eldsunder Partner Information.

Note: The Stakeholder Category eld is an optional eld that contains user-dened values that yourcompany can set up to further categorize your stakeholders if desired.

6. Select Distribution Only if the stakeholder will only participate in the transaction distribution and won't beinvoiced.

You also have the option to change this seing when you add the stakeholder to the ownership denition onthe Ownership Denition page.

7. Under Partner Information, make sure Invoice is selected.

If the external stakeholder is an interested party, see Add an Interested Party Stakeholder.8. Select the invoicing partner from the Invoicing Partner drop-down list.

The system displays the related party information in the eld below and includes any additional details ifavailable.

9. Save the stakeholder.

Add an Internal Stakeholder 1. On the Joint Ventures page, locate and click the name of the joint venture denition that you want to add an

internal stakeholder to.

25



2. On Edit Joint Venture, click the Stakeholders tab on the left.3. Click Add (+ icon) to add a stakeholder.4. On Create Stakeholder, enter a name and description for the stakeholder and click Save.

A description is not required. If left blank and you associate an invoicing partner, the description for theinvoicing partner will appear here.

5. For the Stakeholder Type, select Internal.The status for new stakeholders is Pending. You can’t change it to Active until after you complete the eldsunder Partner Information.

Note: The Stakeholder Category eld is an optional eld that contains user-dened values that yourcompany can set up to further categorize your stakeholders to make them easier to manage.

6. Select Distribution Only if the stakeholder will only participate in the transaction distribution and won't beinvoiced.You also have the option to change this seing when you add the stakeholder to the ownership denition onthe Ownership Denition page.

7. Under Partner Information, select one of these options for the Invoicing Preference:

◦ Create invoices. Create invoices for distributing costs and revenue to accounts receivable (AR) andaccounts payable (AP) respectively.

◦ Create journals. Enable shares of costs and revenue to be posted as journals in the managing partner’scost center.

8. If you selected “Create invoices,” select the invoicing partner from the Invoicing Partner drop-down list.The system displays the related party information in the eld below and includes any additional details ifavailable.

9. If you selected “Create journals,” complete these elds:

◦ Cost Center. Enter the cost center for posting costs and revenue to.

◦ Party. Select a party to include contact information for the cost center internal stakeholder.The system displays the related party information and includes any additional details if available.


Add an Interested Party Stakeholder You can set up an external stakeholder or an internal stakeholder as an interested party.

Before you can add an interested party stakeholder, you must have party information set up for the stakeholder inOracle Applications Cloud. You can then assign the party to the interested party stakeholder. If party information foryour interested party is not available on the Stakeholders page, see Manage Person Information.

1. On the Joint Ventures page, locate and click the name of the joint venture denition that you want to add theinterested party stakeholder to.

2. On Edit Joint Venture, click the Stakeholders tab on the left.3. Click Add (+ icon) to add a stakeholder.4. On Create Stakeholder, enter a name and an optional description for the stakeholder and click Save.5. For the Stakeholder Type, select External or Internal to indicate if the interested party is external or internal to

the managing partner’s organization.The status for new stakeholders is Pending. You can’t change it to Active until after you complete the eldsunder Partner Information.

26

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAUDM2842327



Note: The Stakeholder Category eld is an optional eld that contains user-dened values that yourcompany can set up to further categorize your stakeholders to make them easier to manage.

6. Under Partner Information, select “None – Interested party only.”7. Click the Party drop-down list and select the party for this stakeholder.

The system displays the related party information in the eld below and includes any additional details ifavailable.


Activate a Stakeholder After you set up stakeholders, you can change the status for each stakeholder to Active. The Active status enables youto add the stakeholder to an ownership denition, where you dene the stakeholder’s percentage of ownership in thejoint venture.

Set Up Ownership Denitions An ownership denition provides the information Joint Venture Management uses to calculate the split of costsand revenue to distribute among joint venture partners. It contains a list of the stakeholders and each stakeholder’spercentage of ownership. The ownership percentages for all stakeholders in an ownership denition must total 100%before you can change its status to Active. The Active status enables Joint Venture Management to use the ownershipdenition to process transactions for a joint venture.

An ownership denition includes an eective date range. For Joint Venture Management to process transactions, thedate in the transactions must coincide with the eective dates in the ownership denition.

You can create multiple instances of an ownership denition with the same name, as long as the eective dates in eachinstance don't overlap. This enables you to specify dierent stakeholder percentages for dierent periods of time asagreed upon in the joint operating agreement.

In the joint venture denition, you must designate one ownership denition as the default before you can set the jointventure denition to Active. This default ownership denition is assigned to all transactions that are identied for thejoint venture in the Transactions work area. In the Transactions work area, you can override the default ownershipdenition with a dierent ownership denition. This gives you the ability to set up a default ownership denition thatcovers a majority of the transactions, while having other ownership denitions to cover the split of other costs orrevenue streams.

Rounding Partner You must designate one stakeholder in an ownership denition as the rounding partner. When calculating the split of atransaction, any amount that remains is added to or subtracted from the rounding partner's amount. This ensures thatthe split amounts total the gross amount in the transaction. Typically, the managing partner is the rounding partner, butyou can make any stakeholder the rounding partner.

If you don’t select a rounding partner, the system automatically designates the internal stakeholder with the largestpercentage of ownership as the rounding partner. If there are no internal stakeholders, the system designates theexternal stakeholder with the largest percentage as the rounding partner.

Example of a Rounding PartnerJoint venture ABC has four stakeholders, each with an equal 25% interest. An expense of 301.50 USD must bedistributed among the stakeholders. When you divide 301.50 USD equally among the four stakeholders, you get 75.375

27



USD. The system uses the rounding partner to be able to split the amounts as evenly as possible, while still being able tocreate distributions with valid amounts. In this scenario, the system would create distributions to three of the partnersfor 75.38 USD, and create an invoice to the rounding partner for 75.36 USD. The total of these four invoices is 301.50USD.

Partners Calculation Distribution Amount

Partner 1 301.50 x .25 = 75.375 75.38

Partner 2 301.50 x .25 = 75.375 75.38

Partner 3 301.50 x .25 = 75.375 75.38

Partner 4 (rounding partner) 301.50 x .25 = 75.375 = 75.38 - .02(rounding adjustment)

75.36

Total 301.50

Ownership Denition Statuses An ownership denition has the following statuses:

• Pending. The initial status when you set up an ownership denition.

• Active. Enables the joint venture to use the ownership denition to calculate the split of transactions. You canonly change an ownership denition to Active when the ownership percentages for all stakeholders total 100%.

• Inactive. This status is used when you no longer want the joint venture to process transactions with theownership denition.

Example of Processing Transactions with a Default Ownership Denition A joint venture accountant created an ownership denition named VENTUREOD1 and assigned it as the defaultownership denition for the joint venture. She created three dierent instances of VENTUREOD1, and each instance hassuccessive eective dates that don't overlap. She created the three instances to account for variances in stakeholderownership percentages from one month to the next, as shown in the following table:

Default Ownership Denition Eective Dates Ownership Percentages

VENTUREOD1 1/01/2019 - 1/31/2019 4 stakeholders, 25% each



Over the course of three months, from 1/01/2019 to 3/31/2019, 10 transactions (T1-T10) are identied for the jointventure in Joint Venture Management. Based on the date in each transaction, Joint Venture Management associates thedefault ownership denitions to the transactions, as shown in the following table:

Note: For illustration purposes, this example shows only 10 transactions, but transactions could potentially bein the thousands.

Transaction Transaction Date Default Ownership Denition Instance

T1 1/11/2019 VENTUREOD1 1/01/2019 - 1/31/2019

28



Transaction Transaction Date Default Ownership Denition Instance

T2 1/16/2019 VENTUREOD1 1/01/2019 - 1/31/2019

T3 1/31/2019 VENTUREOD1 1/01/2019 - 1/31/2019

T4 2/02/2019 VENTUREOD1 2/01/2019 - 2/28/2019

T5 2/13/2019 VENTUREOD1 2/01/2019 - 2/28/2019

T6 2/22/2019 VENTUREOD1 2/01/2019 - 2/28/2019

T7 2/22/2019 VENTUREOD1 2/01/2019 - 2/28/2019

T8 2/27/2019 VENTUREOD1 3/01/2019 - 3/31/2019

T9 3/14/2019 VENTUREOD1 3/01/2019 - 3/31/2019

T10 3/14/2019 VENTUREOD1 3/01/2019 - 3/31/2019

After the transactions are identied, the process is run to calculate the split of each transaction. Joint VentureManagement calculates the split of each transaction according to the ownership percentages dened in each ownershipdenition instance, as shown in the following table:

Transaction Default Ownership Denition Instance Ownership Percentages Used for the Split

T1 - T3 VENTUREOD1 1/01/2019 - 1/31/2019 4 stakeholders, 25% each



Example of Overriding the Default Ownership Denition A joint venture accountant needs to create ownership denitions to calculate splits based on certain conditions inthe joint venture operating agreement (JOA). The managing partner uses two cost centers, Cost Center A and CostCenter B, to manage the nancials for the joint venture. The majority of transactions will be applied to Cost Center A,with a small subset of transactions to be applied to Cost Center B. In accordance with the conditions in the JOA, theaccountant creates the following ownership denitions for the rst three operating months of the joint venture:

• A default ownership denition for spliing the majority of transactions in Cost Center A. She creates threedierent versions of the default ownership denition to account for variances in stakeholder ownershippercentages in each month.

• An ownership denition for spliing transactions from Cost Center A that contain expense amounts over 25thousand.

• An ownership denition for spliing transactions in Cost Center A that contain a revenue amount under 5thousand.

• An ownership denition for spliing transactions from Cost Center B.

The following table provides more details about each ownership denition:

Ownership Denition Eective Dates Default – Y/N

Purpose

VENTUREOD_COSTCENTER_A 1/01/2019 – 1/31/2019 Yes Process splits of transactions with aJanuary date for Cost Center A, with

29



Ownership Denition Eective Dates Default – Y/N

Purpose

the following ownership percentagebreakdown: 4 stakeholders, 25% each

VENTUREOD_COSTCENTER_A 2/01/2019 – 2/28/2019 Yes Process splits of transactions with aFebruary date for Cost Center A, withthe following ownership percentagebreakdown: 5 stakeholders, 20% each

VENTUREOD_COSTCENTER_A 3/01/2019 – 3/31/2019 Yes Process splits of transactions with a Marchdate for Cost Center A, with the followingownership percentage breakdown: 4 stakeholders, 25 % each

VENTUREODCCA_EXP_OVER25K 1/01/2019 – 3/31/2019 No Use as an override to process splits oftransactions from Cost Center A withexpenses over 25 thousand. Includesthe following ownership percentagebreakdown: 2 stakeholders, 50/50 split

VENTUREODCCA_REV_UNDER5K 1/01/2019 – 3/31/2019 No Use as an override to process splitsof transactions in Cost Center A withrevenue under 5 thousand. Includesthe following ownership percentagebreakdown: 2 stakeholders, 50/50 split

VENTUREOD_COSTCENTER_B 1/01/2019 – 3/31/2019 No Use as an override to process splits oftransactions in Cost Center B. Includesthe following ownership percentagebreakdown: 2 stakeholders, 70/30 split

After the transactions are identied, the accountant uses the Transactions work area to search for transactions thatneed to be split by ownership denitions other than the default. The following table shows the transactions shesearches for and the ownership denition she assigns to the transactions:

30



Transactions Ownership Denition Assigned

Cost Center B VENTUREOD_COSTCENTER_B

Cost Center A with expenses over 25 thousand VENTUREODCCA_EXP_OVER25K

Cost Center A with revenue under 5 thousand VENTUREODCCA_REV_UNDER5K

Create an Ownership Denition 1. On the Joint Ventures page, click the joint venture denition that you want to add an ownership denition to.2. On Edit Joint Venture, click the Ownership Denitions tab on the left.3. Click Add.4. On Create Ownership Denition, complete the Ownership Denition Name and Description.

Use all upper case characters with no spaces for the name. If you don’t, the system will adjust the nameaccording to this convention.Typically, you’ll set up multiple ownership denitions for a joint venture. So try using a name and descriptionthat makes each denition easy to identify.

5. Save the ownership denition.Notice that the default status for an ownership denition is Pending. After completing the ownership denition,you must change it to Active for it to be used by the joint venture denition.

6. To add a stakeholder and their ownership percentage, click Add (+ icon) in the upper left corner of the grid. Andthen complete the following information in the row:

◦ Stakeholder Name. Select a stakeholder from the drop-down list.The list includes only the stakeholders that have been added to the joint venture denition and have astatus of Active.

◦ Percentage of Interest. Enter the stakeholder’s ownership percentage. The percentage can include up to14 decimal places.

◦ Rounding Partner. You must select one stakeholder as the rounding partner. The rounding partnerreceives the extra cost or revenue that remains after the split is calculated. Typically, the managingpartner is the rounding partner, but you can make any stakeholder the rounding partner.

Note: If you don’t select a rounding partner, the system automatically designates the internalstakeholder with the largest percentage of ownership as the rounding partner. If there areno internal stakeholders, the system designates the external stakeholder with the largestpercentage as the rounding partner. If all percentages are the same, the system selects the rststakeholder in the list.

◦ Distribution Only. This seing is inherited from the stakeholder, but you can override it here. Select if thestakeholder only participates in the transaction distribution and is not invoiced.

7. Repeat the preceding step until all stakeholders are added and their ownership percentages total 100%, asindicated by the Total Ownership Percentage gauge.If you have a stakeholder that's currently not partaking in the share of transactions, you can still add them andenter 0 for the ownership percentage.

8. At this point, you can:

◦ Save and close the ownership denition.

◦ Save it and create another ownership denition.

31



Note: Remember that the ownership denition can’t be used by the joint venture denition until you changeits status to Active.

Activate an Ownership Denition You must change the status of an ownership denition to Active to enable it to be used by a joint venture denition.

Before you can change the status to Active, the ownership percentages for all stakeholders in the ownership denitionmust total 100%.

In the joint venture denition, access the ownership denition and change the status to Active, and then save it.

After changing the status to Active, you can only update the ownership denition if it hasn’t been used by the jointventure to process transactions. For more information about the changes you can make to an ownership denition, seeUpdate an Ownership Denition.

Specify the Default Ownership Denition for a Joint Venture You can have multiple ownership denitions, but you must designate one ownership denition as the default. In theJoint Venture Transactions work area, you can manually assign ownership denitions to transactions that you don'twant processed by the default ownership denition. All transactions without ownership denitions manually appliedto them will be processed by the default ownership denition. For the default, it's recommended that you choose anownership denition that covers the split of the majority of transactions in the joint venture, if possible.

1. Access the Details page for the joint venture denition.2. Select a default ownership denition from the Default Ownership Denition Name drop-down list. Only

ownership denitions with a status of Active appear in the list.

Approve a Joint Venture (optional) Approval of a joint venture denition is optional. You don’t have to approve a denition before activating it. But you canuse the approval feature if your business process requires it.

On the Details page of the joint venture denition, enable the Approved toggle. When enabled, the Approved Dateappears with today’s date. You can change the date if the denition was approved on a prior date and you want tocapture this information for your records.

Activate a Joint Venture When you create a joint venture denition, the default status is Initiated. To enable a joint venture denition to processtransactions for the joint venture, you need to change its status to Active. All required information must be added to thejoint venture denition before you can make it active.

Your system administrator can set up additional user-dened statuses if your business process requires it. For example,you can add an “On Hold” status to indicate that the current denition shouldn't be made active.

1. On the Joint Ventures page, locate and click the name of the joint venture denition that you want to activate.2. On Edit Joint Venture, change the Status to Active.3. Save the joint venture denition.

32

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAJVUjvdef_update_ownership_definition


Chapter 7Schedule or Run ESS Processes for Joint Venture

Management

7 Schedule or Run ESS Processes for JointVenture Management

Schedule or Run Joint Venture Management ESSProcesses

About Joint Venture Management Processes in Oracle EnterpriseScheduler Use Oracle Enterprise Scheduler, also referred to as the Enterprise Scheduler Service (ESS), to schedule and run theseESS processes for Joint Venture Management:

• Identify Joint Venture Transactions

This process uses the details in joint venture denitions, specically the distributable segment values, toidentify transactions for processing. The process ensures transactions previously identied and processed byJoint Venture Management aren't processed again.

• Create Joint Venture Distributions

This process calculates the split of transactions and generates distribution records. It uses the details injoint venture denitions, specically the stakeholder ownership percentages, to calculate the split and createdistributions.

You can also run these processes on demand if you need to reprocess transactions to resolve disputes over distributedamounts or correct other issues. See Correcting Issues with Joint Venture Transactions and Distributions for someexample scenarios.

Schedule or Run Joint Venture Management ESS Processes

Note: Only joint venture denitions with an Active status are recognized by the ESS processes.

1. From the Navigator, select Scheduled Processes.2. On the Scheduled Processes page, click Schedule New Process.3. On the Schedule New Process dialog box, select Job as the Type.4. Search for one of these Joint Venture Management processes, select the process, and then click OK:

◦ Identify Joint Venture Transactions

◦ Create Joint Venture Distributions

5. On the Schedule New Process dialog box, click OK.

33

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FAJVUmanage_correcting_issues_with_transactions_and_distributions


Chapter 7Schedule or Run ESS Processes for Joint Venture

Management6. On Process Details, determine when you want to run the process:

◦ As soon as possible. This is the default.

◦ On a schedule. Click Advanced to set up a schedule for running the process. This displays the AdvancedOptions, where you can create a schedule and set up a notication so you or another user are notiedabout the process.

7. Complete the parameters for the process:

◦ Joint Venture. You can select a particular joint venture or leave it blank if you want the process to executeover all joint ventures. A joint venture must be in an Active status to be processed by the ESS process.

◦ Ledger. Enter a ledger in which the transactions to be processed by Joint Venture Managementwere originally recorded. If you leave this blank, the primary ledger associated with the business unitassociated with the joint venture will be used.

◦ Period. Enter the period in which the transactions to be processed by Joint Venture Management wereoriginally recorded. If you leave this blank, the latest open period for the ledger will be used.

8. Click Submit.9. Back on the Scheduled Processes Overview page, you can view a list of submied processes and their statuses.

Click a process in the table to view additional details about the process.


• Scheduled Processes

34

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR191899


Chapter 8Migrate Joint Venture Setup Data to Production

8 Migrate Joint Venture Setup Data toProduction

Migrate Joint Venture Setup Data to Production Oracle recommends that you set up the following joint venture components in a test environment before youimplement them in a production environment:

• Invoicing partners

• Joint venture denitions

You can then test your setup by running the ESS processes that are used to identify and distribute joint venturetransactions, verifying that distribution records were generated successfully. After testing, export the setup data—invoicing partners and joint venture denitions—from a test environment and import the setup data to a productionenvironment.

If you prefer, you can test one or two joint ventures in a test environment, migrate them to production, and then set upyour remaining joint venture denitions directly in production.

These instructions describe how to use an implementation project to migrate joint venture setup data. This approachhelps ensure a successful data migration. For more information about additional features and options for migratingdata, see these topics:

• Setup Data Export and Import Using Implementation Project

• Setup Data Export and Import

Before You BeginYou must have the Application Implementation Consultant(ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) role to create an implementation project andmigrate setup data.

Joint Venture Management is a functional area in the Financials oering. Before you can migrate Joint VentureManagement setup data, you must migrate the Financials oering setup data that is applicable to your implementation.

Create an Implementation Project for Migrating Setup Data 1. From the Navigator, select Setup and Maintenance.2. Select Financials from the Setup list.3. Click the Tasks menu tab on the right side of the page, and select Manage Implementation Projects.4. Click Create (+ icon).5. Enter a name for the implementation project.

The system automatically populates the Code and Description elds. You can revise these elds if desired. Andyou can use the default values for the remaining elds.

6. Click Save and Open Project.7. Add Joint Venture Management tasks to the project:

35





a. Click Select and Add (+ icon).b. Click the Search drop-down list and select Tasks.c. Search for these tasks:

- Manage Invoicing Partners- Manage Joint Venture Denitions

Note: These are the tasks used to set up your joint ventures. As part of the export, thesetask call the business objects that contain your joint venture setup data.

d. Highlight each task and click Apply to add them to the implementation project.e. Click Done.

8. On the Implementation Project page, click Done.

You’ve created your implementation project, which you can use for future data migrations. You don’t have tocreate a new implementation project for each migration.

9. Click Done.

Export Joint Venture Setup Data 1. On the Setup: Financials page, click the Tasks menu tab on the right side of the page and select Manage

Conguration Packages.2. Click Create (+ icon).3. On Create Conguration Package: Enter Basic Information, click the Name drop-down list and select the

implementation project you created in the preceding task.4. For the Export options, select “Setup task list and setup data.”

The system automatically populates the remaining elds, which you can modify if desired.5. Click Next.6. Change the Import Sequence of the business objects. To do so, click the numbers next to the business objects

and arrange them in the following order:

320 – Invoicing Partner

330 – Joint Venture

340 – Joint Venture Stakeholder

350 – Ownership Percentage

When you change a number, simply click Yes in the warning message that appears. You can enter a duplicatenumber until the business objects are in the proper order.

7. Click the Import Sequence column heading to view the business objects in ascending order. Verify that thebusiness objects are in the sequence as shown in this example:

36



8. Click Save and Close.

You’ve created a conguration package, which has a status of “Denition in progress” until you run the processthe rst time.

9. With the row with the conguration package highlighted, click Export Setup Data.10. On the next page, click Submit.11. Scroll down to the Export and Import Processes area which displays the conguration package that you are

exporting.

Here you’ll nd the status of the export. Click Refresh to view the progress until the download of your exportpackage is ready.

12. When the status changes to “Completed successfully,” click the download icon and select DownloadConguration package.

Your browser displays a link to the export package zip.13. Save the zip to your local machine.

37



Remember where you saved the zip so you can locate it when you import the setup data in your targetenvironment.

Import Joint Venture Setup Data 1. In the target environment, select Navigator, Setup and Maintenance.2. Select Financials from the Setup drop-down list.3. Click the Tasks menu tab and select Manage Conguration Packages.4. Click Upload.5. Click Browse and locate the conguration package with the exported setup data.6. Click Get Details and verify the name of the conguration package and the implementation project.7. Click Submit.

If successful, a message appears conrming the upload of the conguration project and implementationproject.

8. Click Yes.

You’ve uploaded the le, but you still need to import the setup data from the uploaded conguration package.9. In the Export and Import Processes area, highlight the uploaded conguration package and click Import Setup

Data.10. On the next page, click Submit.

A new row displays with an initial status of “Not started.” Wait or click Refresh until the status changes to“Completed successfully.”

11. After the import completes, remember to set these values in the imported joint venture denitions:

◦ Select the default ownership denition for the joint venture denition. See Specify the Default OwnershipDenition for a Joint Venture.

◦ Change the joint venture denition status to Active. See Activate a Joint Venture.

38


Chapter 9Manage Joint Venture Management Lookups

9 Manage Joint Venture ManagementLookups

Manage Joint Venture Management Lookups In Joint Venture Management pages, lists of values in drop-down lists are stored as lookups. You can add values tosome of these lookups according to your business process requirements. For example, Joint Venture Managementincludes a Stakeholder Category eld in the page for seing up stakeholders. This is an optional eld for which youcan create user-dened lookup values, or lookups, to further categorize your stakeholders so that they are easier tomanage.

Each list of values (LOV) has its own lookup table. An entry within a lookup table consists of these elements:

• A lookup type identies the table in which a lookup value exists. In eect, it distinguishes lookup valuesbelonging to one LOV from those belonging to others.

• Within a given lookup type, each entry correlates a "lookup code" to a "meaning." The code is an internal value.The meaning is the text that actually appears in a LOV.

• Each entry may also have a description.

You can add values to the following lookup types in Joint Venture Management:

Page Field Lookup Type

Create Invoicing PartnerEdit Invoicing Partner

Status ORA_JV_PARTNER_STATUS

Create Joint VentureEdit Joint Venture

Status ORA_JV_JOINT_VENTURE_STATUS

Create StakeholderEdit Stakeholder

Status ORA_JV_STAKEHOLDER_STATUS

Create StakeholderEdit Stakeholder

Stakeholder Category ORA_JV_STAKEHOLDER_TYPE

To learn about how these lookups are used, see:

• Add an Invoicing Partner

• Enter Joint Venture Details

• Set Up Stakeholders

39


Chapter 9Manage Joint Venture Management Lookups

Create and Edit Lookups To create a lookup:

1. On the Manage Lookups page, select the Create Lookup action. A Create Lookup page opens.2. In the Lookup Type eld, enter the lookup-type that you want to add a lookup to.3. Enter a code in the Lookup Code eld.

A code should consist of 30 or fewer characters, upper-case for alphabetic characters, and no spaces. You canuse an underscore between words instead of spaces.

4. In the Meaning eld, enter text that will appear as a value in the LOV.5. Optionally, describe the lookup in the Description eld.6. Click Save and Close.

To edit a lookup:

1. In the Manage Lookups page, search for the lookup you want to edit. In the Search panel, enter anycombination of type, meaning, and description values, and click the Search buon.

2. In the Search Results panel, click the row for the lookup you want to edit, then select the Edit Lookup action.3. On the Edit Lookup page, modify the meaning or description.

Note: The lookup type and lookup code are presented as read-only values; you can't edit them.

4. Click Save and Close.

40


Chapter 10Integrate and Extend Joint Venture Management

10 Integrate and Extend Joint VentureManagement

Integrate and Extend Joint Venture Management For integration capabilities, Joint Venture Management has a REST API to facilitate the creation, inquiry, update, anddeletion of Joint Venture Management information. This REST API contains resources that enable you to retrieveinformation from Joint Venture Management or manage related information that originates from a third party system.An example of using a REST API is in the oil and gas industry, where companies typically use a third party program tomanage and track the date eective split between joint venture partners. These companies can use a REST API to pulltheir split denitions from their third party program into ownership denitions in Joint Venture Management.

Because Joint Venture Management is a functional area of Oracle Financials, you can nd the Joint VentureManagement REST API documentation in the REST API for Oracle Financials Cloud Reference Guide.

For extensibility purposes, Joint Venture Management is built entirely with the Oracle Visual Builder Cloud Service(VBCS). VBCS is a hosted environment for your application development infrastructure. It provides an open-source,standards-based solution to develop and collaborate on applications within Oracle Cloud. You can use VBCS to extendyour Joint Venture Management implementation. See Oracle Visual Builder for more information.

41

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FARFA

https://www.oracle.com/pls/topic/lookup?ctx=cloud&id=FARFA

https://docs.oracle.com/en/cloud/paas/app-builder-cloud/index.html


Chapter 10Integrate and Extend Joint Venture Management

42

Documents

Management Cloud Oracle Joint Venture€¦ · Joint Venture Management uses the information in the ownership denition to calculate the split of transactions and create distributions