Hierarchy Filter Selects Wrong Node When Running Allocation
(Doc ID 2423955.1)
Last updated on MARCH 10, 2023
Applies to:
Oracle Financial Services Profitability Management - Version 8.0.0 and laterOracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Symptoms
In Oracle Financial Services Profitability Management (PFT) 8.0.5, after loading a Hierarchy, creating a Hierarchy Filter and selecting it in an Allocation, when running the Allocation, no rows are returned. Reviewing the Allocation SQL in the ofspa log in $FIC_DB_HOME/log/FusionApps, the code is referencing the wrong NODE_XX in OFSA_IDT_ROLLUP. For example, the code selects NODE_02 but, in OFSA_IDT_ROLLUP, the actual value exists in NODE_09.
AND GL_ACCOUNT_ID IN
(SELECT LEAF_NODE
FROM OFSA_IDT_ROLLUP
WHERE OFSA_IDT_ROLLUP.SYS_ID_NUM = 202940
AND (OFSA_IDT_ROLLUP.NODE_02 IN
(SELECT REV_HIERARCHY_FILTER.LEAF_NODE
FROM REV_HIERARCHY_FILTER
WHERE REV_HIERARCHY_FILTER.SYS_ID_NUM = 210816
AND REV_HIERARCHY_FILTER.HIERARCHY_LEVEL = 3
) )
)
In this example, you expect the Allocation SQL to reference NODE_09 and for it to find rows when executing.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |