Search Results edr_inter_event_test_events_p




Overview
Explore in AI Chat

Overview

EDR_INTER_EVENT_TEST_EVENTS is an E-Records (EDR) module table in the Oracle E-Business Suite EDR schema. It stores information about the individual events that are to be raised within a test scenario instance. The table functions as the detail (child) table for EDR_INTER_EVENT_TEST_SCENARIOS, meaning each row represents a single event definition belonging to a parent test scenario. In the context of Oracle EBS 12.1.1 and 12.2.2, this object supports the configuration, simulation, and validation of event-raising behavior within the E-Records framework without impacting production event processing.

From a modeling perspective, the metadata classifies this table heuristically as a standalone Data Vault construct. Although it holds a foreign key to its parent scenario table, its classification as standalone suggests it acts as an independent descriptive entity rather than a pure link or satellite. It is best treated as a detail table whose grain is one row per event per test scenario.

Key Information Stored

The table contains 43 documented columns. The most operationally significant are the identifier and event-definition columns:

The unique index EDR_INTER_EVENT_TEST_EVENTS_P on INTER_EVENT_TEST_ID is the sole documented business-key candidate; no separate natural-key unique constraint is documented.

Common Use Cases and Queries

Typical usage centers on retrieving, sequencing, and reporting the events configured for a test scenario. A common query joins the detail events to their parent scenario:

SELECT e.INTER_EVENT_TEST_ID, e.EVENT_NAME, e.EVENT_RAISE_TYPE, e.EVENT_RAISE_MODE, e.EVENT_EXECUTION_ORDER FROM EDR.EDR_INTER_EVENT_TEST_EVENTS e WHERE e.TEST_SCENARIO_ID = :scenario_id ORDER BY e.EVENT_EXECUTION_ORDER;

Analysts use such queries to verify that events are raised in the intended order, to confirm raise types and modes, and to audit related-event chains. Reporting scenarios include listing all events for a given test scenario, identifying events by raise mode, and validating that no two events share an unintended execution order. Because the table carries DFF attributes, reporting can also surface customer-defined qualifiers stored in ATTRIBUTE1 through ATTRIBUTE30.

Related Objects

  • EDR_INTER_EVENT_TEST_SCENARIOS — The immediate parent table. Join on EDR_INTER_EVENT_TEST_EVENTS.TEST_SCENARIO_ID = EDR_INTER_EVENT_TEST_SCENARIOS.TEST_SCENARIO_ID (documented foreign key).
  • EDR_INTER_EVENT_TEST_EVENTS_P — The primary key unique index supporting direct lookups by INTER_EVENT_TEST_ID.
  • EDR module event infrastructure — The E-Records event processing components that consume the event definitions stored here during scenario execution.
  • EDR test scenario validation utilities — Objects that read this table to simulate event raising within a test instance.

In summary, EDR_INTER_EVENT_TEST_EVENTS is a detail table that defines the events belonging to an E-Records test scenario, joined to its parent via TEST_SCENARIO_ID and uniquely identified by INTER_EVENT_TEST_ID.