Search Results fii_gl_cost_center_pkg2

Overview

APPS.FII_GL_COST_CENTER_PKG2 is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as an "OTHER" API type. The package forms part of the Financial Intelligence (FII) family of objects, a set of General Ledger reporting and analysis utilities used to populate the Oracle Financial Intelligence dashboards and related performance management views. Its central role is to produce cost center-oriented financial measures — revenue, expenses, cost of goods sold, contribution margin, and operating margin — aggregated at the General Ledger cost center level. These measures are consumed by reporting layers that let management evaluate the profitability and expense behavior of individual cost centers across an enterprise. Because the package is an internal, non-public utility rather than a published open interface, it is invoked by other FII reporting components rather than by external integrations. The object status is VALID in the documented environment, confirming that it compiled successfully against the database on which the metadata was extracted.

Key Procedures and Functions

The ETRM metadata documents seven procedures or functions within the package body. Each returns a cost-center-oriented financial metric used in FII reporting:

• GET_REV_CC — Retrieves revenue amounts aggregated by cost center, providing the top-line income measure for each reporting unit.
• GET_EXP_CC — Returns expense amounts aggregated by cost center, supporting analysis of spending attributable to each cost center.
• GET_COGS_CC — Returns cost of goods sold by cost center, used to derive gross profitability at the cost center level.
• GET_REVEXP_CC — Returns combined revenue and expense figures for a cost center, useful for condensed profit-and-loss style comparisons.
• GET_CONT_MARG — Computes contribution margin, typically revenue less variable costs, by cost center.
• GET_OPERA_MARG — Computes operating margin, typically the result of revenue less operating expenses, by cost center.
• GET_EXP_BY_CAT — Returns expense figures categorized by expense category, allowing expense composition analysis rather than a single aggregate.

No parameter lists are documented in the ETRM extract, so signatures are not restated here. In practice these routines accept a cost center identifier and a period or date range and return a numeric measure, but that detail is not confirmed by the supplied metadata.

Tables Accessed

The documented dependency information shows the package references APPS synonyms for BIS_PMV_PAGE_PARAMETER_TBL, BIS_QUERY_ATTRIBUTES, and BIS_QUERY_ATTRIBUTES_TBL. These are Business Intelligence System (BIS) performance management metadata tables that hold page parameter definitions and query attribute definitions used by the Oracle Daily Business Intelligence and Financial Intelligence reporting framework. The package also depends on FII_GL_UTIL_PKG, a shared FII General Ledger utility package, which likely supplies common GL query and lookup logic, and on the SYS.STANDARD package for base PL/SQL types. The ETRM listing does not enumerate the underlying GL balance or code combination tables directly, because those are accessed through the utility package. No application tables are written by this package; it is a read-oriented reporting utility.

Usage Notes

FII_GL_COST_CENTER_PKG2 is not referenced by any other database object, indicating it is a terminal provider of query logic invoked directly by FII reporting components or dashboard definitions. In a 12.1.1 or 12.2.2 environment it would normally be called from Financial Intelligence dashboard regions, from concurrent programs that materialize FII summary data, or from custom reporting code extending the FII framework. Because it is an APPS-owned internal package with no documented public interface, it should be treated as unsupported for direct customer modification; upgrades or patches may change its internals. Developers extending FII reporting are advised to call the package's functions from their own reporting logic rather than altering the package body itself, and to validate any assumptions about parameter signatures against the actual source in the target instance, since the ETRM metadata does not document them.