Results for “data_level_id”

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

Overview

The UDA_SETUP_METADATA_V view is a Purchasing (PO) module database object owned by the APPS schema. It provides a consolidated, read-only projection of User-Defined Attribute (UDA) setup metadata, joining descriptive flexfield definitions to their underlying extension tables and attribute-group template definitions. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the metadata backbone for the UDA framework, which allows customers to attach custom attribute groups to purchasing documents and other entities without modifying base tables.

The view is primarily consumed by setup validation, configuration reporting, and integration routines that must determine, at runtime, which attribute groups are valid, which descriptive flexfields back them, and which extension tables physically store the user-defined values. Because it filters out dummy attribute groups and archived data levels, it exposes only active, actionable setup metadata suitable for production reporting.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over four referenced base objects:

• EGO_DATA_LEVEL_VL (VIEW) — referenced twice, once as the dummy driving row and once as the real attribute-group row. Supplies ATTR_GROUP_TYPE, DATA_LEVEL_ID, DATA_LEVEL_NAME, and USER_DATA_LEVEL_NAME.
• EGO_OBJECT_EXT_TABLES_B (SYNONYM) — supplies OBJECT_ID, APPLICATION_ID, and the physical extension table name.
• FND_DESCRIPTIVE_FLEXS (SYNONYM) — links the descriptive flexfield name to its application table, aligning the flexfield definition with the physical extension table.
• PO_UDA_AG_TEMPLATES_VL (VIEW) — supplies template metadata including TEMPLATE_ID, DISPLAY_NAME (template name), and REVISION via an outer join on ENTITY_CODE.

The join logic establishes a chain from the dummy data level through the real data level, the descriptive flexfield, the object extension table, and finally the optional attribute-group template. The outer join (TEMPLATES.ENTITY_CODE(+)) permits attribute groups without an associated template to remain visible.

Key Columns

• OBJECT_ID — Identifier of the extensible object that owns the extension table.
• APPLICATION_ID — Application owning the object, used to scope metadata by module.
• EXTENSION_TABLE — The physical database table storing UDA values; derived from the flexfield's application table name.
• ATTR_GROUP_TYPE — The attribute group (descriptive flexfield) name; the central linkage column.
• TEMPLATE_ID / TEMPLATE_NAME / REVISION — Attribute-group template identity, display label, and version, nullable when no template exists.
• DATA_LEVEL_ID — Identifier of the data level governing attribute-group ordering or hierarchy.
• DATA_LEVEL_NAME — The internal name of the data level; the column most frequently searched for by users investigating UDA setup (e.g., data_level_name).
• USER_DATA_LEVEL_NAME — The user-facing label for the same data level.

Common Use Cases and Queries

Typical scenarios include auditing which attribute groups are active, locating the extension table that stores UDA values, and confirming template revisions prior to data migration. To list all active setup metadata for a given data level:

• SELECT data_level_id, data_level_name, user_data_level_name, attr_group_type, extension_table FROM uda_setup_metadata_v WHERE data_level_name = :level_name;
• SELECT attr_group_type, template_name, revision, extension_table FROM uda_setup_metadata_v WHERE template_name IS NOT NULL ORDER BY attr_group_type;
• SELECT DISTINCT user_data_level_name FROM uda_setup_metadata_v ORDER BY 1;

These queries support configuration reporting, dependency analysis before flexfield changes, and integration metadata lookups in both 12.1.1 and 12.2.2 environments.