Search Results az_structures_b




Overview
Explore in AI Chat

Overview

AZ_STRUCTURES_B is a table in the AZ (Application Implementation) schema of Oracle E-Business Suite, documented as VALID in releases 12.1.1 and 12.2.2. Its description, "Structures," identifies it as the definition repository for structure codes used by Oracle's Application Implementation module. In the EBS architecture, the AZ module supports setup and configuration work performed during and after implementation, and AZ_STRUCTURES_B provides the master list of structures against which edition, hierarchy, and activation attributes are maintained.

The table carries nine documented columns. Its primary key is AZ_STRUCTURES_B_PK, defined on STRUCTURE_CODE. Under the metadata's heuristic Data Vault classification, mined from the foreign-key structure, the object is assessed as standalone; no parent or child foreign keys were detected in the documented schema. From a Data Vault modeling perspective, this suggests AZ_STRUCTURES_B behaves as a reference or hub-like table holding a stable business key (STRUCTURE_CODE), with its descriptive attributes carried on the same row rather than normalized into separate dependent objects.

Key Information Stored

The columns below are the ones from the documented physical schema that carry the greatest analytical and integration value.

  • STRUCTURE_CODE — The business identifier for a structure and the column on which the primary key AZ_STRUCTURES_B_PK is defined. All downstream references to a structure resolve through this value.
  • ZD_EDITION_NAME — The edition identifier. It participates with STRUCTURE_CODE in the unique index AZ_STRUCTURES_B_U1, making the pair the business-key candidate for this table and providing edition-scoped uniqueness for structure codes.
  • HIERARCHICAL_FLAG — Indicates whether the structure is hierarchical in nature, allowing consumers to distinguish flat and hierarchical structure definitions.
  • ACTIVE — The enabled/disabled indicator governing whether the structure remains available for use in setup and configuration processing.
  • CREATED_BY, CREATION_DATE — Standard EBS audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the last modifying user, timestamp, and login context.

Nine columns are documented in total; the remainder are audit or edition-related attributes consistent with the ones described above. Note that the surrogate primary key is a single-column constraint on STRUCTURE_CODE, while the unique index AZ_STRUCTURES_B_U1 (STRUCTURE_CODE, ZD_EDITION_NAME) provides the stronger edition-aware business-key candidate.

Common Use Cases and Queries

Typical usage centers on configuration validation, edition comparison, and audit reporting. Queries frequently filter on ACTIVE to return only structures available for assignment, or on HIERARCHICAL_FLAG to separate hierarchical from flat definitions.

  • Active structure listing: SELECT structure_code, hierarchical_flag FROM az.az_structures_b WHERE active = 'Y' ORDER BY structure_code;
  • Edition-scoped lookup: SELECT * FROM az.az_structures_b WHERE structure_code = :code AND zd_edition_name = :edition;
  • Hierarchical structure inventory: SELECT structure_code, creation_date FROM az.az_structures_b WHERE hierarchical_flag = 'Y';
  • Audit and change tracking: query on LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recent maintenance activity.
  • Data Vault staging extraction: STRUCTURE_CODE plus ZD_EDITION_NAME form the natural composite key for a hub or reference load, with HIERARCHICAL_FLAG and ACTIVE as descriptive satellite attributes.

Related Objects

The documented relationship data classifies AZ_STRUCTURES_B as standalone, meaning no foreign-key relationships to other tables were mined from the metadata. Consequently, the objects below are inferred from AZ-module conventions and standard EBS reference patterns rather than from documented constraints.

  • AZ_STRUCTURES_TL — The translated sibling table for structure names and descriptions, joined on STRUCTURE_CODE.
  • AZ_STRUCTURES_VL — The view that ordinarily joins the base and translated tables, exposing user-facing structure values.
  • AZ_STRUCTURES_B_PK — The primary key constraint on STRUCTURE_CODE; enforced through a unique index of the same name.
  • AZ_STRUCTURES_B_U1 — The unique index on (STRUCTURE_CODE, ZD_EDITION_NAME) supporting edition-aware lookups.
  • AZ_EDITION-related objects — Edition metadata objects that resolve ZD_EDITION_NAME values.
  • FND_* concurrent and lookup tables — Standard EBS lookups and concurrent program registrations that reference structure codes.

Because the metadata confirms no documented foreign keys, integrators should verify relationships against the AZ module's runtime dependencies before establishing joins.