Allocation With Static Table Driver Using Two Target Dimensions Assigns Wrong Output Leaf Value (Doc ID 3064705.1)

Last updated on DECEMBER 31, 2024

Applies to:

Symptoms

On PFT 8.1.1.1, it appears that allocation of Static Table Driver with two target dimensions assigns the wrong Output leaf value.

Static table driver is created for 2 source dimensions and 2 target dimensions as below.
t0_id: report_center_id (Dimension id 9)
t1_id: report_gl_account_id( Dimension id 11)

As per the log file, the Allocation process creates a view with the static table driver data. For target (‘T’ Leaf_Type), leaf_1 refers to t0_id ( report_center_id) and leaf_2 has t1_id (report_gl_account_id).
In the Allocation Rule definition, Output debit given as for report_center_id.
Output credit given as for report_gl_account_id

The merge statement of Debit had leaf_1 as "report_center_id", which is expected.
However, the merge statement of Credit had wrongly assigned leaf_1 as "report_gl_account_id", instead of assigning leaf_2 values.
This causes the results to have report_center_id values on report_gl_account_id field in Credit screen, which is incorrect.

As per our understanding, it is assigning output leaf values not according to the matching target dimension but on the basis of ordered by dimension id.
This issue is occurring when static table driver has 2 target dimensions and either debit/credit screen is defined as for only 1 dimension, then its assigning leaf values based on the dimension id order, but not by the matching dimension.

The issue can be reproduced at will with the following steps:

a) Create static table driver with 2 target dimensions (report_center_id =t0, report_gl_account_id=t1)
b) Create static table driver allocation rule referring the above static table driver.
c) Define Debit and credit sections of Output tab of Allocation rule in below manner.
Debit : Report_center_id = <same as table>
Credit: Report_gl_account_id = <same as table>

d) Run the Allocation Rule.
e) You can observe both Report_center_id & Report_gl_account_id dimensions getting the same leaf values of Report_center_id values i.e. leaf_1.
"Report_gl_account_id"(credit) getting values of Report_center_id is wrong.

Changes

Cause

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