Search Results x_custom_output

Overview

APPS.POA_DBI_NEG_PKG is a PL/SQL package that belongs to the Oracle Procurement and Purchasing family of DBI (Daily Business Intelligence) reporting objects. In Oracle EBS 12.1.1 and 12.2.2, DBI dashboards derive their content from dynamically constructed SQL rather than from static views. Each DBI region invokes a package whose procedures return a query string and the associated query attribute metadata at runtime. POA_DBI_NEG_PKG fulfills this role for the negotiation-related procurement dashboard pages, supplying the SQL that drives the status, trend, and detail regions of the Negotiations dashboard.

The package is classified in the ETRM repository as API classification OTHER, meaning it is an internal reporting helper rather than a public business API. Its header carries the version string 120.0 and the comment noship, indicating that it ships as a standard component but is not intended for direct customer invocation. The core design pattern is uniform across all procedures: each accepts an inbound parameter table of type BIS_PMV_PAGE_PARAMETER_TBL and returns an x_custom_sql OUT NOCOPY VARCHAR2 together with an x_custom_output OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL. The x_custom_sql output is the element most frequently referenced in searches, since it is the literal SQL text returned to the DBI runtime engine.

Key Procedures and Functions

The package exposes twelve documented procedures and one documented function. Each SQL-generating procedure follows the standard DBI callback signature and is responsible for a distinct dashboard region:

• STATUS_SQL — builds the query for the negotiation status summary region.
• AWD_STATUS_SQL — builds the query for the awarded negotiation status region.
• AVG_CYCLE_TIME_SQL — builds the query for the average negotiation cycle time region.
• REALIZED_STATUS_SQL — builds the query for the realized savings status region.
• AWD_TREND_SQL — builds the trend query for awarded negotiations.
• AVG_CYCLE_TREND_SQL — builds the trend query for average cycle time.
• PRJ_SVNG_TREND_SQL — builds the trend query for projected savings.
• PRJ_SVNG_LN_TREND_SQL — builds the line-level trend query for projected savings.
• REAL_SVNG_TREND_SQL — builds the trend query for realized savings.
• NEG_PO_TREND_SQL — builds the trend query linking negotiations to purchase orders.
• DTL_SQL — builds the drill-down detail query used by the dashboard detail regions.
• GET_DTL_FILTER — the single documented function, returning filter criteria used to constrain the detail query.

Because the package body is not included in the metadata, individual WHERE-clause logic and column projections are not documented here; only the procedure names, their purposes, and the shared DBI parameter contract are confirmed.

Tables Accessed

The ETRM metadata documents a single table reference: PLITBLM, accessed through an APPS synonym. PLITBLM is a standard purchasing line/location staging table used in procurement reporting contexts. Given that the package produces negotiation dashboard SQL, the generated statements additionally draw on the underlying negotiation and sourcing tables at execution time, but PLITBLM is the only object explicitly recorded in the repository metadata for this package. The package itself does not perform DML; it emits SQL text, so direct read/write activity is limited to whatever the DBI engine subsequently executes.

Usage Notes

POA_DBI_NEG_PKG is invoked by the Oracle Daily Business Intelligence framework rather than by end users directly. When a user opens a negotiation-related DBI dashboard page, the DBI runtime calls the appropriate procedure, passing page parameters, and receives the generated SQL and attribute metadata in return. Because the package is referenced by zero other packages in the ETRM repository, it sits at the leaf of the dependency tree and has no internal callers within the documented metadata.

Customization should not target this package directly. All procedures return SQL through x_custom_sql, and the supported extension mechanism in EBS DBI is to override that output using the framework's custom SQL hooks rather than to modify the seeded package. Any change made to APPS.POA_DBI_NEG_PKG will be lost on patching, and direct modification is unsupported. Customers requiring altered negotiation dashboard behavior should implement the override through the documented DBI customization path and leave the shipped package intact.