Search Results opt_attribute_code

Overview

The view CZBV_CONFIG_AUTOSELECT_RANGES is a Bills of Material (BOM) module database object in Oracle EBS 12.1.1 / 12.2.2, delivered as part of the Oracle Configurator (CZ) schema. It exposes auto-selection range definitions used by Oracle Configurator to automatically select or exclude configuration options based on numeric or date-bounded ranges. The view presents a read-only, presentation-layer projection of the underlying autoselection range data, including retrofitted label substitution expressions for two Yes/No lookup-backed flags. It is documented in ETRM with the description "- Retrofitted", indicating it was re-engineered for the 12.2.x technology stack and the Online Patching (ADOP) editioning model. The metadata notes that the view is "Not implemented in this database" in the reference environment and, under documented 12.2.2 metadata, lists no base objects — a common artifact of retrofitted seed views that are validated at runtime or only present when a specific product feature is installed and set up.

In an EBS reporting and integration context, the view serves as a stable, query-friendly surface over configuration autoselection logic. Because Configurator ranges drive automatic option selection at runtime, exposing them in a view supports audit, diagnostics, and data extraction without requiring callers to know the physical table column names or to decode lookup meaning translations themselves.

Underlying Base Objects

The documented view text is a straightforward projection over a single base table, CZ_AUTOSELECTION_RANGES AU, with a WITH READ ONLY clause applied. No other base objects, joins, or lookups are documented in the ETRM metadata; the reference environment records no referenced base objects and states the view is not implemented there. The two "_LA:" prefixed columns in the projection are label-substitution expressions that resolve FND_LOOKUPS values for the YES_NO lookup type against the AUTOSELECT_ON_BOOK and PRICE_FLAG source columns, mapping them to the lookup MEANING. This style of underscore-prefixed expression ("_LA:") is characteristic of retrofitted Oracle Configurator views that push translation logic into the view definition.

Key Columns

• CONFIGURATION_RANGE_ID — the unique identifier for each autoselection range (aliased from RANGE_ID in the base table).
• FROM_RANGE / TO_RANGE — the lower and upper bounds that define when the autoselection rule applies.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the effective and disable dates governing the validity period of the range (sourced from EFFECTIVITY_DATE and DISABLE_DATE).
• OPT_ATTRIBUTE_CODE — the configuration option attribute code against which the range is evaluated; this is the column most directly associated with the user's search term and is central to identifying which option feature a range constrains.
• "_LA:AT_BOOKING_FLAG" — translated Yes/No meaning for the AUTOSELECT_ON_BOOK flag, derived via FND_LOOKUPS.
• "_LA:INCLUDE_PRICE_FLAG" — translated Yes/No meaning for the PRICE_FLAG.
• ASSIGNMENT_ID — links the range to its assignment context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include auditing auto-selection ranges for a given option attribute, verifying effective-date windows, and extracting configuration rules for migration or reconciliation. A representative query filtering on the searched column follows:

SELECT configuration_range_id, from_range, to_range,
opt_attribute_code, start_effective_date, end_effective_date
FROM czbv_config_autoselect_ranges
WHERE opt_attribute_code = :attribute_code
AND TRUNC(SYSDATE) BETWEEN start_effective_date AND end_effective_date;

A second query retrieves the translated flags for rule validation:

SELECT configuration_range_id, opt_attribute_code,
"_LA:AT_BOOKING_FLAG", "_LA:INCLUDE_PRICE_FLAG"
FROM czbv_config_autoselect_ranges;

Because the view is defined WITH READ ONLY, it is intended strictly for query and reporting access; all maintenance of autoselection ranges must be performed through Configurator setup or the base table via supported APIs, not through this view.