Results for “ecx_xref_hdr”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECX_XREF_HDR is a table within the ECX - XML Gateway product of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its stated purpose is to hold the code conversion categories used by the XML Gateway infrastructure. In practice, this table functions as the header or master record for cross-reference (XREF) definitions, providing the category-level container under which individual code conversion entries and standards mappings are organized. XML Gateway relies on these cross-reference definitions to translate between internal EBS values and the external code values exchanged with trading partners, middleware, and other applications during message processing.

From a modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. This suggests that ECX_XREF_HDR is best treated as a hub entity: a table whose primary key represents a distinct business concept (a cross-reference category) and whose identity is referenced by dependent tables. Its behavior is consistent with a hub rather than a link or satellite because the table is the parent in all documented foreign key relationships and does not itself carry foreign keys into other objects. Note that this classification reflects structural mining of the foreign key graph and should be treated as a modeling suggestion rather than an authoritative EBS fact.

Key Information Stored

The documented metadata is concise, and the table is identified by a single primary key with no additional columns enumerated in the excerpt. The most significant attributes are therefore implied by the documented constraints:

• XREF_CATEGORY_ID — the surrogate primary key defined by the ECX_XREF_HDR_PK constraint. This column uniquely identifies each code conversion category row and serves as the reference point for dependent tables.
• Cross-reference category attributes — although individual column names are not listed in the available metadata, the table description states it "contains the code conversion categories," so each row represents one category. Business-key candidates are not explicitly documented as unique indexes in the supplied metadata; in EBS deployments, category name or code columns typically act as natural business identifiers, but this cannot be confirmed from the provided excerpt.

Because the documentation excerpt states "Not implemented in this database," the table may not be present or populated in every environment. This is a common condition for optional XML Gateway configuration objects, which exist only when cross-reference functionality has been configured. Implementers should verify physical presence and row counts before relying on it.

Common Use Cases and Queries

Typical scenarios center on auditing and troubleshooting code conversion configuration. A common pattern is to enumerate all defined cross-reference categories, then drill into their detail rows and standards mappings:

• Listing all conversion categories: SELECT XREF_CATEGORY_ID FROM ECX_XREF_HDR ORDER BY XREF_CATEGORY_ID;
• Counting detail entries per category: SELECT h.XREF_CATEGORY_ID, COUNT(d.XREF_CATEGORY_ID) FROM ECX_XREF_HDR h LEFT JOIN ECX_XREF_DTL d ON d.XREF_CATEGORY_ID = h.XREF_CATEGORY_ID GROUP BY h.XREF_CATEGORY_ID;
• Checking standards coverage: join to ECX_XREF_STANDARDS on XREF_CATEGORY_ID to confirm which categories have external standards associated.
• Verifying whether the object is implemented in a given instance by querying the data dictionary before running the queries above.

Reporting use cases include configuration migration validation between environments, impact analysis before changing or retiring a category, and reconciliation of cross-reference definitions across source and target systems during integration projects.

Related Objects

The documented foreign key relationships identify two direct dependents, both of which reference ECX_XREF_HDR through XREF_CATEGORY_ID:

• ECX_XREF_DTL — holds the individual cross-reference detail entries. Join column: ECX_XREF_DTL.XREF_CATEGORY_ID → ECX_XREF_HDR.XREF_CATEGORY_ID.
• ECX_XREF_STANDARDS — holds associated standards information. Join column: ECX_XREF_STANDARDS.XREF_CATEGORY_ID → ECX_XREF_HDR.XREF_CATEGORY_ID.

Beyond these documented dependencies, other ECX XML Gateway components such as message definition and mapping runtime objects may reference the cross-reference categories indirectly through the detail and standards tables. The primary key ECX_XREF_HDR_PK constrains XREF_CATEGORY_ID and enforces referential integrity for both dependent tables. When performing configuration analysis, these three tables are typically queried together as a unit representing the complete cross-reference definition.