Search Results edr_inter_event_test_scenarios




Overview
Explore in AI Chat

Overview

The EDR_INTER_EVENT_TEST_SCENARIOS table is a core E-Records (EDR) object within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores information about test scenario instances that are created through the Inter Event Verification form. In regulated environments, the Inter Event Verification process is used to confirm that electronic records and their associated events remain consistent and trustworthy. Each row in this table represents one instance of a test scenario executed against that verification process.

The table also carries a flag that indicates whether an ERES (Electronic Records and Electronic Signatures) signature was requested for the current test scenario instance. This makes the table significant for compliance auditing under frameworks such as 21 CFR Part 11, where the linkage between verification activity and signature intent must be demonstrable.

From a data modeling perspective, the metadata classifies this object heuristically as standalone under a Data Vault treatment. In practice this suggests the table behaves closest to a hub or a self-contained reference entity: it holds the master list of test scenario instances keyed by a single surrogate identifier, and dependent child records attach to it rather than the reverse. No parent foreign keys are documented, reinforcing this standalone classification.

Key Information Stored

The physical schema comprises ten documented columns. The most important are:

  • TEST_SCENARIO_ID — The surrogate primary key, enforced by the EDR_INTEREVENT_TEST_SCENARIO_P constraint. This is the internal system identifier and is not exposed as a business key.
  • TEST_SCENARIO — The business identity of the scenario definition. Together with the instance number, this forms a unique business key.
  • TEST_SCENARIO_INSTANCE — Distinguishes repeated executions of the same scenario, allowing multiple runs to be tracked independently.
  • TEST_SCENARIO_TYPE — Classifies the scenario, supporting filtering and reporting by category of verification performed.
  • ERES_REQUESTED_FLAG — Records whether an electronic signature was requested for this test scenario instance. This is the principal compliance-relevant attribute.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture the standard "who, when, and through which session" audit trail required for GxP-relevant data.

Two unique indexes are documented: EDR_INTEREVENT_TEST_SCENARIO_P on TEST_SCENARIO_ID (the surrogate primary key) and EDR_INTEREVENT_TST_SCENARIO_U1 on the composite (TEST_SCENARIO, TEST_SCENARIO_INSTANCE), which represents the true business-key candidate.

Common Use Cases and Queries

Typical usage centers on compliance reporting, reconciliation, and verification drill-down. A common pattern is to retrieve all instances that requested an ERES signature for a given period:

  • SELECT TEST_SCENARIO, TEST_SCENARIO_INSTANCE, TEST_SCENARIO_TYPE FROM EDR.EDR_INTER_EVENT_TEST_SCENARIOS WHERE ERES_REQUESTED_FLAG = 'Y';
  • Joining to the child events table to reconstruct a scenario's event detail: SELECT s.TEST_SCENARIO, e.* FROM EDR.EDR_INTER_EVENT_TEST_SCENARIOS s, EDR.EDR_INTER_EVENT_TEST_EVENTS e WHERE s.TEST_SCENARIO_ID = e.TEST_SCENARIO_ID;
  • Audit-trail reporting by user and date using CREATED_BY and CREATION_DATE to establish when test evidence was captured.
  • Distinct scenario inventory by type to support periodic validation reviews.

Related Objects

The documented foreign-key relationship shows EDR_INTER_EVENT_TEST_EVENTS.TEST_SCENARIO_ID referencing EDR_INTER_EVENT_TEST_SCENARIOS.TEST_SCENARIO_ID, making the events table the primary dependent child. Other objects of interest include the Inter Event Verification form and its underlying EDR API or package, which create scenario instances; the ERES signature tables that record the actual signatures when ERES_REQUESTED_FLAG is set; and E-Records audit or history tables that log changes. Reporting views over EDR typically join these children back to the parent scenario row to present a complete verification picture.