My Oracle Support Banner

FCCS Data Management Mapping Rules Are Not Executing In Alphabetical Order (Doc ID 2457492.1)

Last updated on OCTOBER 24, 2018

Applies to:

Oracle Financial Consolidation and Close Cloud Service - Version 18.08.49 and later
Information in this document applies to any platform.

Symptoms

While running the Import from Data Management, Mapping rules are not executing in alphabetical order.

Part of the log below shows that execution order was b, c, a. However Order should be a, b, c.

2018-09-03 07:04:31,239 INFO  [AIF]: Data Rows Updated by Location Mapping 'System Generated Map' (LIKE): 0
2018-09-03 07:04:31,239 INFO  [AIF]:
Processing Mappings for Column 'UD5'
2018-09-03 07:04:31,239 DEBUG [AIF]:
             UPDATE TDATASEG_T
             SET UD5X = 'FCCS_ClosingBalance_Input'
                ,UD5R = 30
                ,UD5F = 3
             WHERE LOADID = 36
             AND PARTITIONKEY = 3
             AND CATKEY = 1
             AND (UD5X IS NULL OR UD5X = '')
             AND (UD5 LIKE '1%')
             AND PERIODKEY = '2018-01-31'
2018-09-03 07:04:31,245 INFO  [AIF]: Data Rows Updated by Location Mapping 'b' (LIKE): 135
2018-09-03 07:04:31,245 DEBUG [AIF]:
             UPDATE TDATASEG_T
             SET UD5X = 'FCCS_ClosingBalance_Input'
                ,UD5R = 31
                ,UD5F = 3
             WHERE LOADID = 36
             AND PARTITIONKEY = 3
             AND CATKEY = 1
             AND (UD5X IS NULL OR UD5X = '')
             AND (UD5 LIKE '2%')
             AND PERIODKEY = '2018-01-31'
2018-09-03 07:04:31,249 INFO  [AIF]: Data Rows Updated by Location Mapping 'c' (LIKE): 45
2018-09-03 07:04:31,249 DEBUG [AIF]:
             UPDATE TDATASEG_T
             SET UD5X = 'FCCS_Mvmts_NetIncome'
                ,UD5R = 22
                ,UD5F = 3
             WHERE LOADID = 36
             AND PARTITIONKEY = 3
             AND CATKEY = 1
             AND (UD5X IS NULL OR UD5X = '')
             AND (1=1)
             AND PERIODKEY = '2018-01-31'
2018-09-03 07:04:31,260 INFO  [AIF]: Data Rows Updated by Location Mapping 'a' (LIKE): 261

It is critical that mappings are executed in correct order. Incorrect execution order will result into incorrectly mapped data. This would lead into incorrect data loaded to the application.

Below is copied from Cloud Data Management admin guide:
https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/erpia/erpi_data_rule_map.html

---
When processing the source values for transformations, multiple mappings may apply to a specific source value. The order of precedence is Explicit, Between, In, Multi-Dimension, and Like. Within Between and Like types, mappings can overlap.

The rule name determines precedence within a mapping type. Rules are processed in alphabetical order of the rule name within a mapping type. Numbers may also be used to help with ordering. For example, if numbering by tens or one hundreds, you can insert new rules between existing ones. So if rules are numbered 10, 20, and 30, you can add a rule that starts with 25 and need not rename other rules.

---

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.