Search Results edr_fwk_test_b




Overview
Explore in AI Chat

Overview

EDR_FWK_TEST_B is a table owned by the EDR schema within the Oracle E-Business Suite E-Records (ERES) product. Per the ETRM repository metadata, its documented purpose is to support ERES Framework testing in newly provisioned environments. Oracle explicitly states that this is not a functional table: it carries no production business logic, and its contents should be treated as disposable test scaffolding rather than application data. It remains classified as VALID in the data dictionary in both Oracle EBS 12.1.1 and 12.2.2, but its presence in a production instance is incidental to the EDR schema build, not evidence of a business process dependency.

Mined from its foreign key structure, the table is classified heuristically as standalone in Data Vault terms. No parent hub or link relationships are enforced by foreign keys, so a Data Vault model would most naturally represent it as an isolated satellite-style structure keyed on its own identifier, with no upstream integration obligations. Accordingly, this object is rarely a candidate for inclusion in enterprise data warehouse or golden-record pipelines.

Key Information Stored

The table is physically defined with 41 columns in ETRM 12.2.2. Its meaningful content is thin by design:

  • FWK_TEST_ID — the surrogate primary key, enforced by the unique index EDR_FWK_TEST_B_P.
  • FWK_TEST_NO — the documented business-key candidate, enforced by the unique index EDR_FWK_TEST_B_U1. This is the human-readable test reference used by the framework harness.
  • NUMBER_VALUE and DATE_VALUE — numeric and date payloads used to exercise value conversion, validation, and e-record rendering paths during framework testing.
  • STATUS — lifecycle or processing state of the test record; in a test harness this typically reflects the outcome or stage of the exercise rather than a real approval state.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard Oracle EBS DFF (descriptive flexfield) placeholder block. In this table the thirty attribute columns are almost certainly unused test filler, present because the table was generated from the same DDL template as functional EDR tables.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns, recording row creation and last modification identity and timestamps.

The absence of any foreign key column other than the translation join below reinforces that no application entity depends on this table's contents.

Common Use Cases and Queries

Legitimate use cases are limited to framework verification and environment hygiene. Because the table is non-functional, the most common operation is a sanity check confirming it has been created and populated as part of an ERES Framework smoke test:

  • Verify setup completeness: SELECT COUNT(*) FROM edr.edr_fwk_test_b;
  • Confirm uniqueness enforcement on the business key: SELECT fwk_test_no, COUNT(*) FROM edr.edr_fwk_test_b GROUP BY fwk_test_no HAVING COUNT(*) > 1;
  • Inspect the most recent harness records: SELECT fwk_test_id, fwk_test_no, status, creation_date FROM edr.edr_fwk_test_b ORDER BY creation_date DESC;
  • Join to the translation table for description text: SELECT b.fwk_test_no, t.description FROM edr.edr_fwk_test_b b, edr.edr_fwk_test_tl t WHERE b.fwk_test_id = t.fwk_test_id AND t.language = USERENV('LANG');

It is not a reporting source. Any extract, reconciliation, or analytics requirement referencing EDR_FWK_TEST_B should be challenged and rerouted to the corresponding functional ERES tables.

Related Objects

The documented relationship set is minimal, which is consistent with the table's standalone classification:

  • EDR_FWK_TEST_TL — the only table documented as referencing EDR_FWK_TEST_B, joined on EDR_FWK_TEST_TL.FWK_TEST_ID = EDR_FWK_TEST_B.FWK_TEST_ID. It supplies translated description columns for the test rows; like the base table, it is test-only.
  • EDR_FWK_TEST_B_P — the unique index enforcing the FWK_TEST_ID primary key.
  • EDR_FWK_TEST_B_U1 — the unique index enforcing FWK_TEST_NO as the business-key candidate.
  • ERES Framework runtime objects (EDR schema) — the test harness components that read and write these rows during environment validation. These are referenced operationally, not through declarative foreign keys.

No views, public APIs, or functional EDR entities are documented as depending on this object. Administrators should exclude it from backup retention policies, data archival plans, and any data-quality scope definition for the EDR module.