Results for “parent_attribute_id”

26 results




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

Overview

ECX_OBJECT_ATTRIBUTES is a core configuration table in the Oracle E-Business Suite XML Gateway module (product code ECX). It defines the source and target object attributes that participate in message mapping definitions, providing the structural blueprint for how inbound and outbound XML messages are translated between external documents and internal EBS interface tables or APIs. Each row describes a single attribute belonging to an object level within a mapping, including its data type, position, width, default, and conditional behavior.

Under the ETRM 12.2.2 schema the table resides in the ECX schema, is marked VALID, and contains 22 documented columns. Relationships are anchored through MAP_ID, which references ECX_MAPPINGS. From a Data Vault modeling perspective, this object is heuristically classified as satellite-leaning: it stores descriptive, descriptive-contextual attributes tied to a parent mapping key rather than acting as an independent hub or as a pure relationship link. This classification should be treated as a design suggestion, not a canonical EBS definition.

Key Information Stored

The primary key is ECX_OBJECT_ATTRIBUTES_PK, composed of MAP_ID, ATTRIBUTE_ID, and OBJECTLEVEL_ID. These three columns identify the mapping context, the attribute itself, and the object level (source or target side) to which the attribute belongs.

  • MAP_ID — Foreign key to ECX_MAPPINGS; ties the attribute to a specific mapping definition.
  • ATTRIBUTE_ID — Identifier for the individual attribute within the mapping.
  • OBJECTLEVEL_ID — Distinguishes the source versus target object level for the attribute.
  • ATTRIBUTE_NAME — Logical name of the attribute as exposed in the XML structure.
  • DATA_TYPE — Datatype used for validation or transformation.
  • POSITION and WIDTH — Ordering and length constraints for the attribute.
  • PARENT_ATTRIBUTE_ID — Self-referencing parent for hierarchical attribute structures.
  • ATTRIBUTE_TYPE, OBJECT_COLUMN_FLAG, LEAF_NODE, HAS_ATTRIBUTES — Classifiers describing attribute behavior.
  • REQUIRED_FLAG and DEFAULT_VALUE — Mandatory/optional status and defaults.
  • STAGING_COLUMN — Target staging column into which the value is loaded.
  • COND_NODE, COND_VALUE, COND_NODE_TYPE — Conditional processing rules.
  • IS_MAPPED and OCCURRENCE — Mapping activation and repetition cardinality.

The unique index ECX_OBJECT_ATTRIBUTES_U1 (MAP_ID, ATTRIBUTE_ID, OBJECTLEVEL_ID, ZD_EDITION_NAME) is the business-key candidate and supports edition-aware configuration (ZD_EDITION_NAME being the Oracle editioning column).

Common Use Cases and Queries

Typical use cases include auditing XML Gateway mappings, tracing which staging columns receive inbound values, reviewing conditional attribute rules, and diagnosing failed transactions caused by required or incorrectly typed attributes.

-- All attributes for a given mapping
SELECT a.ATTRIBUTE_NAME, a.DATA_TYPE, a.POSITION,
       a.STAGING_COLUMN, a.REQUIRED_FLAG
FROM   ECX.ECX_OBJECT_ATTRIBUTES a
WHERE  a.MAP_ID = :map_id
ORDER  BY a.OBJECTLEVEL_ID, a.POSITION;

-- Mappings that route to a specific staging column
SELECT m.MAP_ID, a.ATTRIBUTE_NAME
FROM   ECX.ECX_OBJECT_ATTRIBUTES a, ECX.ECX_MAPPINGS m
WHERE  a.MAP_ID = m.MAP_ID
AND    a.STAGING_COLUMN = :column_name;

Related Objects

  • ECX_MAPPINGS — Parent table; joined on ECX_OBJECT_ATTRIBUTES.MAP_ID = ECX_MAPPINGS.MAP_ID (the documented foreign key).
  • ECX_OBJECT_ATTRIBUTES — Self-referencing through PARENT_ATTRIBUTE_ID for hierarchical attributes.
  • ECX_XREF_TYPES / XREF_CATEGORY_ID — Referenced indirectly through the XREF_CATEGORY_ID column for cross-reference lookups.
  • ECX_OBJECT_LEVELS — Defines the object level identified by OBJECTLEVEL_ID.
  • ECX_TP_HEADERS / ECX_OUT_HEADERS — Transaction and outbound header tables that consume mapping definitions.

Because ECX_OBJECT_ATTRIBUTES governs attribute-level mapping metadata, it is consulted indirectly by XML Gateway runtime processing and by interface programs that rely on the ECX_MAPPINGS configuration hierarchy.