Results for “type_param_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.EGO_PUB_PARAMETERS_V is a read-only view in the Oracle E-Business Suite Advanced Product Catalog (EGO) module. It exposes the parameter definitions used by the publication (batch) engine within the Product Catalog, allowing concurrent programs, PL/SQL packages, and custom reporting to interrogate how a given publication type is configured. The view is defined WITH READ ONLY, meaning it carries no DML privileges and serves strictly as a query surface. Because the underlying parameter store uses a generic, data-type-agnostic layout, the view is the canonical entry point for resolving parameter metadata — including the NUMERIC_VALUE column many implementers search for when diagnosing publication behavior.

Underlying Base Objects

The view is defined over a single base object, EGO_PUB_BAT_PARAMS_B, referenced through a synonym in the APPS schema. The trailing _B convention indicates this is the base (non-translated) table; parameter names and descriptive text that require multi-language support would typically reside in an associated _TL table, while the view itself projects only the base columns. The view text is a straightforward pass-through select with no filtering, join, or aggregation:

• TYPE_PARAM_ID, TYPE_ID — identifiers linking a parameter to its owning publication type.
• TYPE, PARAMETER_NAME, DATA_TYPE — categorical and descriptive attributes.
• NUMERIC_VALUE, CHAR_VALUE, DATE_VALUE — the value columns, only one of which is populated per row according to DATA_TYPE.

Key Columns

The DATA_TYPE column governs which of the three value columns is meaningful for a given row. When DATA_TYPE indicates a number, NUMERIC_VALUE holds the operative setting; when it indicates a character or date type, CHAR_VALUE or DATE_VALUE is populated instead. This polymorphic design is a common ETRM pattern and explains why queries filtered on NUMERIC_VALUE frequently return sparse or unexpected results unless they are constrained by DATA_TYPE and TYPE_ID. PARAMETER_NAME supplies the human-readable key, while TYPE_PARAM_ID is generally the primary key of the parameter record and TYPE_ID the foreign key to the publication type definition.

Common Use Cases and Queries

Typical consumers are publication diagnostics, catalog administration reports, and custom concurrent programs that must reproduce or audit a configured batch. A common pattern lists every numeric-typed parameter for a given publication type:

• SELECT type_param_id, type_id, parameter_name, numeric_value FROM apps.ego_pub_parameters_v WHERE data_type = 'NUMBER' AND type_id = :p_type_id;
• SELECT parameter_name, char_value FROM apps.ego_pub_parameters_v WHERE data_type = 'CHAR' AND type_id = :p_type_id;
• SELECT type_id, parameter_name, data_type, numeric_value, char_value, date_value FROM apps.ego_pub_parameters_v ORDER BY type_id, parameter_name;

Because the view is read-only and mirrors the base table directly, it is safe to query in reporting contexts without risk of unintended writes. Implementers troubleshooting a publication frequently begin with the third query to obtain a complete picture of all parameter values, then narrow to NUMERIC_VALUE once the relevant DATA_TYPE is confirmed.