Oracle Accounting Hub Cloud
What's New
  1. Update 19C
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
    1. Accounting Hub
        1. Drill Down from OTBI Subledger Accounting Reports to Subledger Journal Entry Details
        2. Enhanced Export and Import of Subledger Accounting Setup Data
        3. Delete Imported Accounting Transaction in Accounting Hub
        4. Manage User-Defined Formulas Using Nested Formula Definitions
        5. Valuation Methods for Accounting Hub Cloud Subledgers

Update 19C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
07 JUN 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Join Oracle Cloud Customer Connect

Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!

https://cloud.oracle.com/community

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users in a couple of ways:

Access the Opt In page from the New Features Work Area

  1. Click the Navigator, and then click New Features (under the My Enterprise heading)
  2. On the New Features page, select the offering that includes new features you’d like to review
  3. Click Go to Opt In for any feature you want to opt in
  4. On the Edit Features page, select the Enable option for the feature, and then click Done

or...  Access the Opt In page from the Setup and Maintenance Work Area

  1. Click the Navigator, and then click Setup and Maintenance
  2. On the Setup page, select your offering, and then click Change Feature Opt In
  3. On the Opt In page, click the Edit Features icon for any area that includes features you want to opt in
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may auto enable in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially auto enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

Accounting Hub

Drill Down from OTBI Subledger Accounting Reports to Subledger Journal Entry Details

Enhanced Export and Import of Subledger Accounting Setup Data

Delete Imported Accounting Transaction in Accounting Hub

Manage User-Defined Formulas Using Nested Formula Definitions

Valuation Methods for Accounting Hub Cloud Subledgers

Accounting Hub

Drill Down from OTBI Subledger Accounting Reports to Subledger Journal Entry Details

The action link framework in Oracle Business Intelligence Enterprise Edition (OBIEE) allows you to click on an object and navigate directly to the source application. Using this framework, OTBI Financials provides you the capability to drill from an OTBI ad hoc report, which is based on a Subledger Accounting subject area, to subledger journal entry details.

You can configure links in the ad hoc Subledger Accounting OTBI reports to drill down to the Journal Entry page.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports.  For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

The high level steps to configure a drill down from OTBI ad hoc reports to subledger journal entry details are:   

  • Create an ad hoc report using the appropriate Subledger Accounting subject area
  • Select the column for which you wish to configure the drill down to subledger journal entry details.
  • In Column Properties, set up an action link.

Key Resources

For details on specific drill downs and examples, search for 'How to drill down from OTBI ad hoc reports to transaction details in Oracle Fusion Applications' white paper, soon to be available on Customer Connect at the following URL: https://cloudcustomerconnect.oracle.com/posts/cbb022f02b

Enhanced Export and Import of Subledger Accounting Setup Data

Export and import high volume Subledger Accounting setup data with improved scalability and performance.

The setup export and import services automatically group setup data in batches and generate multiple data files to facilitate migration of high volume setup data.  You can export setup data as a configuration package or a csv file.  Export and import in batches is enabled for the following services:

  • Journal Entry Rule Sets Service
  • Mapping Sets Service
  • Account Rules Service
  • Description Rules Service

For exporting, a single zip file is generated to include all the setup data.  Then you can download the zip file and import it into the target instance. 

If a subledger accounting rule is in both the source and target instance, the rule in the target instance is replaced with the same rule exported from the source instance.  However, when a mapping set is imported to a target instance, the mappings that are already in target instance but not in the source instance remain in the target instance.

The task order for the following task lists are also modified to facilitate export and import in batches.

  • Manage Accounting Rules
  • Define Subledger Accounting Methods
  • Define Accounting Rules for Rapid Implementation
  • Define Transaction Accounts         

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The configuration package exported from a source instance prior to 19C may not be imported to a 19C instance.  Hence, you must first upgrade the source instance to 19C and then export the setup data.  Finally, import the setup data to target instance with same release.

If you are planning to migrate subledger accounting rule setup from one instance to another instance after upgrading to 19C, it is recommended to perform the following steps:

  • To migrate setup using configuration package:
    1. Create a new implementation project, which includes subledger accounting rule set up tasks and set scope to the subledger for which you wish to export the setup.
    2. Create a new configuration package with the new implementation project.
    3. Export setup for the configuration package.
    4. Download the configuration package zip file.
    5. Upload the configuration package zip file to the target 19C instance and import the setup.
  • To migrate setup using csv export:
    1. Export setup component in csv format from the source instance.
    2. Download the csv file.
    3. Upload the setup csv file to the target instance that is also on same release and import the setup data.

Delete Imported Accounting Transaction in Accounting Hub

Automate exception management for transaction processing. Purge transactions that are not successfully accounted by the accounting process via the ERP Integration Web Service.

Submit the Accounting Hub Maintenance process in the Purge Invalid and Unaccounted Transaction mode to delete accounting transactions that are imported into Accounting Hub for a particular ledger and subledger but are not yet accounted successfully. Later, you can import the corrected transaction data again.

You can reuse the same transaction number to import the accounting transaction again after they are purged from Accounting Hub.

Here’s the list of information that gets deleted for eligible transactions:

  • Transaction records in transaction objects.
  • Transaction entity records.
  • Accounting events including reversal event.
  • Invalid journal entries in these ledgers:
    • Primary ledger and associated reporting currencies.
    • Non-valuation method secondary ledgers.
    • Valuation method secondary ledger.
  • Incomplete accrual reversal journal entries.

The process generates:

  • An output file listing the deleted transactions.
  • Two CSV files with transaction header and line details for the deleted transactions. You can then modify the source value as needed and import the accounting transactions again.

The CSV output files have same layout as the updated transaction template introduced with the Flexible Configuration feature.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Fusion Accounting HubNo Longer Optional From: Update 20A

Tips And Considerations

When the Accounting Hub Maintenance process is submitted in the Purge Invalid and Unaccounted Transactions mode, it deletes all eligible transactions for the ledger and subledger in the program parameter. To avoid unintended deletion of unprocessed transaction, run this process only after all the import accounting transaction and create accounting processes are completed for the ledger and subledger.

Manage User-Defined Formulas Using Nested Formula Definitions

Define a formula by using an existing user-defined formula to derive a value for a subledger accounting entry. Define the commonly used formulas and reuse them in other formulas for consistency and ease of maintenance.

For example, to defer revenue recognition for loan origination fee over the life of the loan, you need a formula to prorate the fee amount by number of days in each period.

You must take the total fee amount and divide it by the number of days in the loan life to determine a daily fee amount.  You then multiply the daily fee amount by the number of days since loan origination to generate the prorate fee amount to be recognized by the current period.

 Prorated fee = Fee / Loan duration * Days since origination

First, you need to calculate loan duration and days since origination from the available source.

 Loan duration = Maturity date - Origination date + 1
 Days since origination = Last day of current accounting period - Origination date +1

Where, maturity date and origination date are transaction data from source system, last day of current accounting period is a system source.

Instead of defining one complex formula like this:

Prorated fee = Fee / (Maturity date - Origination date + 1) * (Last day of current accounting period - Origination date + 1)

You can define simple formula to calculate loan duration and days since origination.  Then, use them in the prorated fee formula definition.

  1. Create a user-defined formula to calculate loan duration.  
  2. Create another user-defined formula to calculate days since origination.  
  3. Now, let's create a formula to calculate the prorated fee amount using the above formulas.
  1. In the Expression section of the prorated fee formula,  click the Source button..
  2. Search and select the formula defined in previous steps to define the prorated fee formula.

You can now use the prorated fee formula to derive the entered amount on the fee revenue recognition multiperiod journal line.

The Create Multiperiod Accounting process calculates entered amount for the multiperiod entries as:

Entered amount = Prorated fee - Multiperiod recognized entered amount

Where, multiperiod recognized entered amount is calculated and stored in the Accounting Hub data model as the total amount recognized for the transaction in prior periods.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

In your formula definition, you can’t use a formula that uses another formula.

For example, the following formula is invalid because the formula 'Prorated Fee' already uses another formula 'Loan Duration'.

               Prorated Fee * 10 / 100

Valuation Methods for Accounting Hub Cloud Subledgers

Use different bases of valuing transactions and account them in different ledgers to meet various management reporting and country specific accounting requirements.

Configure valuation method enabled subledgers to allow using different amounts for accounting and creating materially different accounting representations. 

Some popular use cases for using valuation method based Accounting Hub subledgers are:

  1. Valuing financial instruments differently between IFRS and Local GAAPs. 
  2. Representing income or expense differently for management accounting purposes versus statutory reporting purposes.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Fusion Accounting HubNo Longer Optional From: Update 19D

Configure subledger applications to support multiple valuation methods in Manage Subledger Application.

Flag secondary ledgers as valuation method enabled:

  1. From your Accounting Hub Cloud implementation project go to Manage Subledger Accounting Options task after setting the Subledger Application context.
  2. Search for the secondary ledger that should be enabled for valuation method support.
  3. Expand the list of components for the ledger and click on Edit Accounting Options for the subledger application.
  4. Enable the Valuation Method Ledger option.
  5. Finally, run the Update Subledger Accounting Options process for the subledger application.

Tips And Considerations

Enable subledger applications and ledgers for valuation method support before creating any transaction data.

Send transaction feeds separately to secondary ledgers enabled for valuation method.