Results for “ieo_svr_params_pk”

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

Overview

The IEO_SVR_PARAMS table resides in the IEO schema (Interaction Center Technology module) and stores the definitional metadata for server parameters consumed by the Oracle EBS Interaction Center and its associated server-side components. Each row describes a single configurable parameter — its name, expected data type, length, associated lookup mechanism, and the business object or subsystem to which it applies. The table functions as a parameter catalog rather than a transactional store, so it is relatively static and typically maintained by administrators or seeded during implementation.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. That heuristic reflects the presence of descriptive, attribute-bearing columns (DATA_TYPE, DATA_LENGTH, LOOKUP_TYPE, PARAM_CONFIG) attached to a stable business key, rather than a pure hub or link of independently identified entities. Modelers designing an analytics layer may therefore treat IEO_SVR_PARAMS as a descriptive satellite keyed by its natural business key, with TYPE_ID acting as a link to the parameter-type dimension.

Key Information Stored

The surrogate primary key is PARAM_ID, enforced through the IEO_SVR_PARAMS_PK constraint. Two unique indexes serve as business-key candidates: IEO_SVR_PARAMS_U1 covers PARAM_ID and ZD_EDITION_NAME, while IEO_SVR_PARAMS_U2 covers TYPE_ID, PARAM_NAME, and ZD_EDITION_NAME. The presence of ZD_EDITION_NAME in both unique indexes indicates that the table participates in edition-based or multi-edition data management, where the same logical parameter can exist across editions.

The most significant columns include:

• PARAM_ID — surrogate primary key uniquely identifying each parameter definition.
• TYPE_ID — foreign key to IEO_SVR_TYPES_B, grouping parameters into parameter types.
• PARAM_NAME — the business name of the parameter; combined with TYPE_ID it forms the natural business key.
• DATA_TYPE and DATA_LENGTH — the expected value type and size for parameter values.
• LOOKUP_TYPE and LOOKUP_PROCEDURE — define whether values are derived from a lookup or generated by a PL/SQL procedure.
• OBJECT_CODE — foreign key to JTF_OBJECTS_B, tying the parameter to a specific business object.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for row-level access control.
• PARAM_CONFIG — configuration payload associated with the parameter.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve listing parameters for a given type or business object, validating lookup configuration, and auditing parameter changes over time. Because actual parameter values are held in IEO_SVR_VALUES, joins between the two tables are the most common access pattern.

• Parameter catalog by type: SELECT p.param_id, p.param_name, p.data_type, t.type_name FROM ieo.ieo_svr_params p JOIN ieo.ieo_svr_types_b t ON p.type_id = t.type_id ORDER BY t.type_name, p.param_name;
• Parameters and their current values: SELECT p.param_name, v.value FROM ieo.ieo_svr_params p JOIN ieo.ieo_svr_values v ON v.param_id = p.param_id WHERE p.object_code = :object_code;
• Audit of recent definition changes: SELECT param_name, last_updated_by, last_update_date FROM ieo.ieo_svr_params WHERE last_update_date > :since ORDER BY last_update_date DESC;
• Lookup-driven parameter inventory: SELECT param_name, lookup_type, lookup_procedure FROM ieo.ieo_svr_params WHERE lookup_type IS NOT NULL;

Related Objects

IEO_SVR_PARAMS participates in a set of tightly coupled reference tables:

• IEO_SVR_TYPES_B — parent table of parameter types; joined via TYPE_ID.
• IEO_SVR_VALUES — child table holding parameter values; joined via IEO_SVR_VALUES.PARAM_ID = IEO_SVR_PARAMS.PARAM_ID.
• JTF_OBJECTS_B — defines the business objects referenced by OBJECT_CODE.
• FND_SECURITY_GROUPS — supplies the security grouping referenced by SECURITY_GROUP_ID.
• Standard WHO audit columns align with FND dictionary conventions used across the EBS schema.

Together these relationships confirm that IEO_SVR_PARAMS acts as the central definitional anchor for server-side parameter configuration within the Interaction Center Technology stack.