Results for “ecx_objects”

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

Overview

ECX_OBJECTS is a foundational configuration table in the Oracle EBS XML Gateway module (product code ECX). It resides in the ECX schema and stores the source and target object definitions used by XML Gateway mapping processes. Each row represents an individual business object — such as a message payload, interface table, or standard document — that participates in a map, either as a source (outbound) or target (inbound) endpoint. The table is therefore central to the metadata layer that drives how XML messages are transformed, validated, and routed between Oracle EBS and external trading partners.

Under a heuristic Data Vault classification derived from its foreign-key topology, ECX_OBJECTS is satellite-leaning: it depends on ECX_MAPPINGS through the MAP_ID foreign key and carries descriptive, versioned attributes (notably ZD_EDITION_NAME) rather than acting as an independent business hub or pure association link. Modelers should treat it as a descriptive detail table attaching to the mapping parent.

Key Information Stored

The table contains 10 documented columns. The composite primary key, enforced by ECX_OBJECTS_PK, is (MAP_ID, OBJECT_ID). A unique business-key index, ECX_OBJECTS_U1, covers (MAP_ID, OBJECT_ID, ZD_EDITION_NAME), which suggests edition-aware uniqueness for multi-edition environments.

• MAP_ID — foreign key to ECX_MAPPINGS; identifies the parent map to which this object belongs.
• OBJECT_ID — surrogate identifier for the object row; part of the composite primary key.
• OBJECT_NAME — the logical name of the object as referenced by the map definition.
• OBJECT_TYPE — categorizes the object (for example source versus target, or message versus table).
• OBJECT_DESCRIPTION — free-text description for administrative and reporting clarity.
• OBJECT_STANDARD — indicates the standards body or document standard associated with the object.
• ROOT_ELEMENT — the XML root element expected or produced for the object.
• FULLPATH — the qualified path or location identifier for the object definition.
• RUNTIME_LOCATION — the runtime resolution point used during message processing.
• ZD_EDITION_NAME — editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.

Common Use Cases and Queries

Typical scenarios include auditing which objects are attached to a given map, diagnosing transformation failures by inspecting root elements and runtime locations, and reporting on edition-specific object definitions after an EBS 12.2 upgrade.

List all objects for a specific map using a join to the parent table:

• SELECT o.object_id, o.object_name, o.object_type, o.root_element FROM ecx.ecx_objects o WHERE o.map_id = :map_id;

Find objects by type or standard across all maps:

• SELECT map_id, object_name, object_standard, fullpath FROM ecx.ecx_objects WHERE object_type = :type;

Detect duplicate or overlapping object names within the same map:

• SELECT map_id, object_name, COUNT(*) FROM ecx.ecx_objects GROUP BY map_id, object_name HAVING COUNT(*) > 1;

Related Objects

The most significant relationships, grounded in the documented foreign-key metadata and XML Gateway metadata model, are:

• ECX_MAPPINGS — parent table; joined via ECX_OBJECTS.MAP_ID = ECX_MAPPINGS.MAP_ID. Defines the map to which each object belongs.
• ECX_OBJECT_ATTRIBUTES — child detail table describing individual fields of each object, keyed by OBJECT_ID.
• ECX_OBJECT_RULES — rule definitions applied to object attributes during transformation.
• ECX_MAP_OBJECTS — alternate association surface linking maps to their participating objects.
• ECX_TRANSACTIONS and ECX_MESSAGE_HISTORY — runtime tables that reference processed objects during message execution.

Together these objects form the metadata backbone that the XML Gateway runtime engine consults when validating, translating, and delivering XML documents between Oracle EBS and external systems.