Search Results get_trd_sql

Overview

ISC_DBI_FR_COST_PER_W_TR_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the API classification category OTHER. It belongs to the Oracle Supply Chain Intelligence (ISC) product family, which supplies the embedded Daily Business Intelligence (DBI) dashboards and analytics used by supply chain and logistics personnel. Its specific functional purpose, as indicated by the header comment inside the package body, is to provide the trend query behind the Freight Cost per Unit Weight Report — a DBI analytic that measures transportation spend normalized against shipment weight so that logistics managers can identify cost drift across carriers, lanes, and periods.

The package follows the standard DBI "trend SQL provider" pattern. DBI pages do not embed static SQL; instead, a reporting engine invokes a provider package at runtime, passes the user's page parameter selections into it, and receives back a dynamically composed SQL statement together with its descriptive attributes. This design allows the analytics layer to assemble the query according to the dimensions and filters the user has chosen on the dashboard without redeploying report definitions.

Key Procedures and Functions

The ETRM documentation records exactly one documented program unit in this package, GET_TRD_SQL. It is a procedure rather than a function and is the sole entry point exposed by the package specification; the specification contains no other public declarations.

• GET_TRD_SQL — The trend query provider for the Freight Cost per Unit Weight Report. The documented signature consists of an input parameter collection (the page parameters supplied by the DBI runtime), an output parameter that returns the generated SQL text as a VARCHAR2, and an output parameter collection that returns the query attributes accompanying that SQL. In accordance with DBI conventions, the procedure does not execute the query itself; it only assembles and returns the SQL and its metadata so that the calling BIS query framework can run it against the reporting schema. It is declared with NOCOPY on the OUT parameters, a standard optimization for the potentially large PL/SQL collections returned to the caller.

No private or helper routines are exposed through the package specification, and the documented metadata identifies no additional public procedures or functions.

Tables Accessed

The ETRM metadata records a single referenced table for this package, accessed through an APPS synonym: PLITBLM. PLITBLM is a standard EBS numeric/character translation and lookup helper used throughout the DBI SQL-generation layer, typically for resolving display values and handling localization of lookup codes while a dynamic query string is being built. Its presence here is consistent with the package's role as a SQL text generator rather than a data-access package: the substantive freight cost and shipment weight data used by the report is read by the framework when it executes the returned statement, not by this package directly. Because the dynamic SQL is constructed at runtime, the underlying fact and dimension tables are not statically visible in the package's dependency list.

Usage Notes

This package is not intended for direct invocation by end users or by customer-written code. It is called by the Oracle DBI page framework when a user opens or refreshes the Freight Cost per Unit Weight trend region, with the framework populating the page parameter collection from the current dashboard context and consuming the returned SQL and attribute collections.

• It is not associated with a concurrent program or an Oracle Forms screen; it is an internal provider for the ISC DBI analytics layer.
• Because the returned SQL is assembled at runtime, tailoring typically occurs through the supported DBI page and query configuration rather than by modifying this package.
• The metadata records no other packages referencing this one, confirming that it is a leaf-level provider at the top of the analytics call chain.
• Customizations should avoid direct edits, as the package is patched by Oracle-supplied ISC DBI releases; the header revision string indicates the source file is ISCRGBYS.pls.