Before you Begin
This 30-minute hands-on tutorial shows you how to create journals using translated input currencies.
Background
Translated input currency journals enable you to enter translated data as line-items in journals and post the values to an input currency member, rather than to Entity Currency. The posted data is stored at the Translated Currency Input member of the Consolidation dimension. During consolidation, if the input currency matches the currency of the entity's parent, the value is copied from the input currency member to the Parent Currency member, without translation. When you use the Translate business rule to translate to reporting currencies, if the input currency matches the reporting currency, the value is copied to the reporting currency without translation. Translated input currency values are not reverse translated to the Entity Currency member, even if the input currency matches the currency for Entity Currency.
What Do You Need?
An EPM Cloud Service instance allows you to deploy and use one of the supported business processes. To deploy another business process, you must request another EPM Enterprise Cloud Service instance or remove the current business process.
- Have Service Administrator access to EPM Enterprise Cloud Service. The instance should not have a business process created.
- Upload and import this snapshot into your Financial Consolidation and Close instance.
- Upload and import this additional snapshot into your Financial Consolidation and Close instance to add the data form used in this tutorial.
Note:
For more information on uploading and importing migration snapshots, refer to the Administering Migration for Oracle Enterprise Performance Management Cloud documentation.Enabling the Translated Currency Input feature
You enable the translated input currency feature using the Setup Wizard during business process creation, or from the Configuration page afterward. Enabling the feature adds the Translated Currency Input member to the Consolidation dimension. In order to enable Translated Currency Input, Journals must be enabled also, either with our without workflow.
- From the Home page, click Application, then Configuration.
- Click Enable Features.
- In the Additional Consolidation Members section, select Translated Currency Input.
- Click Enable.
- At the Confirmation dialog box, click OK.
The enablement process may take 3 or 4 minutes.
- At the completion dialog box, click OK.
- Sign out, and then sign back in.
Creating journals Data Source members
In this section you create a data source member named DS_USD with Journal as source data type, and link it to the the USD input currency. You also add a parent member named Total Journals to organize the Journal source data type members.
Adding members
- On the Financial Consolidation and Close home page, click Application, then Overview.
- Click Dimensions, then Data Source.
- Expand FCCS_Total Data Source, then expand TotalInputAndAdjusted.
- Click
(Add Child), then click Apply.
- Enter these properties for the new member
- Member Name: Total Journals
- Data Storage (Default, Consol, and Rates): Dynamic Cal
- Click Save.
- Move FCCS_Journal Input under Total Journals by changing its Parent Member property from FCCS_TotalInputandAdjusted to Total Journals. Once you've updated the Parent Member, click Save.
- Place the cursor on Total Journals.
- Click
(Add Child), then click Apply.
- Enter these properties for the new member:
- Member Name: DS_USD
- Source Data Type: Journal
- Source Currency Type: USD
- Click Save.
- Click Cancel to close the Edit Member Properties dialog box.
![Add Child](images/AddChild.png)
Refreshing the database
- Select Actions, then Refresh Database.
- Click Create, then click Refresh Database.
- Click Refresh.
- When completed click Finish.
- Click Close, then click Close again.
- Click
(Home) to return to the home page.
Recomputing ownership data
After updating metadata, you may need to refresh the ownership information in the Consolidation page.
- From the Home page, click Application , then Consolidation.
- On the Manage Ownership page, select Actions, and then Recompute Ownership Data.
- Make the selections below, then click Recompute.
- Scenario: Actual
- Year: FY18
- Start Period: Jan
- When completed, click OK.
- Click
(Home) to return to the home page.
Entering translation rates
- From the Home page, click Data.
- In the list of forms, click Enter Exchange Rates - Single Period.
- Verify that the POV is set to Jan, FY18, Actual, and then enter the following rates for CAD to USD:
- Average: .5
- Ending: .75
- Click Save.
- At the Results dialog box, click OK, and then click the x on the Enter Exchange Rates - Single Period tab at the bottom of the page to close the form.
- Click
(Home) to return to the home page.
Creating Translated Currency Input journals
Opening periods
- From the Home page, click Application, and then Manage Periods.
- In the POV, verify that Scenario is Actual and Year is FY18.
- In the Jan row, click the Actions icon and select Open to change the Period status to Opened.
- Click
(Home) to return to the home page.
Creating standard and translated input currency journals
In this section, you create a standard local currency journal that uses the Journal Input Data Source member and the Entity Input Consolidation member. You then create a translated currency input journal that uses the DS_USD Data Source member and the Translated Currency Input Consolidation member. You enter the line-items for this journal in the parent's currency.
- Click Journals to open the Manage Journals page.
- Verify that the POV is set to Actual, FY18, Jan, Periodic, Entity Input.
- Click Create to start a new journal.
- Enter the following journal details:
- Label: Cash Adjs Std
- Journal Type: Regular
- Data Source: Journal Input
- Click Create to add a blank journal line item.
- Enter the following member information. You can type the member names in the field or click the Action menu for the row and select Pick Members to browse the member hierarchy.
- Entity: Legal Entity 0014 (CAD)
- Account: Cash
- Intercompany: No Intercompany
- Movement: Changes in Cash
- Multi-GAAP: Local GAAP
- Product: No Product
- Click Create to add another journal line item. The member information is inherited from the existing line-item. Change the Account member in the new line-item from Cash to Bank1.
- Enter 1000 in the Debit field for Cash and 1000 in the Credit field for Bank1.
- Click Save, and then click Close.
- In the row for the Cash Adjs STD journal, click the Actions icon and select Post from the menu.
- In the Post dialog box, click Post.
The status of the Cash Adjs Std journal on the Manage Journals page changes to Posted.
- In the Manage Journal POV, click Consolidation. In the Select A Member dialog box, select Translated Currency Input (it is under the Entity Total parent) and click OK.
- Click
(Go) to update the POV.
- Click Create to start a new journal.
- Enter the following journal details:
- Label: Cash Adjs Parent Cur
- Journal Type: Regular
- Data Source: DS_USD
Notice that the currency for the journal is set to USD automatically. You assigned this currency to the DS_USD member in the Data Source dimension metadata.
- Click Create to add a blank journal line item.
- Enter the following member information. You can type the member names in the field or click the Action menu for the row and select Pick Members to browse the member hierarchy.
- Entity: Legal Entity 0014 (CAD)
- Account: Cash
- Intercompany: No Intercompany
- Movement: Changes in Cash
- Multi-GAAP: Local GAAP
- Product: No Product
- Click Create to add another journal line item. The member information is inherited from the existing line-item. Change the Account member in the new line-item from Cash to Bank1.
- Enter 750 in the Debit field for Cash and 750 in the Credit field for Bank1.
- Click Save, and then click Close.
- In the row for the Cash Adjs Parent Cur journal, click the Actions icon and select Post from the menu.
- In the Post dialog box, click Post.
The status of the Cash Adjs Parent Cur journal on the Manage Journals page changes to Posted.
Journals created under this POV will be posted to the Translated Currency Input member of the Consolidation dimension.
![Journal POV](images/S0_16_TTCI_POV.png)
Viewing Translated Currency Input data
In this section, you open a form that displays journals data for the Cash account. You compare the entries created by the standard journal to those created by the translated input currency journal.
- Click Data.
- Open the Input Currency Adjustments folder and click Translated Currency Input.
- Scroll the columns until the Journal Input and DS_USD columns for the Data Source dimension are visible and review the journal data.
The form shows journals data for the Cash account. The 1000 from the Cash Adjs Std journal was posted to the Entity Currency member of the Currency dimension for the Journal Input Data Source member and the Entity Input member of the Consolidation dimension. The 750 from the Cash Adjs Parent Cur journal was posted to the USD input currency member of the Currency dimension for the DS_USD Data Source member and the Translated Currency Input member of the Consolidation dimension.
- From the Actions menu, select Business Rules.
- In the list of rules, click Consolidate.
- Enter the following member information, and then click Launch.
- Entity: Legal Entity 0014 (CAD)
- Scenario: Actual
- Period: Jan
- Year: FY18
- At the Information dialog box, click OK.
- Click Refresh to refresh the form data.
- Scroll the columns until the Journal Input and DS_USD columns for the Data Source dimension are visible and review the journal data.
For the Journal Input Data Source member, the 1000 in Entity Input > Changes in Cash > Entity Currency was translated by the average rate ( .5 ) to Entity Input > Changes in Cash > Parent Currency, resulting in a value of 500. The system-defined foreign exchange calculation made an adjustment of 250. in order to adjust the translated value for Closing Balance to the ending rate ( .75 ), resulting in a Entity Input > Closing Balance > Parent Currency value of 750.
For the DS_USD Data Source member, the 750 in Translated Input Currency > Changes in Cash > USD was copied to Translated Input Currency > Changes in Cash > Parent Currency without translation. The system-defined foreign exchange calculation was not applied, so the value in Translated Input Currency > Closing Balance> Parent Currency is also 750.
- From the Actions menu, select Business Rules.
- In the list of rules, click Translate.
- Enter the following member information, then click Launch.
- Reporting Currency: USD_Reporting
- Entity: Legal Entity 0014 (CAD)
- Scenario: Actual
- Period: Jan
- Year: FY18
- At the Information dialog box, click OK.
- Scroll the columns until the Journal Input and DS_USD columns for the Data Source dimension are visible and review the journal data. The reporting currency column is the USD column to the right of the Parent Currency column. (If data is not displayed for reporting currency, you may need to click Refresh.)
For the Journal Input Data Source member, the 1000 in Entity Input > Changes in Cash > Entity Currency was translated by the average rate of .5 to Entity Input > Changes in Cash > USD_Reporting for a value of 500. The system defined foreign exchange calculation made an adjustment of 250 to bring the translated value to the ending rate of .75, resulting in a Entity Input > Closing Balance > USD_Reporting value of 750 .
For the DS_USD Data Source member, the 750 in Translated Input Currency > Changes in Cash > USD was copied to Translated Input Currency > Changes in Cash > USD_Reporting without translation. The system-defined foreign exchange calculation was not applied, so the Translated Input Currency > Closing Balance> USD value is also 750.
Learn More
Creating Journals Using Translated Input Currencies in Financial Consolidation and Close
F48911-01
October 2021
Copyright © 2021, Oracle and/or its affiliates.
This 30-minute hands-on tutorial shows you how to create journals using translated input currencies.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted 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.
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, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, 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 modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted 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 for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates 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 and/or its affiliates. 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 trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. 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. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for 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 applicable agreement between you and Oracle.