Search Results cz_autoselection_ranges




Overview
Explore in AI Chat

Overview

CZ_AUTOSELECTION_RANGES is a Configurator foundation table within the Oracle E-Business Suite Bills of Material (BOM) module. It stores the range definitions that drive the automatic selection of optional items during a configuration session. When a user configures a model in Oracle Configurator, the application evaluates the active constraint assignments and, where a range rule applies, automatically selects the qualifying option items on the user's behalf. CZ_AUTOSELECTION_RANGES holds the boundary specification for each such autoselection rule, while the individual items that fall within the range are held in the child table CZ_AUTOSELECTION_ITEMS.

From a data modeling perspective, the FK topology described in the ETRM metadata classifies this table as satellite-leaning. It carries descriptive, rule-specific attributes that hang off a parent constraint assignment rather than serving as a pure hub or a pure intersection link. This classification is a heuristic suggestion mined from the foreign key structure and should be validated against the specific integration or warehouse design in use.

Key Information Stored

The table is intentionally narrow. Its documented structure centers on the following columns:

  • RANGE_ID — The surrogate primary key, enforced by CZ_AUTOSELECTION_RANGES_PK. This value is system-generated and uniquely identifies each autoselection range record. It is also the column referenced by CZ_AUTOSELECTION_ITEMS.RANGE_ID.
  • ASSIGNMENT_ID — A foreign key to CZ_CONSTRAINT_ASSIGNMENTS. This associates the range with the constraint assignment whose logic governs the autoselection behavior, tying the range to a specific configurable model, option class, or feature.

Because the ETRM documentation for this object is limited, the range boundary values themselves are not enumerated in the supplied metadata. In practice, the business keys and descriptive attributes that define the lower and upper bounds of the selection range, along with any inclusion flags, are stored on this table. The only documented unique identifier is the surrogate primary key; no additional unique index is recorded in the ETRM metadata, so RANGE_ID is the sole guaranteed unique key.

Common Use Cases and Queries

Typical use cases cluster around troubleshooting and auditing configuration behavior. Consultants and support analysts investigate why a particular option was selected automatically during an order capture or quote session, or why an expected autoselection failed to occur. Reporting requirements often include a listing of all autoselection rules active for a given model or constraint assignment.

A common query pattern joins the range table to its parent assignment to resolve the owning model context:

  • SELECT r.RANGE_ID, r.ASSIGNMENT_ID FROM CZ_AUTOSELECTION_RANGES r WHERE r.ASSIGNMENT_ID = :assignment_id;
  • SELECT r.RANGE_ID, i.* FROM CZ_AUTOSELECTION_RANGES r, CZ_AUTOSELECTION_ITEMS i WHERE i.RANGE_ID = r.RANGE_ID;

The second pattern is the canonical parent-child expansion, returning every item that falls inside each declared range. These queries are frequently used in data migration validation, where custom or legacy autoselection logic must be reconciled against Oracle Configurator definitions before an upgrade from 12.1.1 to 12.2.2.

Related Objects

  • CZ_CONSTRAINT_ASSIGNMENTS — Parent object referenced by CZ_AUTOSELECTION_RANGES.ASSIGNMENT_ID; supplies the constraint context under which the range operates.
  • CZ_AUTOSELECTION_ITEMS — Child table linked by CZ_AUTOSELECTION_ITEMS.RANGE_ID; holds the individual items eligible for autoselection within each range.

Beyond these direct relationships, the broader Configurator data model connects through the constraint assignment layer to configuration models, option classes, and features, which supply the runtime context for autoselection evaluation. Note that the ETRM metadata states this table is not implemented in the reference database, meaning the object exists in the product schema but may be empty or unused in environments where autoselection ranges are not configured.