Search Results ax_structures_u1

Overview

The AX.AX_STRUCTURES table is a core metadata object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, specifically belonging to the Applications (AX) schema associated with the Enterprise Territory and Resource Management (ETRM) or related distribution processing modules. This table stores the structural definitions used by a distribution plan to retrieve the information it requires. It contains a row for every structure within a given plan, defining how data is sourced, queried, and mapped during distribution execution. Each structure entry specifies the structure type (such as ACCOUNT, ACCOUNTED AMOUNT, COMMENT, DESCRIPTION, ENTERED_AMOUNT, or THIRD PARTY), the source type, the query chain utilized, and the source of the information. Physically, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Based on the foreign key relationships and column composition, the heuristic Data Vault classification for this object is satellite-leaning, suggesting it primarily stores descriptive attributes and context surrounding the central distribution plan entities.

Key Information Stored

The table's surrogate primary key is AX_STRUCTURES_PK, composed of SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME, STRUCTURE_TYPE, and STRUCTURE_NUMBER. A unique index, AX_STRUCTURES_U1, exists on the same set of columns, reinforcing this composite as the primary business-key candidate for identifying a structure uniquely. Beyond the key, the most critical columns include SET_OF_BOOKS_ID (identifying the ledger context), APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME, STRUCTURE_TYPE, and STRUCTURE_NUMBER. Source-related columns such as SOURCE_TYPE, QUERY_CHAIN_NAME, SOURCE_TABLE, SOURCE_COLUMN_VALUE, and SOURCE_SEGMENT define where and how the structure retrieves its data. Target-related columns including TARGET_SEGMENT, TARGET_COLUMN_NAME, START_POSITION, and END_POSITION define how the retrieved data is mapped or positioned. Audit columns like LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN track record changes. The table contains 20 documented columns in total.

Common Use Cases and Queries

Typical use cases involve examining the structures configured for a distribution plan, tracing the query chains and source tables used, and reporting on structure definitions across ledgers. A common query pattern joins AX_STRUCTURES to AX_DISTRIB_PLANS on the composite key (SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME) to retrieve plan-level context. Analysts frequently filter by STRUCTURE_TYPE or QUERY_CHAIN_NAME to audit specific retrieval logic. For example, selecting PLAN_NAME, STRUCTURE_TYPE, STRUCTURE_NUMBER, SOURCE_TABLE, SOURCE_COLUMN_VALUE, and TARGET_COLUMN_NAME ordered by PLAN_NAME provides a readable structure map. Index AX_STRUCTURES_N1 supports queries filtering on APPLICATION_ID and QUERY_CHAIN_NAME, while AX_STRUCTURES_N2 and AX_STRUCTURES_N3 support joins and lookups involving SET_OF_BOOKS_ID, TRANSLATION_SCHEME, and SOURCE_TABLE or SOURCE_COLUMN_VALUE. These queries are essential for debugging distribution output and validating configuration during implementation or upgrade.

Related Objects

AX_STRUCTURES maintains foreign key relationships with AX_DISTRIB_PLANS and AX_QUERY_CHAINS, referencing them via SET_OF_BOOKS_ID, APPLICATION_ID, and related columns. Additionally, it references AX_ARITHMETIC_EXPR and AX_CONDITIONS through composite foreign keys that include SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME, STRUCTURE_TYPE, and STRUCTURE_NUMBER, linking structural definitions to their arithmetic expressions and conditions. Conversely, AX_ARITHMETIC_EXPR and AX_CONDITIONS reference AX_STRUCTURES back via SET_OF_BOOKS_ID, establishing a tightly coupled dependency where structures are consumed by expression and condition logic. These relationships confirm that AX_STRUCTURES acts as a foundational configuration table for distribution processing, with its primary consumers being the plans, query chains, expressions, and conditions that depend on accurate structural metadata.