Search Results optimize_attribute_code

Overview

The view CZ_AUTOSELECTION_RANGES_V is a Bills of Material (BOM) component of the Oracle E-Business Suite configuration infrastructure, exposing the autoselection ranges defined for configurable items and models. Autoselection ranges are the rules that determine when a configurable component is automatically selected during a configuration session, based on the value of an option, numeric range, or attribute comparison. The view denormalizes the base table by joining the range definitions to the descriptive name of the associated optimize attribute held in the Oracle Common Applications attribute repository.

Because it is a view rather than a base table, CZ_AUTOSELECTION_RANGES_V is primarily a reporting and integration surface. It allows Oracle Configurator, order capture, quoting, and custom reporting layers to query autoselection logic without directly referencing the underlying configuration tables. The metadata records the object as "Not implemented in this database" in the sample environment, which is a normal condition when Oracle Configurator is not installed or the relevant schema objects have not been deployed. In such cases, queries against the view fail or return no rows, and the reported symptom "0 Item(s) Selected." is consistent with a configuration model whose autoselection ranges are absent, disabled, or not deployable in that instance.

Underlying Base Objects

The documented metadata states that no base objects are referenced, but the view text unambiguously shows the definition. The view selects from CZ_AUTOSELECTION_RANGES (aliased AR) with an outer join to AK_ATTRIBUTES_VL (aliased AK). The join condition is AK.ATTRIBUTE_CODE(+) = AR.OPT_ATTRIBUTE_CODE and AK.ATTRIBUTE_APPLICATION_ID(+) = 702. Application identifier 702 corresponds to the Oracle Configurator product, so the attribute lookup is restricted to Configurator-owned attributes. The outer join operator ensures that range rows survive even when no matching attribute name exists, in which case OPTIMIZE_ATTRIBUTE_NAME returns null.

The driving table, CZ_AUTOSELECTION_RANGES, stores one row per range rule, linked to a configuration assignment through ASSIGNMENT_ID. The ROWID of the base row is exposed as ROW_ID, which allows the view to be used in updatable contexts where the framework requires a row identifier.

Key Columns

• RANGE_ID and ASSIGNMENT_ID — identify the range rule and the assignment (model, component, or option) to which it belongs.
• LOW_RANGE / HIGH_RANGE and FROM_RANGE / TO_RANGE — define the numeric or character bounds within which the rule applies.
• EFFECTIVITY_DATE and DISABLE_DATE — control the effective period of the range; a disabled or expired range is a frequent cause of zero autoselections.
• OPTIMIZE_ATTRIBUTE_CODE and OPTIMIZE_ATTRIBUTE_NAME — the attribute driving the optimization, with the descriptive name supplied by the attribute repository join.
• COMPONENT_CODE and PRICE_FLAG — identify the component being selected and whether pricing is affected.
• OPT_ATTRIBUTE_CODE — the key used to join to AK_ATTRIBUTES_VL for the attribute name.
• AUTOSELECT_ON_BOOK — indicates whether the component is autoselected at the time an order is booked.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield columns for customer-specific extensions.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO columns for change tracking.

Common Use Cases and Queries

The view is typically queried to validate autoselection configuration, diagnose missing or expired ranges, and support custom reporting on configuration rules. A typical diagnostic query lists active ranges for a given assignment:

• SELECT range_id, assignment_id, opt_attribute_code, optimize_attribute_name, low_range, high_range, from_range, to_range, effectivity_date, disable_date, autoselect_on_book FROM cz_autoselection_ranges_v WHERE assignment_id = :p_assignment_id ORDER BY range_id;

To detect the cause of a "0 Item(s) Selected." condition, filter on date windows and the autoselect flag:

• SELECT range_id, optimize_attribute_name, low_range, high_range, effectivity_date, disable_date FROM cz_autoselection_ranges_v WHERE assignment_id = :p_assignment_id AND (disable_date IS NULL OR disable_date > SYSDATE) AND effectivity_date <= SYSDATE;

Because the view exposes ROW_ID and WHO columns, it can also be used for integration extracts that feed external configuration or pricing engines. Where the view is not implemented in a given instance, the equivalent base-table query against CZ_AUTOSELECTION_RANGES combined with AK_ATTRIBUTES_VL provides the same data.