Results for “czfv_config_object_attributes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view CZFV_CONFIG_OBJECT_ATTRIBUTES is a Bills of Material (BOM) module database object delivered within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 code environment. Its metadata designation records it as "Retrofitted," indicating that the object was carried forward from an earlier release architecture into the current Release 12.x code line, typically in support of backward compatibility rather than active functional use. The view belongs to the family of configuration-oriented database objects associated with Oracle's model and configuration infrastructure, where it exposes descriptive attribute metadata tied to a specific flexfield-keyed system entity.

The view presents a denormalized, read-only projection of attribute definitions drawn from the Application Object Library (AK) attribute dictionary, joined against application and object registration data. It presents the object name, attribute code, attribute name, owning application name, and the database object against which the attribute is defined, together with standard audit columns. In reporting and integration contexts, such a view is useful when an extract must enumerate the configured attributes registered against a designated database object, along with the application that owns each attribute definition. The view carries a WITH READ ONLY constraint, so it can be queried only; no DML is possible against it.

Underlying Base Objects

The documented metadata records the owner field as blank and states that no referenced base objects are separately documented. The view text, however, shows the underlying dictionary tables explicitly. The view is defined over four base objects joined in a single SELECT:

• FND_APPLICATION_VL — joined on ATTRIBUTE_APPLICATION_ID = APPLICATION_ID to supply the application name.
• AK_ATTRIBUTES_VL — joined on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID to supply the attribute name.
• AK_OBJECTS_VL — joined on DATABASE_OBJECT_NAME to supply the object name.
• AK_OBJECT_ATTRIBUTES — the driving table providing the attribute registrations, object references, and audit columns.

The join conditions confirm that attribute identity is qualified by both the attribute code and the owning application, ensuring uniqueness across applications. The view text applies a restricting predicate on DATABASE_OBJECT_NAME equal to 'MTL_SYSTEM_ITEMS_KFV' and ATTRIBUTE_APPLICATION_ID equal to 702, meaning the view is effectively scoped to the attributes registered by the application with ID 702 against the key flexfield view for system items.

Key Columns

The columns projected by the view include:

• OBJECT_NAME — the name of the registered object, derived from the object dictionary VL view.
• ATTRIBUTE_ID — the attribute identifier exposed by the view's column list.
• ATTRIBUTE_NAME — the descriptive attribute name from the attribute dictionary.
• ATTRIBUTE_APPLICATION_NAME — the application name resolved from ATTRIBUTE_APPLICATION_ID via the application VL view. This is the column most commonly matched when searching for "attribute_application_name," as it corresponds directly to the projection of AP.APPLICATION_NAME.
• DATABASE_OBJECT_NAME — the database object against which the attribute is defined, constrained to MTL_SYSTEM_ITEMS_KFV.
• ATTRIBUTE_APPLICATION_ID — the numeric application identifier, fixed at 702 by the view predicate.
• CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — standard audit columns carried from AK_OBJECT_ATTRIBUTES.

Common Use Cases and Queries

Because the view is restricted to a single database object and a single application ID, its practical utility is narrow. It is most applicable when confirming which attributes are registered against the system items key flexfield view and which application owns them. A representative query is:

SELECT object_name, attribute_name, attribute_application_name, database_object_name FROM czfv_config_object_attributes ORDER BY attribute_name;

Additional filtering may be applied on the audit columns for change tracking, for example selecting rows updated after a given date. The view supports troubleshooting of attribute registration mismatches, verification of application ownership during patching analysis, and dependency review before modifications to the system items flexfield structure. As the metadata notes "Not implemented in this database," availability in any given environment should be confirmed by querying the data dictionary before the view is relied upon in custom code or integration extracts.