1. Administering Data Integration for Oracle Enterprise Performance Management Cloud
  2. Data Integration
  3. Using EPM Cloud Business Processes in Data Integration
  4. Customers Using Tax Reporting

Customers Using Tax Reporting

For those Oracle Hyperion Tax Provision customers moving to Tax Reporting, note the key differences:

  • Balance data or exchange rates may be loaded to the Tax Reporting application using a file. (Data and exchange rates cannot be loaded by way of the same file.) In addition, balance data from the Oracle Financials Cloud may also be directly integrated to the Tax Reporting application. At this time, exchange rate loading from the Oracle ERP Cloud is not supported.

  • Data is loaded to Tax Reporting at the summary account level. Line-item detail is not supported in Tax Reporting.

  • Journals are not supported in Tax Reporting at this time. In Data Integration, only "data" load types are supported for Tax Reporting applications.

  • Drill through from a Tax Reporting web form or Oracle Smart View for Office (dynamically linked to Tax Reporting) to Data Integration is supported.

  • Drill through to a Tax Reporting web form from Data Integration is only available when Tax Reporting includes a URL that can be called from Data Integration.

  • Drill through functionality is not supported for exchange rates data.

  • Data loaded from Data Integration to Tax Reporting is summarized based on the dimensionality in Data Integration, and this summarized data is loaded to Tax Reporting. Any computations or consolidation logic is only performed within Tax Reporting.

  • Tax Reporting supports "YTD" data only, and consequently no data is modified when it has been loaded.

  • Tax Reporting customers can extract dynamic calculated values by selecting the All Data option in Direct Integration Options (for more information, seeDefining Direct Integration Options). It is a Data Integration prerequisite that the CONTROL TO-DATE VIEW STORAGE setting in Tax Reporting is enabled, or the Tax Reporting application is DSO (Dense Sparse Optimization enabled application) based, to extract dynamic calculated values. For more information, see Using the Control To Date View Option.

  • The export modes available to Tax Reporting target application are:

    • Merge—If data already existed in the application, the system simply adds values from the load file to the existing data. No existing data is deleted. If data does not exist, new data will be created.
    • Replace —The system first deletes all values based on the scenario, year, period, entity, and data source before it submits the load.
    • Accumulate—Accumulate the data in the application with the data in the load file.
    • Dry Run—Scan a data load file for invalid records without loading data it to the target application. For each unique point of view in the data file, the value from the load file is added to the value in the application.

    Note:

    In Replace mode, before the first record for a specific Scenario/Year/Period/Entity/Mapped Data Source is encountered, the entire combination of data for that Scenario, Year, Period, Entity, and Mapped Data Source is cleared, whether entered manually or previously loaded. Note that when you have a year of data in the Planning application, but are only loading a single month, this option clears the entire year before performing the load.

  • If you need to consolidate all entities as part of the data load process, in Data Integration, use the Check Entity Group option (see Creating Check Rule Groups in Administering Data Management for Oracle Enterprise Performance Management Cloud).

  • The "ownership of data" feature in Tax Reporting is not supported in this release.

  • The rundatarule command of the EPM Automate utility, which executes a Data Integration based on the start period and end period, can be executed for an Tax Reporting application.

  • Data Integration can be used to move data between business processes. This means you can move data between Tax Reporting applications, or Tax Reporting data to and from other Oracle Enterprise Performance Management Cloud business processes.

  • To load data to actual currency rather than entity currency when the currency is fixed, set the currency in the Functional Currency field when creating the integration. See Creating Direct Integrations.

  • You can add a Currency row in the import format and map it. See Mapping Dimensions.

  • After completing a data load cycle in Tax Reporting, data can be written out to a text file created in a custom application for use in an external application, or to an (on-premises) location. When the custom application is defined, you can export the file and download it using EPM Automate.

  • For additional features available to Tax Reporting users, see the contents of this guide.