Results for “xref_ext_value”

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

Overview

ECX_XREF_DTL_B is a core configuration table in the Oracle E-Business Suite XML Gateway (ECX) product module. It resides in the ECX schema with VALID status and is documented across EBS 12.1.1 and 12.2.2 releases. The table stores trading partner code conversion values, providing the detailed mapping entries that allow inbound and outbound XML business messages to translate between external partner-defined codes and internal Oracle EBS codes. Without these cross-reference details, XML Gateway transactions cannot reconcile partner-specific identifiers for units of measure, currency, item numbers, status codes, and similar attributes against the values expected by EBS application modules.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure suggests this object behaves as a link table. It sits between trading partner header definitions, cross-reference category headers, and EBS standard code definitions, resolving a many-to-many relationship among those entities while carrying the descriptive conversion values. This classification is a modeling suggestion rather than a physical designation, since EBS does not implement Data Vault semantics natively.

Key Information Stored

Each row represents one directional conversion entry for a trading partner, a standard, and an XREF category. The surrogate primary key is XREF_DTL_ID, enforced by the ECX_XREF_DTL_B_PK constraint, and it is also captured by the unique index ECX_XREF_DTL_B_U1. This column uniquely identifies every detail record and is the recommended join key for programmatic access.

The business-key candidate is defined by the unique index ECX_XREF_DTL_B_U2, composed of XREF_CATEGORY_ID, STANDARD_ID, XREF_INT_VALUE, XREF_EXT_VALUE, DIRECTION, and TP_HEADER_ID. This composite uniqueness guarantees that a given external value maps to exactly one internal value within a specific category, standard, direction, and trading partner combination.

• XREF_DTL_ID – Surrogate primary key for the detail row.
• XREF_CATEGORY_ID – Foreign key to ECX_XREF_HDR_B, identifying the cross-reference category header under which this conversion is grouped.
• STANDARD_ID – Foreign key to ECX_STANDARDS_B, linking the entry to a specific EBS standard definition.
• XREF_STANDARD_CODE – The standard code value associated with the mapping.
• TP_HEADER_ID – Foreign key to ECX_TP_HEADERS, identifying the trading partner that owns this conversion.
• XREF_EXT_VALUE – The external (partner-defined) code value being converted.
• XREF_INT_VALUE – The internal Oracle EBS code value that the external value maps to.
• DIRECTION – Indicates whether the conversion applies to inbound, outbound, or bidirectional message flow.
• DESCRIPTION – Free-text explanation of the conversion entry.
• APPLICATION_ID – Identifies the owning EBS application.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture standard EBS who/when tracking.

Common Use Cases and Queries

Typical usage centers on troubleshooting XML Gateway mapping failures, validating partner setup during integrations, and auditing code conversion maintenance. Analysts often join the detail table to the header tables to obtain complete context. A representative query retrieves all conversions for a specific trading partner and category:

• Joining ECX_XREF_DTL_B to ECX_TP_HEADERS on TP_HEADER_ID to display the partner name alongside each mapping.
• Joining to ECX_XREF_HDR_B on XREF_CATEGORY_ID to retrieve the human-readable category name.
• Joining to ECX_STANDARDS_B on STANDARD_ID to resolve the standard code description.
• Filtering on XREF_EXT_VALUE or XREF_INT_VALUE to trace why a specific message failed conversion.
• Reporting on rows where DIRECTION is inbound versus outbound to verify both directions are maintained.

Because the table is effectively a business configuration surface, any insert, update, or delete impacts live XML message processing and should be performed through supported XML Gateway setup screens rather than direct DML whenever possible.

Related Objects

The documented foreign key structure ties ECX_XREF_DTL_B to three parent tables, and it is itself a child within the cross-reference hierarchy.

• ECX_XREF_HDR_B – Joined on XREF_CATEGORY_ID; provides the category header information each detail row belongs to.
• ECX_TP_HEADERS – Joined on TP_HEADER_ID; defines the trading partner that owns the conversion.
• ECX_STANDARDS_B – Joined on STANDARD_ID; supplies the EBS standard code definition against which conversions are validated.

In addition, the XML Gateway runtime relies on this table indirectly through xref resolution APIs and concurrent programs that populate and validate code conversion values during message processing. Administrators should treat these related objects as a single functional unit when diagnosing mapping behavior, since a missing or misaligned parent record will render the corresponding detail conversion unusable.