Search Results bis_parameter_validation

Overview

BIS_PARAMETER_VALIDATION is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that forms part of the Oracle Business Intelligence System (BIS) — the foundation layer of the EBS Daily Business Intelligence and Embedded Analytics architecture. Its principal business function is to validate, resolve, and materialize the runtime parameters that drive Business Intelligence reporting. When a user launches a DBI dashboard, requests a drill-down, or executes a PMV (Performance Management Viewer) query, the reporting engine must translate the user's declarative selections — a time period, a hierarchy level, a dimension member — into concrete SQL fragments and identifiers that the underlying summary and fact tables can be queried against. BIS_PARAMETER_VALIDATION performs that translation and verification work.

The package is a low-level utility rather than a user-facing API. According to the ETRM metadata for 12.1.1, it is classified as an OTHER API and exposes four documented procedures or functions. It is referenced by four other packages, confirming its role as a shared foundation routine within the BIS schema. In 12.2.2 the package retains the same identity and status (VALID) within the APPS schema.

Key Procedures and Functions

The ETRM metadata documents four callable units. Their names indicate a consistent parameter-resolution theme:

• GETTIMELOVSQL — Returns a SQL fragment (list of values clause) that constrains a query to the appropriate time periods. This supports time-based dimension filtering in DBI and PMV reports.
• DRILLACROSS — Supports the drill-across navigation model, in which a user moves from a summary value to related detail across a different dimension or measure. It resolves the target query context required to satisfy the drill request.
• GETHIERARCHYELEMENTID — Resolves the identifier of a specific element within an analytical hierarchy. This allows reports to address a particular level or node (for example, a cost center within an organization hierarchy) by its internal ID.
• GETDIMENSIONFORATTRIBUTE — Determines which dimension an attribute belongs to, enabling the reporting engine to route attribute-based filtering to the correct dimension table.

The package also exposes its own internal references (BIS_PARAMETER_VALIDATION is listed among its own referencing objects), consistent with private helper routines used by the public procedures.

Tables Accessed

The ETRM excerpt does not enumerate specific tables or APPS synonyms referenced by this package, stating only the dependency on SYS.STANDARD. Its access pattern is nevertheless discernible from the calling context: the four procedures must inspect BIS metadata and dimension definitions — the tables that store hierarchy structures, dimension members, time period definitions, and parameter registry entries — in order to return the SQL fragments and identifiers requested by callers. Because the documented dependency list shows no direct table references, the package most likely resolves its data through the BIS_AUTOINC_SCHEDULE and related packages, or through deferred (dynamic) SQL, which would explain the absence of static table dependencies in the metadata.

Usage Notes

BIS_PARAMETER_VALIDATION is not intended for direct invocation by end users or by ad hoc custom code. It is invoked internally by the BIS reporting stack. The documented referencing objects establish the calling pattern:

• BIS_AUTOINC_SCHEDULE — the schedule maintenance package for Business Intelligence incremental builds.
• BIS_PMV_DRILL_PUB — the public drill-down API for Performance Management Viewer reports.
• BIS_PMV_QUERY_PVT — the private query-construction package for PMV.
• ISC_EDW_O2C_DRILL_P — the Order-to-Cash drill procedure in the Supply Chain Intelligence warehouse.

These callers confirm that the package is exercised during dashboard page rendering, drill-down navigation, and scheduled analytics builds. Because the package resides in the APPS schema and is not a published public API, any custom extension should invoke the higher-level drill and query packages rather than BIS_PARAMETER_VALIDATION directly; doing so preserves compatibility across 12.1.1 and 12.2.2 upgrades, where the internal signatures of utility procedures such as these may change without notice.