Search Results test_scenario_instance

Overview

EDR_INTER_EVENT_TEST_EVENTS_V is a reporting and diagnostic view owned by the APPS schema within the EDR (E-Records) product module of Oracle E-Business Suite. It exposes the definition of inter-event test scenarios used by the EDR framework's event-testing infrastructure. In EBS 12.1.1 and 12.2.2, EDR provides the foundation for electronic records and electronic signatures, and the ability to validate sequencing, timing, and interdependency of business events is central to that framework. This view presents the configured relationship between a test scenario, its instance, and the individual events assigned to it, along with their raise type, raise mode, execution order, and related-event linkage.

The view is read-only and carries no DML semantics; its role is to flatten several normalized EDR and Workflow tables into a single row per test event so that concurrent programs, personalizations, and ad hoc queries can resolve a TEST_SCENARIO_INSTANCE to the set of events that must be raised and evaluated. The status is VALID, confirming the underlying base objects are compiled and consistent in both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over three documented base objects:

• EDR_INTER_EVENT_TEST_SCENARIOS (SYNONYM) — the scenario header and instance definition.
• EDR_INTER_EVENT_TEST_EVENTS (SYNONYM) — the per-event configuration rows.
• WF_EVENTS_VL (VIEW) — the Workflow Business Events repository, supplying display names.

The join is driven through TEST_SCENARIO_ID linking scenarios to events, with WF_EVENTS_VL joined twice: once on TESTS.EVENT_NAME = EVENTS.NAME (inner join) and again on TESTS.RELATED_EVENT_NAME = RELEVENTS.NAME as an outer join ((+)). The outer join preserves test event rows where no related event is defined, so the related-event columns may return NULL. This structure confirms that inter-event tests are modeled as ordered, related event pairs anchored to a scenario instance.

Key Columns

• TEST_SCENARIO_ID, TEST_SCENARIO, TEST_SCENARIO_INSTANCE — the scenario identifier, its descriptive name, and the runtime instance used to isolate a test execution.
• INTER_EVENT_TEST_ID — surrogate key for each inter-event test assignment.
• EVENT_NAME, EVENT_DISPLAY_NAME — the business event under test and its user-facing Workflow display name.
• EVENT_RAISE_TYPE, EVENT_RAISE_MODE — how the event is raised (e.g., synchronous/asynchronous, direct or deferred).
• EVENT_EXECUTION_ORDER — sequencing of the event within the scenario.
• RELATED_EVENT_NAME, RELATED_EVENT_DISPLAY_NAME — the companion event against which interdependency (ordering/prior raise) is validated.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) columns for scenario-specific extensions.

Common Use Cases and Queries

Typical use is to inspect or audit a configured test scenario and to resolve which events and orders are expected. A representative query filtering on the instance:

SELECT TEST_SCENARIO,
       TEST_SCENARIO_INSTANCE,
       EVENT_NAME,
       EVENT_DISPLAY_NAME,
       EVENT_RAISE_TYPE,
       EVENT_RAISE_MODE,
       EVENT_EXECUTION_ORDER,
       RELATED_EVENT_NAME,
       RELATED_EVENT_DISPLAY_NAME
  FROM APPS.EDR_INTER_EVENT_TEST_EVENTS_V
 WHERE TEST_SCENARIO_INSTANCE = :p_instance
 ORDER BY TEST_SCENARIO_ID, EVENT_EXECUTION_ORDER;

To identify scenarios containing related-event pairs only:

SELECT TEST_SCENARIO, TEST_SCENARIO_INSTANCE, EVENT_NAME, RELATED_EVENT_NAME
  FROM APPS.EDR_INTER_EVENT_TEST_EVENTS_V
 WHERE RELATED_EVENT_NAME IS NOT NULL;

Because the view joins to WF_EVENTS_VL, it is also convenient for validating that configured event names exist in the Workflow event dictionary, supporting troubleshooting when an event fails to raise during an inter-event test run.