Results for “ecx_standards_b”

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

Overview

ECX_STANDARDS_B is a core configuration table owned by the ECX schema within the Oracle E-Business Suite XML Gateway module (ECX). It stores the standards definitions that govern how the XML Gateway recognizes, validates, and maps inbound and outbound business documents against recognized industry and proprietary messaging standards. In practice, ECX_STANDARDS_B acts as the master registry of the standards that the XML Gateway engine references when processing transactions exchanged with external trading partners.

From a Data Vault modeling perspective, the mined foreign-key structure classifies ECX_STANDARDS_B as hub-leaning. It holds the durable business identity of a standard (its code and type), and is referenced by downstream tables rather than being a pure transactional or descriptive satellite. This is a modeling suggestion only; the physical object remains a conventional EBS configuration table protected by a primary key and unique constraints.

The table is defined by primary key ECX_STANDARDS_B_PK on STANDARD_ID, and two unique indexes act as business-key candidates: ECX_STANDARDS_B_U1 on (STANDARD_CODE, STANDARD_TYPE, ZD_EDITION_NAME) and ECX_STANDARDS_B_U2 on (STANDARD_ID, ZD_EDITION_NAME). These constraints confirm that a standard is uniquely identified by its code, type, and edition.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are:

• STANDARD_ID – Surrogate primary key and the value propagated to dependent tables.
• STANDARD_CODE – The short identifier of the standard (a business-key component).
• STANDARD_TYPE – Classifies the standard (a business-key component).
• STANDARD_DESC – Human-readable description of the standard.
• DATA_SEEDED – Indicates whether the row is seed data delivered by Oracle, a critical distinction for upgrade safety.
• ZD_EDITION_NAME – Editioning column supporting EBR (Edition-Based Redefinition) and part of both unique indexes.
• APPLICATION_ID – The owning application context for the record.
• CREATED_BY – User who created the row.
• CREATION_DATE – Timestamp of row creation.
• LAST_UPDATED_BY – User who last modified the row.
• LAST_UPDATE_DATE – Timestamp of the most recent update.
• LAST_UPDATE_LOGIN – Login context of the last update.

The WHO columns follow the standard Oracle EBS audit convention and are essential for change tracking and support diagnostics.

Common Use Cases and Queries

Typical uses include auditing which standards are seeded versus customer-defined, verifying edition coverage, and tracing document mappings back to their governing standard.

• List all non-seeded standards: SELECT STANDARD_ID, STANDARD_CODE, STANDARD_TYPE FROM ECX_STANDARDS_B WHERE DATA_SEEDED = 'N';
• Resolve a standard by code and type: SELECT * FROM ECX_STANDARDS_B WHERE STANDARD_CODE = :code AND STANDARD_TYPE = :type;
• Report recent changes: SELECT STANDARD_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM ECX_STANDARDS_B WHERE LAST_UPDATE_DATE > :since;
• Join to detail mappings: SELECT s.STANDARD_CODE, d.* FROM ECX_STANDARDS_B s, ECX_XREF_DTL_B d WHERE s.STANDARD_ID = d.STANDARD_ID;

These queries support implementation troubleshooting, upgrade impact analysis, and integration reconciliation reporting.

Related Objects

The FK metadata documents the following principal relationship:

• ECX_XREF_DTL_B.STANDARD_ID → ECX_STANDARDS_B.STANDARD_ID – The detail mapping table that consumes this standard definition; the primary dependent object.

Beyond the documented FK, ECX_STANDARDS_B is referenced conceptually by the XML Gateway transaction and mapping infrastructure, including ECX_XREF_HDR, ECX_XREF_TYPES, and the transactional ECX_OUTBOUND/ECX_INBOUND tables, plus the ECX transaction type definitions that drive document routing. Configuration and DBA reporting views in the ECX schema similarly resolve STANDARD_ID against this registry.