Search Results az_selection_set_entities_b




Overview
Explore in AI Chat

Overview

AZ_SELECTION_SET_ENTITIES_B is a base table in the AZ (Application Implementation) product schema of Oracle E-Business Suite, holding the definition of "Selection Set Entities" used by the Application Implementation / setup migration and comparison toolset. It defines which business entities participate in a given selection set, and how those entities are included, filtered, sequenced, and made updatable during a setup copy, compare, or migration exercise. The table is documented as VALID in both 12.1.1 and 12.2.2 and is exposed in ETRM with 20 columns.

The object is classified heuristically as standalone in the Data Vault sense, meaning the mined foreign-key structure does not surface a parent hub or a dependent link. As a modeling suggestion, this can be read as a reference/definition table whose parent relationships (selection set and entity metadata) are enforced through the selection set code and entity code values rather than through declared, mined foreign keys. The "_B" suffix follows the EBS convention for a base table, typically paired with a translated "_TL" table where descriptive, language-dependent attributes exist.

Key Information Stored

The primary key of the table is AZ_SELECTION_SET_ENTITIES_B_PK, composed of SELECTION_SET_CODE, USER_ID, and ENTITY_OCCURANCE_CODE. A second unique index, AZ_SELECTION_SET_ENTITIES_B_U1, extends that key with ZD_EDITION_NAME. Together these are the business-key candidates that guarantee one entity occurrence per user per selection set (and per edition).

  • SELECTION_SET_CODE — identifies the parent selection set to which this entity definition belongs; the leading business key column.
  • USER_ID — the user context that owns or applies this entity rule, part of the composite key.
  • ENTITY_OCCURANCE_CODE — the specific occurrence of the entity being included; part of the composite key.
  • ENTITY_CODE — the business entity (for example, a setup or object descriptor) to be processed.
  • INCLUDE_TYPE — controls whether the entity is included, excluded, or treated with a specific inclusion rule.
  • REF_ENTITY_OCCURANCE_CODE — a reference to a related entity occurrence, supporting dependent or nested entities.
  • UPDATABLE_FLAG and CHANGE_UPDATABLE_FLAG — flags governing whether the entity may be updated and whether updatability may change during processing.
  • ALLOW_SET_TARGETVAL_FLAG — permits setting target values for the entity in a copy/migration.
  • ALLOW_FILTER_FLAG, FILTER_SET_FLAG, and FILTERING_PARAMETERS — define and store filter criteria applied to the entity's data.
  • SELECTION_FLAG and SEQ_NUM — mark the entity as a selection and establish processing order.
  • ZD_EDITION_NAME — edition reference used in the unique business key.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use is reporting and administration of selection sets: listing which entities a set processes, in what order, with which filters and updatability rules, and for which user. A basic query joins the composite key to retrieve all entity rules for one selection set:

SELECT SELECTION_SET_CODE, USER_ID, ENTITY_OCCURANCE_CODE, ENTITY_CODE, INCLUDE_TYPE, UPDATABLE_FLAG, SEQ_NUM FROM AZ.AZ_SELECTION_SET_ENTITIES_B WHERE SELECTION_SET_CODE = :set_code ORDER BY SEQ_NUM;

Administrators frequently audit filter and target-value behavior, filtering on ALLOW_FILTER_FLAG = 'Y' or ALLOW_SET_TARGETVAL_FLAG = 'Y', and identify recently modified definitions via LAST_UPDATED_BY and LAST_UPDATE_DATE. Existence checks against the unique index are useful before inserting new entity occurrences. Because USER_ID forms part of the key, queries should always constrain it when reproducing a specific user's view of a selection set.

Related Objects

The mined relationship data classifies this object as standalone, so no explicit foreign keys are documented. The following are the most significant dependencies inferred from the key columns and AZ product context:

  • Selection set definition table — joined on SELECTION_SET_CODE; the parent that names and owns the set.
  • Entity definition table — joined on ENTITY_CODE; resolves the entity metadata being referenced.
  • Entity occurrence table — joined on ENTITY_OCCURANCE_CODE and REF_ENTITY_OCCURANCE_CODE; resolves occurrence context.
  • User account / FND_USER — joined on USER_ID; identifies the owning user.
  • Filter / parameter tables — related through FILTERING_PARAMETERS and the filter flags.
  • AZ concurrent programs and APIs — the generation, compare, and migration routines that read this table to drive processing at runtime.

Because the object is standalone, joins are conventional application-level key matches rather than enforced referential constraints; any custom SQL should validate these joins explicitly.