Search Results edr_eresparameters_t




Overview
Explore in AI Chat

Overview

EDR_ERESPARAMETERS_T is a table in the EDR (E-Records) product module of Oracle E-Business Suite, residing in the EDR schema. As documented in the ETRM metadata for release 12.2.2 (and applicable to 12.1.1), the table stores user-defined parameters for ORES (Oracle Records and Electronic Signatures). It functions as a configuration repository that allows implementers and administrators to persist name/value pairs governing e-records behavior without modifying application code.

The table carries a documented physical schema of five columns and a single unique index, EDR_ERESPARAMETERS_T_PK, defined on PARAM_ID. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone. That classification suggests the table is best modeled as a standalone hub or reference-style structure rather than as a link or satellite dependent on a parent business entity, since no enforced foreign-key dependencies to other EDR tables are documented.

Key Information Stored

The documented column set is compact, and each column contributes directly to the parameter-resolution model:

  • PARAM_ID — The surrogate primary key, enforcing uniqueness through EDR_ERESPARAMETERS_T_PK. It is the sole documented business-key candidate via the unique index on this column.
  • PARENT_ID — Identifies the owning record or context to which the parameter applies, enabling parameters to be scoped to a specific parent rather than defined globally.
  • PARENT_TYPE — A discriminator that qualifies the meaning of PARENT_ID, distinguishing the category of parent entity against which the parameter is resolved.
  • PARAM_NAME — The user-defined parameter identifier. Together with the parent context, this column drives lookup behavior when the ORES engine resolves configuration.
  • PARAM_VALUE — The stored value assigned to the named parameter, holding the effective setting consumed by ORES processing.

The absence of audit columns such as creation or last-update metadata in the documented schema indicates the table is treated as a straightforward keyed parameter store rather than a transactional or history-tracking entity.

Common Use Cases and Queries

Typical usage centers on retrieving the effective value of a named parameter for a given parent context, or enumerating all parameters configured for a parent type during setup and migration activities.

  • Retrieve a specific parameter by name: SELECT PARAM_VALUE FROM EDR.EDR_ERESPARAMETERS_T WHERE PARAM_NAME = :name;
  • List all parameters scoped to a parent: SELECT PARAM_NAME, PARAM_VALUE FROM EDR.EDR_ERESPARAMETERS_T WHERE PARENT_ID = :id AND PARENT_TYPE = :type;
  • Audit configuration coverage by group: SELECT PARENT_TYPE, COUNT(*) FROM EDR.EDR_ERESPARAMETERS_T GROUP BY PARENT_TYPE;

These patterns support implementation reviews, environment comparison between development and production, and troubleshooting when ORES behavior diverges from expectations because a parameter is missing or carries an unexpected value.

Related Objects

The documented metadata records no enforced foreign keys, consistent with the standalone classification. Related objects are therefore best identified through the ORES processing layer and the parent entities implied by PARENT_ID and PARENT_TYPE rather than through declarative constraints:

  • EDR_ERESPARAMETERS_T_PK — The primary-key index that guarantees uniqueness of PARAM_ID and underpins all point lookups.
  • ORES configuration and signature-processing objects in the EDR schema — Consumers that read PARAM_NAME and PARAM_VALUE at runtime.
  • Parent entities referenced by PARENT_ID/PARENT_TYPE — The logical owners whose identity is recorded but not enforced by database constraints.

Because referential integrity is not enforced, joins to parent tables must be validated by application logic and PARENT_TYPE filtering.