My Oracle Support Banner

Why the Global Temp Table (GTT) Query for a Dynamic Driver Allocation Does Not Use Fiscal Month (Doc ID 2626458.1)

Last updated on JANUARY 24, 2020

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.5 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)

Goal

For a Management Ledger Dynamic Driver Allocation, why does the "where" clause used in the creation of the Global Temporary Table (GTT) only reference FISCAL_YEAR but not FISCAL_MONTH?

Example:

Module Logging OFS Access module data: CREATE
CREATE GLOBAL TEMPORARY TABLE GLBL22939TMP ON COMMIT PRESERVE
       ROWS AS
SELECT *
FROM   (SELECT mv.AS_OF_DATE, mv.BALANCE_TYPE_CD, mv.COMMON_COA_ID,
       mv.CONSOLIDATION_CD, DECODE(FISCAL_YEAR, 1999,
       DECODE(mv.ISO_CURRENCY_CD, '', mv.ENTERED_BALANCE,
       mv.ENTERED_BALANCE), ENTERED_BALANCE) ENTERED_BALANCE,
       mv.FINANCIAL_ELEM_ID, mv.FISCAL_MONTH, mv.FISCAL_YEAR,
       mv.FUNCTIONAL_BALANCE, mv.GL_ACCOUNT_ID, mv.IDENTITY_CODE,
       mv.ISO_CURRENCY_CD, mv.LEGAL_ENTITY_ID, mv.ORG_UNIT_ID,
       mv.PRODUCT_ID, mv.STRATEGY_ID
FROM FSI_D_MANAGEMENT_LEDGER mv) m
WHERE FISCAL_YEAR = 2019.000000
AND CONSOLIDATION_CD = 100.000000
AND FINANCIAL_ELEM_ID = 100.000000

FISCAL_MONTH is not included in the WHERE clause.

Solution

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
Goal
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.