Results for “edr_event_relationship”

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

Overview

The EDR_EVENT_RELATIONSHIP table resides in the EDR schema and is classified under the EDR – E-Records product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the relationship between eRecords, providing the persistent linkage structure that connects one electronic record (the parent) to another (the child). This table is central to hierarchical and associative modeling of eRecords, allowing the EDR framework to represent parent-child dependencies, lineage, and event correlation without duplicating the underlying record content itself.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as a standalone entity rather than a strict Data Vault hub, link, or satellite. As a modeling suggestion, this classification reflects that the table is not governed by an inferred foreign-key data vault topology; instead it acts as a self-contained relationship register whose semantics are driven by the event name and event key pairs it carries. The absence of enforced FK relationships in the documented schema reinforces its role as a lightweight, decoupled association table.

Key Information Stored

The table contains twelve documented columns. The most significant are summarized below:

• RELATIONSHIP_ID — The surrogate primary key, enforced by the unique index EDR_EVENT_RELATIONSHIP_P. Uniquely identifies each relationship row.
• PARENT_ERECORD_ID and CHILD_ERECORD_ID — Business-key candidates forming the unique index EDR_EVENT_RELATIONSHIP_U. Together they define the parent and child eRecord participating in the relationship.
• PARENT_EVENT_NAME, PARENT_EVENT_KEY, CHILD_EVENT_NAME, CHILD_EVENT_KEY — Descriptive identifiers that qualify the parent and child events the eRecords belong to, enabling relationship resolution by event context rather than by numeric ID alone.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard EBS audit columns tracking who created and last modified each relationship.

The surrogate key (RELATIONSHIP_ID) provides internal referential stability, while the composite unique key (PARENT_ERECORD_ID, CHILD_ERECORD_ID) enforces the business rule that a given parent-child pair may only appear once.

Common Use Cases and Queries

Typical usage centers on reconstructing hierarchies, tracing lineage, and reporting on record dependencies.

• Retrieving children of a parent eRecord:

  SELECT CHILD_ERECORD_ID, CHILD_EVENT_NAME, CHILD_EVENT_KEY FROM EDR.EDR_EVENT_RELATIONSHIP WHERE PARENT_ERECORD_ID = :p_id;

• Finding the parent of a given child:

  SELECT PARENT_ERECORD_ID, PARENT_EVENT_NAME FROM EDR.EDR_EVENT_RELATIONSHIP WHERE CHILD_ERECORD_ID = :c_id;

• Detecting duplicate or invalid relationships by verifying uniqueness of the parent-child pair.
• Joining to event and eRecord tables via the stored event name and event key columns to enrich reports with descriptive attributes.
• Auditing relationship creation trends over time using CREATION_DATE and CREATED_BY.

Because the table is classified as standalone, queries should not assume enforced FK joins; event name and key columns must be matched explicitly.

Related Objects

The documented schema does not expose enforced foreign keys, so related objects are inferred from the event and eRecord identifiers stored:

• eRecord master tables (EDR_ERECORD / related EDR entities) — joined via PARENT_ERECORD_ID and CHILD_ERECORD_ID to resolve record content.
• Event definition tables — referenced through PARENT_EVENT_NAME, PARENT_EVENT_KEY, CHILD_EVENT_NAME, and CHILD_EVENT_KEY.
• EDR_EVENT_RELATIONSHIP_P and EDR_EVENT_RELATIONSHIP_U — the unique indexes governing the surrogate and business keys.
• Standard EBS audit columns — linked conceptually to FND_USER via CREATED_BY and LAST_UPDATED_BY.

Together these objects support a decoupled eRecord relationship framework usable across EDR event processing, reporting, and lineage analysis.