Search Results get_non_ag_cat_pmv_sql
Overview
FII_GL_UTIL_PKG is a shared utility package in the APPS schema that underpins the Oracle Financial Intelligence (FII) / Daily Business Intelligence (DBI) general ledger analytics layer. Its role is not to perform a single business transaction but to supply the common, reusable services that the FII general ledger family of packages depends upon: resolving view-by and page parameters, constructing PMV (Page Metadata View) SQL fragments, resolving financial hierarchies (cost center, LOB, financial item, category), evaluating manager and supervisor relationships, and returning bitmask and lookup values. In EBS 12.1.1 and 12.2.2 the package is documented as VALID and is classified as a general-purpose API (classification OTHER) rather than a public business API. It exposes fifteen documented procedures and functions and is referenced by twelve other packages, which makes it a central dependency for GL-based FII dashboards and reports.
Key Procedures and Functions
- RESET_GLOBALS — reinitializes package-level global state between invocations to prevent parameter bleed across calls.
- GET_VIEWBY_SQL — returns the SQL text used to drive the view-by selector logic common to FII GL pages.
- GET_NON_AG_CAT_PMV_SQL — builds PMV SQL for category analysis where no assignment group (AG) context applies.
- GET_LOB_PMV_SQL — constructs PMV SQL scoped to line-of-business hierarchy reporting.
- GET_CCC_PMV_SQL — constructs PMV SQL for cost center (CCC) based reporting.
- GET_CAT_PMV_SQL — constructs PMV SQL for category based reporting.
- GET_PARAMETERS — retrieves and interprets the runtime parameters passed to FII GL pages.
- BIND_VARIABLE — helper for binding variables into dynamically assembled SQL.
- GET_BITMASKS — resolves bitmask values used to encode combined parameter flags.
- GET_MGR_PMV_SQL — constructs PMV SQL scoped to manager hierarchy reporting.
- GET_SUPERVISOR — returns the supervisor for a given hierarchy context.
- GET_LOB — resolves the line-of-business value for the current reporting context.
- CCC_WITHIN_MGR_LOB — determines cost centers that fall within a manager's LOB scope.
- GET_FIN_ITEM — resolves financial item hierarchy members.
- GET_FIRST_STRING — utility to return the first non-null string from a set of candidates.
Tables Accessed
- FII_CC_MGR_HIERARCHIES — cost center to manager hierarchy; supports GET_SUPERVISOR and manager PMV SQL.
- FII_COM_CC_MAPPINGS — cost center mappings used when resolving CCC scope.
- FII_FINANCIAL_DIMENSIONS — financial dimension definitions driving view-by and PMV construction.
- FII_FIN_CAT_TYPE_ASSGNS — financial category/type assignments for category PMV SQL.
- FII_FIN_ITEM_HIERARCHIES — financial item hierarchy for GET_FIN_ITEM.
- FII_LOB_HIERARCHIES — line-of-business hierarchy for GET_LOB and LOB PMV SQL.
- FII_TIME_DAY, FII_TIME_WEEK, FII_TIME_ENT_PERIOD, FII_TIME_ENT_QTR — time hierarchy tables backing period, quarter, week and day level reporting.
- DUAL and PLITBLM — utility access for scalar selects and PL/SQL table/bitmap handling.
Dependencies also list BIS_PMV_PAGE_PARAMETER_TBL and BIS_QUERY_ATTRIBUTES_TBL, the DBI/BIS integration tables used to exchange PMV page parameters and query attributes.
Usage Notes
FII_GL_UTIL_PKG is not invoked directly by end users. It is called from within the FII GL analytics packages such as FII_GL_COST_CENTER_PKG, FII_GL_EXPENSE_PKG, FII_GL_PROFIT_AND_LOSS, FII_GL_REV_PROD, FII_GL_TOP_SPENDERS_PKG2, FII_GL_SRC_INV_PKG and FII_GL_CUMUL_REV_TREND_PKG, as well as ISC_DBI_REV_CUM_TREND_PKG and FII_MSG. Because these callers render DBI/FII dashboard regions via the Oracle BIS PMV framework, FII_GL_UTIL_PKG is typically exercised when a user opens or refreshes an FII GL dashboard page. In customizations, the supported approach is to call the specific FII GL page package; calling FII_GL_UTIL_PKG directly is possible but should be treated as an internal interface, as its signature and behavior are not a supported public API. In both 12.1.1 and 12.2.2 the package is reported VALID, with no known issues in the ETRM metadata.