An Oracle White Paper January 2018 Oracle Enterprise Performance Management Cloud Extracting YTD Balances from FCCS using Data Management
Disclaimer This document is provided for information purposes and should not be relied upon in making a purchasing decision. The contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. THIS DOCUMENT IS NOT PART OF A LICENSE AGREEMENT NOR CAN IT BE INCORPORATED INTO ANY CONTRACTUAL AGREEMENT WITH ORACLE CORPORATION OR ITS SUBSIDIARIES OR AFFILIATES. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Contents Overview... 3 1. Set Up the FCCS Target Application... 3 2. Application Period Mapping... 5 3. Category Mapping... 7 4. Import Format... 7 5. Setting Up Your Location... 9 6. Defining Data Load Rules for your Income Statement and Balance Sheet Data... 10 7. Defining Source Options for your Load Rules... 13 8. Mapping Data... 14 9. Importing Data into TRCS... 14 10. Batch schedule Option... 14 Example:... 15 1
Introduction Oracle provides market leading EPM cloud applications, including the Financial Consolidation and Close Cloud Service (FCCS), Planning and Budgeting Cloud Service and Tax Reporting Cloud Service (TRCS). Oracle Tax Reporting Cloud Service requires an YTD Trial balance as a starting point for calculating the provision. At this time, period to date (PTD) balances may be extracted from FCCS, but year to date (YTD) amounts are not directly supported when extracting data using Data Management. This document explains a technique to extract YTD balances from FCCS using Data Management. Tax Reporting Cloud Service requires the following information: Income Statement Data (YTD) Balance Sheet Closing Balance data (PTD) In order to get all this from FCCS, follow the steps in this document. 2
Overview Data Management may be used as a method to extract data from each of the EPM cloud services, including FCCS. Data is stored in FCCS as PTD balances, and YTD balances are computed as part of the consolidation process. To pull YTD balances using Data Management, there are specific setup steps that may be used: 1) Set up an FCCS Target Application in TRCS. 2) Set up your period mappings. 3) Set up your Import Format. 4) Set up your Location. 5) Create two load rules for your location (nonstandard setup). The remainder of this document explains the specific setup steps required in Data Management for connecting FCCS to TRCS. Please note that it is assumed that the reader of this document is familiar with Data Management. Specific details in regards to defining artifacts like Locations or Import Formats will not be explained. This document describes how one location can be set up to get the correct data out of FCCS that is required for TRCS. 1. Set Up the FCCS Target Application You must set up one target application to be able to export Trial Balance data export PTD closing balances from the Balance Sheet accounts (normal setup). Create a custom application that can be used as the source for the extracted FCCS data. Here is an example of a custom target application setup: 1. From Data Management 2. Set up tab 3. Target Application menu 4. Click Add to create a new Target application (which will act as a source application). 5. Enter EPM Cloud credentials: (a) URL (b) Administrator s User Name (c) Administrator s Password (d) Domain (if required) (e) Under Type, click Show applications. (f) Under Type, select Consolidation as the type of application. (Consolidation = FCCS) 3
(g) Under Application Name, select the application name (FCCS in this example). (h) Optional: Enter a Prefix. 6. FCCS is now created and displayed at the top part of the screen. 7. Leave all Application Details as is. 8. Save your new Target application (which will act as a source). You should have now at least two target applications: TRCS FCCS 4
2. Application Period Mapping The Application Period Mapping is the artifact that allows the extract of the YTD data by defining a date range that can be used to combine PTD data. For example, if you want to pull YTD data for February, you need to add the PTD amounts for January and February. In the Application Period Mapping screen, you define the period for February with the prior period for December of the prior year so that all PTD data for January and February will be extracted. Assumption: You have already setup the Global Mapping, as displayed below: 1. Set up the Application Mapping for FCCS a. From Data Management b. Select Setup tab c. Select the Period Mapping (integration Setup) d. Select Target Application FCCS. e. Click Add. f. Add all periods to the FCCS target application and enter the Target Period Month and Target Period Year as displayed in the screenshot below. Leave all other values as is. 5
g. Save your changes. You have now created your FCCS period mapping 2. Set up the Application Mapping for TRCS: a. From Data Management b. Select Setup tab c. Select the Period Mapping (integration Setup) d. Select Target Application TRCS e. Click Add f. Add all periods to the TRCS target application and enter the Target Period Month and Target Period Year as displayed in the screenshot below. g. Change the Prior Period Key dates, so that they point to the last period of the prior year. For example, 31/12/2015 (for all FY16 periods) h. Save your changes. You have now created your TRCS period mapping. 6
3. Set up the Source Mapping to map the periods of FCCS to TRCS a. From Data Management b. Select Setup tab c. Select the Period Mapping (integration Setup). d. Select Source Application tab. e. Set the POV to: Source System: EPM Source Application: FCCS Target Application: TRCS Mapping Type: Explicit f. Click Add. g. Add all FCCS source periods to the screen, and add the TRCS target period. h. Save your changes. 3. Category Mapping Ensure that you have also set up a generic category mapping. Should be known. 4. Import Format Define the Import Format to import FCCS data into TRCS, where FCCS is the source and TRCS is the target. a. From Data Management b. Setup Tab c. Select Import Format d. Click Add Import Format e. Provide a logical name. (FCCSImport in this example.) f. Select FCCS as Source. g. Select TRCS as Target. 7
h. Enter a description (optional). i. Save your location details. j. Set your Import_IS_FCCS mappings accordingly: k. Save your changes. 8
5. Setting Up Your Location Set up a location for importing FCCS Data into TRCS: 1. From Data Management 2. Setup Tab 3. Select Locations 4. Click Add location. 5. Provide a logical name. (FCCStoTRCS in this example.) 6. Browse for the correct Import Format (FCCSImport in this example.) 7. Enter a description (optional). 8. Leave all other options as default. 9. Save your location details. 10. Additional location details are added, such as Functional Currency, and Consolidation View. Leave them all as default. 9
6. Defining Data Load Rules for your Income Statement and Balance Sheet Data You need to create two data load rules, one for the Balance Sheet and one for the Income Statement location (which can both run from the same location) to export the correct data from FCCS, then import this into Data Management and then map the data accordingly to TRCS. To start defining your Data Load Rules for the FCCS: a. From Data Management b. Select Workflow. c. Select Data Load Rules. d. Change your POV (bottom of the screen) to the newly created location FCCStoTRCS. e. Click the location in your POV to change it to the following: 10
In this example we work with P2-16 to show the differences between the Income Statement Data and the Balance Sheet Data. Create the first load rule: a. Click Add to add a new load rule. b. Provide a name for the first load rule. (ImportYTDIncomeStatement in this example.) c. Enter a description. d. Set the Target Cube to Consol (TRCS Consol Cube). e. Set the Source Cube to Consol (FCCS Consol Cube). f. Set the category to Actual. g. IMPORTANT: Period Mapping type should be Default. h. Save your changes. 11
The Source Filters are intentionally left blank. See later remark. Create a second load rule: a. Click Add to add a new load rule (second rule). b. Provide a name for the first load rule (ImportPTDBalanceSheet in this example). c. Enter a description. d. Set the Target Cube to Consol (TRCS Consol Cube). e. Set the Source Cube to Consol (FCCS Consol Cube). f. Set the category to Actual. g. IMPORTANT: Period Mapping type should be Explicit. h. Save your changes 12
The Source Filters are intentionally left blank. See later remark. 7. Defining Source Options for your Load Rules You must define source filters for both load rules. These filters are used to export data from FCCS into TRCS. The ImportPTDBalanceSheet data should only include accounts that are truly part of the balance sheet, excluding the Income Statement accounts, which are in FCCS, and also embedded in the Balance Sheet hierarchy. The ImportPTDBalanceSheet should include a filter on the Movement member FCCS_TBClosing to ensure only Closing Balances are imported. The ImportYTDBalanceSheet data should only include accounts and movements that are part of the FCCS Income Statement. It is recommended that you manually point to the correct accounts. This is a onetime effort. It is also recommended that you point only to the Entity Currency currency member, otherwise you will get both Parent Currency and Entity Currency details. The more you limit the source options, the better performance will be. 13
8. Mapping Data Mapping must also be added to your location. The mapping of the Balance Sheet and Income Statement accounts can be part of one mapping. If you need to map the same account to two different targets based on the two rules, use the Apply To Rule ; otherwise, you can leave this blank. 9. Importing Data into TRCS Test the import steps by Executing both rules (one at a time) and validate your import, validate and export steps from the workbench. Be aware that you need to be careful with the Replace option when loading into TRCS because it replaces existing data in your entity, year, period and scenario. If no data is yet available in the Scenario, Year, Period, Entity combination, you can Replace the data of your first rule, and merge the second load. Do not switch the location, but switch the rule if you are manually importing, validating and exporting data to TRCS. 10. Batch schedule Option To load both the Balance Sheet data and the Income Statement data in one go, you can set up a batch for this as well. Note that the batch can only use the Merge load mode; otherwise you will lose the data for the first rule. 14
Example: Parameters: 15
Oracle Enterprise Perofrmance Management Cloud January 2018 Author: Mike Casey and Margaret Reed Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Copyright 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com