Results for “cz_inst_attr_values_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view CZ_INST_ATTR_VALUES_V is a Bills of Material (BOM) database object that exposes item attribute values associated with flexible attribute definitions in Oracle EBS Release 12.1.1 and 12.2.2. It functions as a consolidated reporting and integration interface over the Oracle Application Object Library (AK) attribute model, presenting instance-level attribute values in a form that is directly joinable to descriptive and extensible flexfield metadata. The view is particularly significant for consumers who store or search item attribute data by data type, because it performs an explicit type-aware projection of attribute values. The user query "value_varchar2" reflects this role: CZ_INST_ATTR_VALUES_V normalizes disparate underlying storage columns into a single ATTRIBUTE_VALUE output, and for attributes whose AK.DATA_TYPE is VARCHAR2 it exposes the raw VALUE_VARCHAR2 content. The view is documented as not implemented in the target database, meaning it is a seeded definition that exists in the ETRM metadata and application dictionary but may not be instantiated in every instance. It is owned by the BOM product and is not part of a documented public API, so it should be treated as an internal reporting view rather than a supported integration endpoint.
Underlying Base Objects
The view is defined over three AK objects through an inner-join construction:
- AK_INST_ATTRIBUTE_VALUES V — the instance-level attribute value store, holding the key values and the type-specific value columns (VALUE_VARCHAR2, VALUE_NUMBER).
- AK_OBJECT_ATTRIBUTES O — the mapping between database objects and registered attributes.
- AK_ATTRIBUTES_VL AK — the attribute definition table, supplying the DATA_TYPE discriminator.
The joins require equality on DATABASE_OBJECT_NAME, ATTRIBUTE_APPLICATION_ID (fixed at 702), and ATTRIBUTE_CODE across the three objects. The predicate V.DATABASE_OBJECT_NAME = 'MTL_SYSTEM_ITEMS_KFV' restricts the view to attributes registered against the item key flexfield view, which is the basis of the Item Attribute Values feature in BOM. No other base objects are documented as referenced. Because application ID 702 is hard-coded, the view returns only attributes owned by the BOM application.
Key Columns
- DATABASE_OBJECT_NAME — the registered object name, constrained to MTL_SYSTEM_ITEMS_KFV.
- KEY_VALUE1 through KEY_VALUE10 — the attribute key segment values that identify the specific instance record being described.
- ATTRIBUTE_APPLICATION_ID — the owning application, fixed at 702 for this view.
- ATTRIBUTE_CODE — the internal attribute identifier used for joining to the attribute definition.
- DATA_TYPE — the declared AK data type of the attribute, such as VARCHAR2 or NUMBER.
- ATTRIBUTE_VALUE — the computed value returned by DECODE on DATA_TYPE: VALUE_VARCHAR2 for VARCHAR2 attributes, VALUE_NUMBER for NUMBER attributes, and -999 when the type is not one of these two.
Common Use Cases and Queries
The view supports reporting on item attribute values where the value is stored in a type-specific column and must be surfaced uniformly. The following query returns all VARCHAR2-typed item attribute values, which directly addresses the "value_varchar2" search term:
- SELECT ATTRIBUTE_CODE, DATA_TYPE, ATTRIBUTE_VALUE FROM CZ_INST_ATTR_VALUES_V WHERE DATA_TYPE = 'VARCHAR2';
- SELECT ATTRIBUTE_CODE, ATTRIBUTE_VALUE FROM CZ_INST_ATTR_VALUES_V WHERE KEY_VALUE1 = :item_id;
- SELECT DATA_TYPE, COUNT(*) FROM CZ_INST_ATTR_VALUES_V GROUP BY DATA_TYPE;
Consumers should note the -999 sentinel returned for unsupported data types and filter accordingly, and should confirm view availability in the target instance given the documented "not implemented" status before embedding it in production queries.
-
View: CZ_INST_ATTR_VALUES_V 12.2.2
Item attribute values
Not implemented in this database·Explore BOM module →
-
View: CZ_INST_ATTR_VALUES_V 12.1.1
Item attribute values
Not implemented in this database·Explore BOM module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1