Search Results base_table_column_name




Overview
Explore in AI Chat

Overview

OE_PC_ATTRIBUTES_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and defined within the Oracle Order Management (ONT) product. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is classified as a VIEW. As its description states, the view stores the attributes of sales order entities — that is, the descriptive and structural metadata that describes the columns available on Order Management entities such as order headers, order lines, and related business objects.

The view plays a key role in Oracle's attribute framework. Rather than exposing transactional sales order data, it exposes the definition of the attributes themselves, including the data type, the underlying base table and column, the display label, and constraint-related flags. This makes it a metadata repository: consumers can discover which attributes belong to a given entity, where each attribute is physically stored, and how it should be presented. Because the column list includes BASE_TABLE_COLUMN_NAME, the view is particularly relevant to report and integration developers who must map an Order Management attribute (referenced by ATTRIBUTE_CODE) back to the exact base table column that holds its value.

Underlying Base Objects

The view text joins five documented base objects, each presented through an APPS synonym: AK_OBJECT_ATTRIBUTES, AK_ATTRIBUTES, AK_ATTRIBUTES_TL, OE_AK_OBJECTS_EXT, and OE_AK_OBJ_ATTR_EXT. The AK_ tables come from the Oracle Application Object Library attribute-definition framework, while the two OE_AK_* tables are the Order Management extensions that associate those generic attribute definitions with specific sales order entities.

The joins are driven by matching DATABASE_OBJECT_NAME and ATTRIBUTE_CODE across the AK and OE extension tables, so the view returns only attributes that are registered in both the generic attribute framework and the Order Management entity extension.

Key Columns

  • ROW_ID — the row identifier of the OE_AK_OBJ_ATTR_EXT record.
  • APPLICATION_ID — the application owning the attribute definition.
  • ENTITY_ID — identifies the sales order entity to which the attribute belongs.
  • DB_OBJECT_NAME and DB_OBJECT_TYPE — the database object name and its type (the literal 'VIEW').
  • ATTRIBUTE_CODE and ATTRIBUTE_ID — the internal attribute identifier and its numeric ID.
  • COLUMN_NAME and ATTRIBUTE_DISPLAY_NAME — the column name and the translated, user-facing label.
  • DATA_TYPE, DATA_SOURCE_TYPE, DATA_STORAGE_TYPE — the attribute's data type and how/where its value is sourced and stored.
  • TABLE_NAME and BASE_TABLE_COLUMN_NAME — the physical base table and column that back the attribute, essential for mapping metadata to stored data.
  • CONSTRAINTS_ENABLED_FLAG, CONSTRAINTS_CONDN_REF_FLAG, STATE_ATTRIBUTE_FLAG — flags indicating whether constraints are enabled, whether a constraint references the attribute, and whether the attribute represents a state.
  • ATTRIBUTE_LABEL_LENGTH — the displayed label length.

Common Use Cases and Queries

Typical scenarios include attribute discovery for Order Management entities, building dynamic report or integration mappings, and resolving an attribute code to its stored base table column. A representative query filtering by entity is:

SELECT ENTITY_ID, ATTRIBUTE_CODE, ATTRIBUTE_DISPLAY_NAME, TABLE_NAME, BASE_TABLE_COLUMN_NAME, DATA_TYPE FROM OE_PC_ATTRIBUTES_V WHERE ENTITY_ID = :p_entity_id ORDER BY ATTRIBUTE_CODE;

Because the view depends on USERENV('LANG'), results reflect the runtime session language. Queries should be treated as read-only metadata lookups; the view is not intended for direct DML.