Search Results poa_dbi_sutil_pkg




Overview
Explore in AI Chat

Overview

POA_DBI_SUTIL_PKG is a PL/SQL package body owned by the APPS schema that provides the shared utility layer for the Oracle E-Business Suite Procurement and Spend Daily Business Intelligence (DBI) dashboards. Its prefix identifies it as a Procurement (POA) DBI helper, and the object is classified as OTHER in the ETRM repository. The package supplies the runtime building blocks required to translate a dashboard page's parameter selections into executable SQL: it resolves security predicates, builds join and aggregation metadata, binds time and request fact values, and assembles the SELECT and WHERE fragments used against the DBI materialized views and views. Because it is a body only, all callable units are internal or package-private, consumed by sibling DBI packages rather than exposed as a public API. The package is VALID in the documented environment and serves both Oracle EBS 12.1.1 and 12.2.2, where the DBI schema and FII (Financial Intelligence) foundation objects are shared across releases.

Key Procedures and Functions

The ETRM metadata documents 37 procedures and functions in total; the units above are the principal documented entries.

Tables Accessed

The package reads security and hierarchy definitions from FII_COMPANY_GRANTS, FII_COST_CENTER_GRANTS, FII_COMPANY_HIERARCHIES, FII_COST_CTR_HIERARCHIES, FII_CC_PMV_AGRT_NODES, and FII_COM_PMV_AGRT_NODES to build security predicates. Time dimension values are resolved from FII_TIME_WEEK, FII_TIME_ENT_PERIOD, FII_TIME_ENT_QTR, and FII_TIME_ENT_YEAR. Organization and supplier context comes from PER_ORGANIZATION_LIST, POA_SUPPLIERS_V, and POA_SUPPLIER_SITES_V. Commodity restrictions are read from PO_COMMODITY_CATEGORIES and PO_COMMODITY_GRANTS. User identity and menu security are obtained from FND_USER, FND_MENUS, FND_APPLICATION, and AK_WEB_USER_SEC_ATTR_VALUES. Logging is written to POA_LOG.

Usage Notes

POA_DBI_SUTIL_PKG is invoked indirectly at runtime by the Procurement and Spend DBI dashboard pages and by the DBI collection and query-generation infrastructure; the metadata records that it is referenced by 22 other packages and that it is not referenced by any database object, confirming it is a top-level consumer rather than a dependency target. It is not intended for direct invocation from forms, concurrent programs, or custom code. Customizations should treat it as internal to the DBI layer; because it is a package body under APPS, any modification risks invalidation across the dependent DBI packages.