Why Does the DIM_GL_ACCOUNT_V View Used to Populate DIM_GL_ACCOUNT Include Node Values?
Last updated on OCTOBER 20, 2017
Applies to:Oracle Financial Services Enterprise Financial Performance Analytics - Version 6.1 and later
Oracle Financial Services Asset Liability Management Analytics - Version 6.1 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
For Oracle Financial Services Asset Liability Management Analytics (ALMBI) and Enterprise Financial Performance Analytics (EFPA) 6.1, why is DIM_GL_ACCOUNT populated in a different manner than the other similar dimension tables? Why does the view used to populate it, DIM_GL_ACCOUNT_V, not include a filter on LEAF_ONLY_FLAG = 'Y'? Why, for each record, does it populate V_GL_PARENT_ACCOUNT_CODE with the immediate parent of the leaf or node, in addition to populating the LEVEL columns?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms