Search Results get_parameters_from_table




Overview
Explore in AI Chat

Overview

APPS.HRI_OLTP_PMV_UTIL_PARAM is a utility package within the Oracle E-Business Suite Human Resources Intelligence (HRMSi) architecture. Its principal responsibility is to consolidate and normalize the runtime parameters that drive Page and Materialized View (PMV) reporting pages in the Oracle HRMSi / Daily Business Intelligence (DBI) framework. These PMV pages present workforce analytics — headcount, turnover, absence, compensation comparisons, and supervisory roll-ups — and require a consistent set of date ranges, comparison periods, currency conversion settings, and organizational filters before any query can be assembled.

The package exposes strongly typed PL/SQL record structures used to pass these parameter values between the PMV engine, the Business Intelligence System (BIS) page layer, and downstream dynamic SQL generators. In Oracle EBS 12.1.1 and 12.2.2 the package remains a compiled, wrapped/obfuscated-style database object owned by APPS, classified as API type "OTHER," indicating it is an internal-support API rather than a public integration interface. It is referenced extensively across the HRMSi PMV code base, with metadata listing dependencies from 48 other packages, confirming its role as a shared parameter-translation utility rather than a user-facing program.

Key Procedures and Functions

  • GET_PARAMETERS_FROM_TABLE — The single documented procedure in the package. It accepts the PMV page parameter table (a BIS page-parameter collection) as input and returns, via NOCOPY OUT parameters, a populated HRI_PMV_PARAM_REC_TYPE record and an HRI_PMV_BIND_TAB_TYPE associative array. The procedure extracts, validates, and maps the raw row-based parameter values supplied by the page into the structured record fields defined at package level and produces the corresponding SQL and PMV bind strings needed to execute downstream dynamic queries.

The package-level type definitions form the contract for this procedure. HRI_PMV_PARAM_REC_TYPE carries current and comparison period start/end dates, page period type, comparison type, supervisor identifier, currency code and rate type, separation/absence attributes, view-by and roll-up flags, week-type key, order-by clause, region code, and a debug header. HRI_PMV_BIND_REC_TYPE pairs a PMV bind string with a SQL bind string, and HRI_PMV_BIND_TAB_TYPE indexes these records by a VARCHAR2 key so that each parameter is bound by name at query execution time.

Tables Accessed

ETRM documentation identifies PLITBLM as the sole referenced table (via an APPS synonym) for this package. PLITBLM is the standard Oracle Applications pl/sql table-driven structure used by forms and PL/SQL utilities to store name/value parameter pairs. The procedure reads this table to obtain the driving parameter set passed from the PMV page context, then decomposes it into the typed record and bind-table outputs described above. No direct DML against transactional workforce tables is documented; persistent data access occurs in the caller, using the bind strings this package produces.

Usage Notes

This package is invoked indirectly. It is not attached to a concurrent program or form directly, but is called by the HRMSi PMV page-processing engine and by the 48 dependent packages that assemble workforce dashboards and reports. Typical invocation follows this pattern: a BIS PMV page request populates a BIS_PMV_PAGE_PARAMETER_TBL, which is passed to GET_PARAMETERS_FROM_TABLE; the returned record and bind table are then consumed by the PMV SQL builder to generate and execute the analytic query.

For customers and partners extending HRMSi, the package matters primarily as a signature-stability concern. Because nearly four dozen delivered packages depend on its record definitions, any custom code that builds or consumes HRI_PMV_PARAM_REC_TYPE or HRI_PMV_BIND_TAB_TYPE must match the delivered structure exactly. Customizations should treat GET_PARAMETERS_FROM_TABLE as a black box, never modify the APPS-owned package in a supported environment, and apply changes only through supported extension points or clones in a custom schema. Consistent with Oracle EBS 12.1.1 and 12.2.2 online patching practice, the object is patched as part of the HRMSi product family and should be validated after any HRMSi or BIS patch application.