Search Results component_sort_code

Overview

The CZ_AUTOSELECTION_ITEMS_V view is a Bills of Material (BOM) reporting object within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes the records that govern Oracle Configurator autoselection behavior, that is, the inventory items that are automatically selected as components when a model or option configuration is instantiated. The view presents these autoselection definitions alongside descriptive item information drawn from the item master, allowing report writers, integration developers, and configuration analysts to identify which items will be pulled into a configuration, in what quantity, under what effective and disable dates, and in what sort sequence.

Because autoselection rules tie a configurable model or option range to specific inventory items, this view functions as a bridge between configuration logic (held in the CZ schema) and item master data (held in the MTL schema). It is primarily consumed for reporting, data extraction, and validation of setup, rather than for transactional processing.

Underlying Base Objects

The view is defined over two objects:

• CZ_AUTOSELECTION_ITEMS AI — the driving table, containing the autoselection rule records keyed by AUTOSELECTION_ID, with foreign references to range and assignment identifiers.
• MTL_SYSTEM_ITEMS_KFV MSI — the item master key flexfield view, joined on both INVENTORY_ITEM_ID and ORGANIZATION_ID to supply concatenated segment values (item name), unit of measure, and item description context.

The join condition is AI.INVENTORY_ITEM_ID = MSI.INVENTORY_ITEM_ID AND AI.ORGANIZATION_ID = MSI.ORGANIZATION_ID, ensuring that the item attributes returned are organization-specific. The documented ETRM metadata lists no additional referenced base objects and does not name an owning schema for the view itself; it is noted as "Not implemented in this database," which indicates the view text is a reference definition rather than a deployed object in the source extract environment.

Key Columns

• AUTOSELECTION_ID — primary identifier for the autoselection rule; the surrogate key of the underlying CZ base record.
• RANGE_ID / ASSIGNMENT_ID — links back to the option range and configuration assignment that own the rule.
• ORGANIZATION_ID / INVENTORY_ITEM_ID — the organization and item master identifiers for the component being autoselected.
• CONCATENATED_SEGMENTS — the flexfield-concatenated item name from MTL_SYSTEM_ITEMS_KFV, exposed in the view column list as INVENTORY_ITEM_NAME.
• PRIMARY_UNIT_OF_MEASURE — the item's primary UOM (listed as UOM in the column listing).
• QUANTITY — quantity of the component applied when autoselected.
• COMPONENT_CODE and COMPONENT_SORT_CODE — the component identifier and the sort sequence that determines the order in which autoselected components appear.
• PRICE_FLAG — indicates whether the component contributes to pricing.
• EFFECTIVITY_DATE / DISABLE_DATE — the active date window for the rule; both are standard EBS date-tracked columns.
• OPT_ATTRIBUTE_CODE and AUTOSELECT_ON_BOOK — the option attribute reference and the on-book autoselection behavior indicator.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for capturing setup-specific metadata.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ROWID) — standard audit and row identification columns.

Common Use Cases and Queries

The most frequent use case is auditing which components an autoselection rule will bring into a configuration, and in what order. The following query retrieves the autoselected components for a given organization, ordered by sort code:

SELECT autoselection_id,
       range_id,
       assignment_id,
       inventory_item_name,
       uom,
       quantity,
       component_code,
       component_sort_code,
       effectivity_date,
       disable_date
  FROM cz_autoselection_items_v
 WHERE organization_id = :org_id
   AND TRUNC(SYSDATE) BETWEEN NVL(effectivity_date, SYSDATE)
                          AND NVL(disable_date, SYSDATE + 1)
 ORDER BY component_sort_code;

A second common scenario is validating that every autoselected item resolves to an active item master record. Since the view performs an inner join to MTL_SYSTEM_ITEMS_KFV, orphaned CZ_AUTOSELECTION_ITEMS rows (whose item is missing or belongs to another organization) will not appear. Comparing a COUNT from the base CZ table against the view is therefore a reliable integrity check.

A third use case is extracting pricing-relevant autoselections by filtering on PRICE_FLAG, and a fourth is reporting by effectivity window to identify rules that expire within a given period. Because the view is a read-only projection with an inner join, queries should always supply ORGANIZATION_ID where possible to restrict the result set and leverage the organization-scoped access path.