Ledger Derivation on Accounting Hub Transaction Import

Automatically derive ledgers during transaction import based on user-defined source mapping sets. The attribute defaulting rule allows you to create a mapping set to map the target attribute, Ledger Name, to one or more header level sources as needed. Deriving valid ledgers from source transaction attributes using configurable rules simplifies the integration when ledger is not provided with transaction data. You can derive both primary and valuation method secondary ledgers using a single attribute defaulting rule to facilitate multiple accounting representations.  

For example, if two attributes, location and reference, in external transaction are used to derive the ledger in Fusion Accounting Hub, then follow these steps to configure the Attribute Defaulting Rule with an attribute mapping set.

1. Navigate to the Attribute Defaulting Rules task from the General Ledger Journals work area.
2. On the Attribute Defaulting Rules page, change the attribute scope and select the subledger application in the Entity field.

   Change scope

   

   Select scope

3. Create a new defaulting rule by selecting target attribute Ledger Name, source attributes Location and Reference, and rule type Mapping Set.

   Create new rule with mapping set as rule type.

4. Enter a valid ledger for each combination of Location and Reference. Use an asterisk(*) to indicate 'any value' for cases with no explicit mappings defined. 

In the below example, if Location is CA and Reference is SL for a transaction, the ledger will be OFS SL – USD.  If Location is CA and Reference is not SL, the ledger will be OFS Ledger US. If Location is Dublin, the ledger will be OFS Ledger GB, regardless of the Reference value.

Attribute Mapping Set

5. Save the mappings and activate the rule in the Attribute Defaulting Rule page before it can be applied during the Import Accounting Transactions process.

   Activate attribute defaulting rule

This feature streamlines transaction processing by removing the need for an external preprocessor to derive a ledger before importing transactions into Fusion Accounting Hub. Users can define and manage derivation rules through a guided, user-friendly interface.

Steps to Enable

Use the following steps to enable the feature:

1. Navigate to Setup and Maintenance.
2. Search and navigate to the Setup Task: Manage Standard Lookups.
3. Search the Lookup Type: ORA_ERP_CONTROLLED_CONFIG.
4. Define the following Lookup Code under above Lookup Type -
   • Lookup Code:  XLA_36529795
   • Enabled: <Checked>
   • Meaning: Ledger Derivation for Accounting Hub Transactions
5. Save the changes.

Tips And Considerations

You can only use this feature with the Flexible Configuration of Accounting Hub Cloud Service End to End Flow feature enabled.

Key Resources

• Based on Idea 789384 from the Subledger Accounting & Accounting Hub Idea Lab on Oracle Cloud Customer Connect.

Access Requirements

To manage rules, users need this privilege added to one of their configured job roles:

• Manage Attribute Derivation Rules (FUN_MANAGE_ATTRIBUTE_DERIVATION_RULES_PRIV)