My Oracle Support Banner

PFT – Static Table Driver Allocation Swap Leaf Codes When Static Table Driver Has More Than One Dimension (Doc ID 2873036.1)

Last updated on APRIL 02, 2024

Applies to:

Oracle Financial Services Profitability Management - Version and later
Information in this document applies to any platform.
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Analytical Application Infrastructure (OFSAAI)
Oracle Financial Services Enterprise Performance Management (EPM)


On : version, PFT static table driver allocation swap leaf codes

Sometimes the target dimensions are not properly updated, the process insert into leaf1 the values from leaf2 and vice versa as per below example:

The Allocation process use a static table driver. This static table driver has one source dimension (18) and two target dimensions(3 and 17)

Dimension 3 (common coa) is the T0
Dimension 17 (segment) is the T1

As per the log file, the Allocation process create a view with the static table driver data. For target (‘T’ Leaf_Type) the leaf_1 refers to t1_id (segment_id) and leaf_2 has t0_id (common_coa_id)

The merge statement has leaf_1 as common_coa_id, and leaf_2 as segment_id. This cause that results has common_coa_id values on segment_id field, which is incorrect.




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

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