Results for “ego_pub_bat_params_b”

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

Overview

EGO_PUB_BAT_PARAMS_B is a configuration table owned by the EGO schema within the Oracle Advanced Product Catalog module. It stores parameter definitions associated with batch or background processing types, where each parameter is typed and can hold a value in one of several physical columns based on its declared data type. The table acts as a metadata registry for parameters that control the behavior of batch programs and processing routines invoked by the catalog subsystems. In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID and is structured as a standalone entity relative to other business tables.

Heuristically the ETRM relationship analysis classifies this table as standalone in Data Vault terms, with a single documented foreign key to IEO_SVR_TYPES_B via TYPE_ID. From a modeling perspective, this suggests a satellite-style structure anchored to a type hub (IEO_SVR_TYPES_B), where the parameter rows describe typed attributes of the parent type. The 14 documented columns reflect this: one surrogate key, one foreign key, and a small number of descriptive and value columns alongside standard audit and concurrency columns.

Key Information Stored

• TYPE_PARAM_ID — the surrogate primary key uniquely identifying each parameter row.
• TYPE_ID — foreign key referencing IEO_SVR_TYPES_B, linking the parameter to its owning batch or server type; this is the primary business-key candidate for grouping parameters by type.
• TYPE — a discriminator describing the parameter category.
• PARAMETER_NAME — the human-readable name of the parameter, typically the most common business-key candidate alongside TYPE_ID.
• DATA_TYPE — indicates which value column is populated (date, character, or numeric).
• DATE_VALUE — holds the value when DATA_TYPE is date-based.
• CHAR_VALUE — holds the value when DATA_TYPE is character-based.
• NUMERIC_VALUE — holds the value when DATA_TYPE is numeric.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns recording who last modified the row and when.
• CREATION_DATE, CREATED_BY — creation audit columns.
• LAST_UPDATE_LOGIN — login identifier of the last updating session.
• OBJECT_VERSION_NUMBER — optimistic concurrency control column used by the EBS framework to detect concurrent updates.

The three polymorphic value columns (DATE_VALUE, CHAR_VALUE, NUMERIC_VALUE) are a recurring EBS pattern that lets a single table store heterogeneous typed values while keeping type information in DATA_TYPE.

Common Use Cases and Queries

Typical usage centers on retrieving and reporting parameter settings for a given batch or server type, and on verifying which parameters are configured before running catalog batch programs.

• List all parameters for a specific type: SELECT parameter_name, data_type, char_value, numeric_value, date_value FROM ego.ego_pub_bat_params_b WHERE type_id = :p_type_id;
• Find parameters by name across all types: SELECT type_id, parameter_name FROM ego.ego_pub_bat_params_b WHERE parameter_name LIKE :p_name;
• Locate numeric-only parameters: SELECT type_id, parameter_name, numeric_value FROM ego.ego_pub_bat_params_b WHERE data_type = 'NUMBER';
• Audit recently changed parameters: SELECT * FROM ego.ego_pub_bat_params_b WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

Reporting on these rows supports configuration review and troubleshooting of batch processing behavior in Advanced Product Catalog.

Related Objects

• IEO_SVR_TYPES_B — the parent type table referenced by TYPE_ID; joining on this column yields the type name and description for each parameter.
• EGO_PUB_BAT_PARAMS_TL — the likely translated sibling table providing language-specific parameter text where used.
• IEO_SVR_TYPES_TL — translation of the type table, useful in multilingual reporting.
• EGO_ITEM_BATCH_PUB / EGO batch APIs — the processing packages that consume parameter values defined here.
• IEO_SVR_Types_VL — the view commonly joined for displaying human-readable type names alongside parameters.

When constructing joins, the reliable path is EGO_PUB_BAT_PARAMS_B.TYPE_ID equals IEO_SVR_TYPES_B.TYPE_ID, filtered by the desired batch or server type.