Search Results edr_raw_xml_t




Overview
Explore in AI Chat

Overview

EDR_RAW_XML_T is a table in the EDR (E-Records) product module of Oracle E-Business Suite, residing in the EDR schema. It stores the raw XML payloads associated with electronic records events, capturing the complete document content as received or generated by the E-Records framework. The table functions as a persistence layer for XML documents that underpin the e-records lifecycle, providing the source-of-truth representation from which downstream parsing, validation, and archival activities are performed.

The table is classified as VALID and is documented in the ETRM 12.2.2 physical schema with eight columns. From a heuristic Data Vault modeling perspective, EDR_RAW_XML_T presents characteristics of a satellite structure, keyed by a composite business key rather than a generated surrogate. Its primary key, EDR_RAW_XML_T_P, is defined over EVENT_NAME and EVENT_KEY, indicating that the table is tightly coupled to an event-based parent concept and holds descriptive, non-key attributes (the raw XML and audit columns) that change over time.

Key Information Stored

The table's identity is anchored by the composite primary key EDR_RAW_XML_T_P, which spans the following business-key candidates:

  • EVENT_NAME — Identifies the type or classification of the e-records event whose XML payload is being persisted. Combined with EVENT_KEY, it forms the unique business key.
  • EVENT_KEY — A value that uniquely identifies a specific instance of the named event. Together with EVENT_NAME it constitutes the composite unique index EDR_RAW_XML_T_P.
  • RAW_XML — The core payload column, holding the raw XML content of the electronic record document. This is the primary reason the table exists and is the column most frequently selected for downstream processing.

Standard EBS audit columns are also present and maintained by the application framework:

A secondary unique index, SYS_IL0000396575C00003$$, is documented and corresponds to the LOB/XML storage infrastructure, not to a business key. The only genuine business-key candidate is EDR_RAW_XML_T_P.

Common Use Cases and Queries

Typical usage centers on retrieving the XML payload for a known event so it can be parsed, transformed, or audited. A direct lookup by composite key is the most efficient access path:

  • Retrieve a single record's XML: SELECT raw_xml FROM edr.edr_raw_xml_t WHERE event_name = :p_event_name AND event_key = :p_event_key;
  • List all events of a given type within a time window: SELECT event_key, creation_date FROM edr.edr_raw_xml_t WHERE event_name = :p_event_name AND creation_date >= :p_from_date;
  • Audit recent changes: SELECT event_name, event_key, last_updated_by, last_update_date FROM edr.edr_raw_xml_t WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;
  • Confirm payload presence for reconciliation or troubleshooting: SELECT COUNT(*) FROM edr.edr_raw_xml_t WHERE event_name = :p_event_name;

Reporting use cases include extracting embedded XML values via XMLQuery or XMLTable for BI Publisher reports, verifying completeness of e-records for compliance audits, and feeding downstream integration or archival processes that consume the raw document.

Related Objects

The metadata classifies EDR_RAW_XML_T as standalone from a foreign-key perspective, meaning no declarative FK constraints are mined into or out of this table. Its relationships are therefore defined logically by the EVENT_NAME and EVENT_KEY composite identifier rather than by enforced referential integrity. Significant related objects include:

  • Event registry tables in the EDR schema — Parent objects keyed by EVENT_NAME that describe the available event types whose payloads are stored here.
  • EDR event instance tables — Logical counterparts keyed by EVENT_NAME and EVENT_KEY that record event occurrences and whose XML content is persisted in EDR_RAW_XML_T.
  • E-Records processing and validation packages — PL/SQL APIs in the EDR schema that read RAW_XML for parsing and rule evaluation.
  • Archival and purge concurrent programs — Components that reference EDR_RAW_XML_T to move or remove aged XML payloads.
  • Audit and compliance reporting views — BI Publisher or OBIEE data models that join EDR_RAW_XML_T with event metadata on EVENT_NAME and EVENT_KEY.

Because the table is standalone and not protected by enforced foreign keys, joins to related EDR objects should always be performed explicitly on EVENT_NAME and EVENT_KEY, with appropriate indexing on both columns to preserve query performance.