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 the Tax Reporting.
Journals are not supported in Tax Reporting at this time. In Data Management, only "data" load types are supported for Tax Reporting applications.
Drill through from an Tax Reporting web form or Oracle Smart View for Office (dynamically linked to Tax Reporting) to Data Management is supported.
Drill through to an Tax Reporting web form from Data Management is only available when Tax Reporting includes a URL that can be called from Data Management.
Drill through functionality is not supported for exchange rates data.
Data loaded from Data Management to Tax Reporting is summarized based on the dimensionality in Data Management, and this summarized data is loaded to Tax Reporting. Any computations or consolidation logic is only performed within Tax Reporting.
The Tax Reporting supports "YTD" data only, and consequently no data is modified when it has been loaded.
When data load rules are executed, there are two export modes for loading data to the target Tax Reporting application:
- Merge—By default, all data load is processed in the Merge mode. If data already existed in the application, the system overwrites the existing data with the new data from the load file. If data does not exist, the new data will be created.
- Replace—The system first clears any existing data in the application for those referenced in the data load file. Then the system performs the data load in Merge mode.
  
  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 Management, use the Check Entity Group option (see Creating Check Entity Groups.)
The "ownership of data" feature in Tax Reporting is not supported in this release.
Oracle Hyperion Financial Data Quality Management, Enterprise Edition can be used as a primary gateway to integrate on-premise and Tax Reporting based applications. This feature enables customers to adapt cloud deployments into their existing EPM portfolio.
The rundatarule command of the EPM Automate utility, which executes a Data Management data load rule based on the start period and end period, can be executed for an Tax Reporting application.
Data Management can be used to move data between service instances. This means you can move data between Tax Reporting applications, or Tax Reporting data to and from other Oracle Enterprise Performance Management Cloud services.
To load data to actual currency rather than entity currency when the currency is fixed, set the currency in the Functional Currency field in the Location option. SeeDefining Locations. You can also add a Currency row in the import format and map it. See Defining the Import Format.
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 FDMEE (onpremise) 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.