1. Implementing Joint Venture Management
  2. Create a Supporting Reference to Capture a Transaction Date

Create a Supporting Reference to Capture a Transaction Date

You must be a user with the Financial Application Administrator role to create supporting references. This role includes the Joint Venture Administrator role, so you can use it to create supporting references and perform other joint venture application administrator tasks.

  1. Navigate to Setup and Maintenance and select the Joint Venture Management functional area under the Financials offering.

  2. Click Show - All Tasks and select Manage Supporting References in the list of tasks.

    Note: This is a shared task that is used by multiple products. It’s not specific to Joint Venture Management.

  3. On the Manage Supporting Reference page, click the Without Balances tab.

    You can set up supporting references with balances or without balances. Because this supporting reference is for a date, use Without Balances.

  4. Click Add Row (+ icon), and in the new row, complete these fields:

    • Name

    • Short Name

      Remember this name because you will need to select this supporting reference later in the Joint Venture System Options.

    • Description

      The following example shows a row for a supporting reference added for a transaction date:

      This image shows one record with the following values in separate columns from left to right: TRANSACTION_DATE, TRANSACTION_DATE, Joint venture transaction date, Active.
  5. With the new supporting reference row selected, scroll down to the Sources area and identify the source of the transaction date for each subledger:

    1. In the Sources area, click Select and Add (+ icon).

    2. On Select and Add: Sources, search for the source by Subledger Application and Event Class. In addition, you can search by Source if you know the name of the source.

      The following example shows the results of searching for a transaction date source in Payables accounts:

      This image shows the Select and Add: Sources section and the Search Results section for the TRANSACTION_DATE supporting reference with this search criteria: Subledger Application = Payables; Event Class = Invoices for the search criteria. The Search Results show five records in a table with Source, Event Class, and Description columns. The records contain the following data respective of the aforementioned columns: Invoice Data, Invoices, Date on the invoice; Invoice Description, invoices, Invoice Description; Invoice Discount Amount Taken, Invoices, Amount of discount taken on the invoice; Invoice Distribution Account, Invoices, Accounting flexfield identifier for account...; Invoice Distribution Accounting Date, Invoices, Invoice Distribution Accounting Date.

    3. Select the source row, which is “Invoice Date” in the preceding example, and click OK.

    4. Continue to add additional sources and related event classes where a transaction date is used.

      The following example shows sources for the transaction date in Oracle Payables and Receivables for various event classes:

      This image shows the Manage Supporting Reference section, which has to tabs: Without Balances and With Balances. The Without Balances tab is selected and contains a Supporting References section, with the focus on the highlighted row for the TRANSACTION_DATE supporting reference. The section below is related to the selected TRANSACTION_DATE row with TRANSACTION_DATE:Sources as the title of the section. The focus of this section is to show two records that show the sources for the selected supporting reference. The table has three columns: Subledger Application, Event Class, and Source. The rows contain the following data respective of these columns: Payables, Credit Memos, Invoice Date; Payables, Debit Memos, Invoice Date, Payables; Invoices, Invoice Date; Receivables, Credit Memo, Transaction Date.

      Next, associate this supporting reference to journal entry rule sets in the Oracle Financials accounting methods as described in the next topic.