Results for “object_level”

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

Overview

ECX_OBJECT_LEVELS is a table in the ECX (XML Gateway) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. Its documented purpose is to store the source and target object levels used by the XML Gateway mapping infrastructure. In practical terms, the table defines the hierarchical level structure that applies to a trading partner mapping: which business object participates at each level of the document (header, line, detail, and similar tiers), how those levels are named, and how they nest through a parent-child relationship.

Because mappings in XML Gateway transform inbound and outbound business documents between internal EBS objects and external XML messages, the level definitions held here determine how repeating groups and nested structures are resolved during message processing. Each row anchors a level to a specific mapping through MAP_ID, so the table functions as a dependent child of the mapping definition rather than as an independent master entity.

From a Data Vault modeling perspective, the mined foreign key structure classifies ECX_OBJECT_LEVELS as satellite-leaning. This is a modeling suggestion only: the table carries descriptive attributes about levels that are owned by a parent mapping, rather than acting as a hub of independent business keys or as a pure link between two hubs. Its grain is one row per level per mapping.

Key Information Stored

The table contains eight documented columns. The most significant are:

• MAP_ID — Identifier of the owning mapping in ECX_MAPPINGS. This is the primary foreign key and the principal access path for retrieving the levels of a given mapping.
• OBJECTLEVEL_ID — Identifier of the object level within the mapping. Together with MAP_ID it forms the composite primary key ECX_OBJECT_LEVELS_PK.
• OBJECT_ID — Reference to the object associated with the level, identifying which business object participates at that tier.
• OBJECT_LEVEL — Numeric or coded indicator of the level's position in the hierarchy.
• OBJECT_LEVEL_NAME — Descriptive name of the level, typically used for display and for identifying header, line, or detail tiers.
• PARENT_LEVEL — Reference to the level that sits above this one, enabling the self-referencing hierarchy within a mapping.
• ENABLED — Flag indicating whether the level is active and should be considered during processing.
• ZD_EDITION_NAME — Editioning column introduced by the EBS 12.2 online patching architecture; it participates in the unique index ECX_OBJECT_LEVELS_U1 and is populated with the default edition value in 12.1.1 environments.

The surrogate primary key is the composite ECX_OBJECT_LEVELS_PK (MAP_ID, OBJECTLEVEL_ID). The unique index ECX_OBJECT_LEVELS_U1 (MAP_ID, OBJECTLEVEL_ID, ZD_EDITION_NAME) is the business-key candidate, and its inclusion of the edition column reflects the 12.2 editioning model.

Common Use Cases and Queries

Typical usage centers on diagnosing mapping behavior and validating level configuration before running XML Gateway transactions. A common pattern retrieves all levels for a mapping in hierarchical order:

• SELECT OBJECTLEVEL_ID, OBJECT_ID, OBJECT_LEVEL, OBJECT_LEVEL_NAME, PARENT_LEVEL, ENABLED FROM ECX.ECX_OBJECT_LEVELS WHERE MAP_ID = :map_id ORDER BY OBJECT_LEVEL;
• Filtering for active levels only: add AND ENABLED = 'Y' when generating documentation or validating a mapping.
• Identifying child levels of a given tier by joining on PARENT_LEVEL to reconstruct the nesting tree.
• Auditing mappings that reference missing or disabled objects by joining OBJECT_ID to the corresponding object definition tables.
• Reporting on mappings that contain more than one level, to confirm that repeating document structures are correctly modeled.

In 12.2 environments, queries issued against the base table may return edition-scoped rows; reports should account for ZD_EDITION_NAME or rely on the editioning view where one is defined.

Related Objects

The following objects are most significant in relation to ECX_OBJECT_LEVELS:

• ECX_MAPPINGS — Parent table, joined on ECX_OBJECT_LEVELS.MAP_ID = ECX_MAPPINGS.MAP_ID. This is the only documented foreign key and the primary dependency.
• ECX_OBJECT_LEVELS_U1 — Unique index supporting business-key lookups by mapping, level, and edition.
• ECX_OBJECT_LEVELS_PK — Primary key index on MAP_ID and OBJECTLEVEL_ID.
• ECX_OBJECTS / object definition tables — Referenced through OBJECT_ID to resolve the business object represented at each level.
• ECX_LOOKUPS — Frequently consulted to decode level names and status values used across the ECX schema.
• XML Gateway mapping and transaction runtime programs — Consume the level definitions during document transformation and validation.

Because ECX_OBJECT_LEVELS is a dependent satellite of ECX_MAPPINGS, changes to a mapping should be reviewed alongside its level definitions to ensure the document hierarchy remains consistent.