Search Results poa_dbi_ncp_pkg

Overview

APPS.POA_DBI_NCP_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Procurement Operations Analysis (POA) product family, specifically the Database Intelligence (DBI) reporting layer that underpins the Procurement Dashboard and associated HTML-based analytics pages. The package provides the SQL-generation logic required to produce the "NCP" (Non-Conformance/Non-Compliance Procurement) style metrics displayed within the POA dashboard framework. Because it is a package body with no corresponding specification exposed in the dependency listing, it is intended primarily as an internal implementation unit invoked by higher-level dashboard packaging, notably POA_DBI_TEMPLATE_PKG and POA_DBI_UTIL_PKG, which supply the surrounding rendering and parameter-handling infrastructure. The object is marked VALID and does not appear as a dependency of any other database object, confirming its role as a leaf-level report-generator rather than a shared utility.

Key Procedures and Functions

The package body exposes two documented program units:

• STATUS_SQL — Builds the query string that returns the current status classification of the non-conformance procurement metric. It is typically invoked by the dashboard framework to populate the status region of a POA page.
• TREND_SQL — Builds the query string that returns trend data, allowing period-over-period comparison of the same metric. It supports the graphical trend components embedded in POA dashboard pages.

Both units are SQL-string generators rather than data-returning APIs; they assemble dynamic SQL that the calling framework executes against the relevant DBI views. The documented metadata does not expose parameter lists, and none are reproduced here.

Tables Accessed

The ETRM metadata identifies PLITBLM as the referenced table via APPS synonym. PLITBLM is the PL/SQL integer table type used for array-style parameter binding, indicating the procedures assemble and pass collections of bind variables into the generated SQL. The dependency list further shows that the package references several BIS (Business Intelligence System) structures — BIS_PMV_PAGE_PARAMETER_TBL, BIS_QUERY_ATTRIBUTES, and BIS_QUERY_ATTRIBUTES_TBL — which hold dashboard page parameters and query attribute definitions consumed when composing the SQL text. Internal POA packages POA_DBI_SUTIL_PKG, POA_DBI_TEMPLATE_PKG, and POA_DBI_UTIL_PKG are also referenced, supplying shared dashboard utilities.

Usage Notes

POA_DBI_NCP_PKG is not a user-facing API and is not referenced by any other database object, so it is not intended for direct invocation by custom code. It is called at runtime by the POA dashboard rendering framework when a user opens or refreshes a procurement analytics page that includes the NCP status or trend region. Because the package returns SQL text rather than a result set, it executes in the session of the requesting dashboard user and relies on the BIS page parameter collection already being populated. Administrators troubleshooting dashboard query errors should verify that the BIS parameter tables contain valid page definitions and that the POA DBI schema objects are compiled and VALID, since the generated SQL depends on the continued availability of the referenced views and utility packages. The behaviour is consistent across EBS 12.1.1 and 12.2.2, with no release-specific variations documented.