Search Results az_selection_set_entities_b_u1

Overview

AZ.AZ_SELECTION_SET_ENTITIES_B is a transactional configuration table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the AZ schema. It resides within the Oracle ETRM (Enterprise Tax and Regulatory Management) product family, which governs tax determination, configuration, and content management. The table stores the constituent entity definitions that make up a "Selection Set" — a reusable grouping construct used to define which transactional entities, occurrence codes, and filtering rules are evaluated together during tax calculation or regulatory processing. Each row associates a selection set, a user context, and an entity occurrence, effectively mapping the members of a set.

Physically, the table is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting a moderately update-intensive configuration table. Its unique index AZ_SELECTION_SET_ENTITIES_B_U1 resides in APPS_TS_TX_IDX, and a LOB index (SYS_IL0000239549C00016$$) supports the FILTERING_PARAMETERS CLOB column in APPS_TS_TX_DATA. The documented primary key is AZ_SELECTION_SET_ENTITIES_B_PK on (SELECTION_SET_CODE, USER_ID, ENTITY_OCCURANCE_CODE). From a Data Vault modeling perspective, the metadata heuristically classifies this object as a standalone entity, meaning it does not declare foreign-key dependencies to other tables and therefore behaves more like a hub or independent reference structure than a link table connecting two hubs. This suggests it is best modeled as an independent business-key-bearing entity rather than a pure association link.

Key Information Stored

The table contains twenty documented columns. The most functionally significant are those defining set membership and behavior:

• SELECTION_SET_CODE (VARCHAR2 45) — identifies the parent selection set to which the row belongs; part of both the primary key and the unique index.
• USER_ID (NUMBER 15) — distinguishes per-user configurations of the same selection set; part of the primary key and unique index.
• ENTITY_OCCURANCE_CODE (VARCHAR2 45) — the specific entity occurrence within the set; also part of the primary key and unique index.
• ENTITY_CODE (VARCHAR2 45) — the underlying entity being referenced.
• INCLUDE_TYPE — controls whether the entity is included or excluded from the set.
• REF_ENTITY_OCCURANCE_CODE (VARCHAR2 45) — a reference to a related entity occurrence.
• UPDATABLE_FLAG and CHANGE_UPDATABLE_FLAG — govern whether the entity configuration can be modified.
• ALLOW_SET_TARGETVAL_FLAG and ALLOW_FILTER_FLAG — enable target value assignment and filtering respectively.
• FILTERING_PARAMETERS (CLOB 4000) — holds filter criteria, typically query predicates, used to constrain the entity selection.
• SELECTION_FLAG, FILTER_SET_FLAG, and SEQ_NUM — control selection state, set filtering behavior, and ordering.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit tracking.

The primary key (SELECTION_SET_CODE, USER_ID, ENTITY_OCCURANCE_CODE) is the surrogate/technical key. The unique index AZ_SELECTION_SET_ENTITIES_B_U1 extends this with ZD_EDITION_NAME, indicating Oracle's edition-based redefinition (EBR) support in 12.2.2, where the same logical key can exist across multiple editions. ZD_EDITION_NAME is thus a business-key qualifier rather than a standalone attribute.

Common Use Cases and Queries

Typical use cases involve reporting on and validating selection set composition for tax configuration.

• Listing all entities belonging to a given selection set:

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

• Auditing recently changed configurations using the WHO columns:

SELECT SELECTION_SET_CODE, ENTITY_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM AZ.AZ_SELECTION_SET_ENTITIES_B WHERE LAST_UPDATE_DATE > SYSDATE - 30;

• Retrieving filter definitions, noting the CLOB requires careful handling:

SELECT SELECTION_SET_CODE, DBMS_LOB.SUBSTR(FILTERING_PARAMETERS, 4000, 1) FROM AZ.AZ_SELECTION_SET_ENTITIES_B WHERE ALLOW_FILTER_FLAG = 'Y';

Because ZD_EDITION_NAME appears in the unique index, edition-aware queries in 12.2.2 should account for the active edition when resolving duplicates.

Related Objects

The documented relationship data classifies AZ_SELECTION_SET_ENTITIES_B as standalone, meaning it does not reference other database objects through declared foreign keys. Significant related objects therefore follow functional dependencies inferred from the schema rather than enforced constraints:

• AZ_SELECTION_SETS_B — the parent set definition keyed by SELECTION_SET_CODE, joined as AZ_SELECTION_SET_ENTITIES_B.SELECTION_SET_CODE = AZ_SELECTION_SETS_B.SELECTION_SET_CODE.
• AZ_SELECTION_SETS_TL — translated names/descriptions, joined on SELECTION_SET_CODE.
• AZ_ENTITIES_B — the entity master keyed by ENTITY_CODE, referenced by AZ_SELECTION_SET_ENTITIES_B.ENTITY_CODE.
• AZ_USER_GROUPS_B — relevant where USER_ID drives per-user set visibility.
• FND_USER — joins to USER_ID for resolving user context.

These joins support administration, reporting, and validation queries against selection set configuration. Because no database-level foreign keys are documented, referential integrity is enforced at the application layer, and cross-object joins should be validated for orphaned rows.