Search Results updateable_flag

Overview

The IBC_ATTRIBUTE_TYPES_VL view is a public, language-sensitive (VL) reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the IBC – Content Manager product module, which underpins content management functionality used in conjunction with Oracle iStore, Oracle Marketing, and related self-service applications. The view presents attribute type definitions associated with content types, combining the base (non-translated) definitional data with translated name and description data resolved to the session language.

Because it is a VL view, it returns exactly one row per attribute type per content type for the language identified by USERENV('LANG'), which makes it well suited to ad-hoc reporting, concurrent program data extraction, and integration interfaces where a single readable label per record is required. The UPDATEABLE_FLAG column, which is the field most often searched against this object, indicates whether end users are permitted to modify the attribute value when authoring or editing content. The view itself is not intended for DML; it exists to expose the underlying tables in a flattened, joined form for query access.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

• IBC_ATTRIBUTE_TYPES_B – the base table holding the language-independent attribute type definition, aliased as B in the view SQL.
• IBC_ATTRIBUTE_TYPES_TL – the translation table holding language-specific attribute type names and descriptions, aliased as T.
• IBC_CONTENT_TYPES_TL – the translation table for content types, aliased as CTTL, joined to supply the translated content type name.

The join conditions link B.ATTRIBUTE_TYPE_CODE = T.ATTRIBUTE_TYPE_CODE and B.CONTENT_TYPE_CODE = T.CONTENT_TYPE_CODE, with the content type name resolved through B.CONTENT_TYPE_CODE = CTTL.CONTENT_TYPE_CODE. All three tables are further constrained by a common language predicate (T.LANGUAGE = CTTL.LANGUAGE AND T.LANGUAGE = USERENV('LANG')), which is the defining characteristic of a VL view. The view also surfaces B.ROWID as ROW_ID.

Key Columns

• ATTRIBUTE_TYPE_CODE and CONTENT_TYPE_CODE – composite key identifying the attribute type within its owning content type.
• ATTRIBUTE_TYPE_NAME and DESCRIPTION – translated, user-facing text sourced from IBC_ATTRIBUTE_TYPES_TL.
• CONTENT_TYPE_NAME – translated content type label from IBC_CONTENT_TYPES_TL.
• FLEX_VALUE_SET_ID – references the value set used when the attribute data type relies on a key flexfield validation.
• DATA_TYPE_CODE and DATA_LENGTH – define the expected value type and length for the attribute.
• MIN_INSTANCES and MAX_INSTANCES – cardinality constraints indicating whether the attribute is single or repeating.
• REFERENCE_CODE and DEFAULT_VALUE – default and lookup-related settings for the attribute.
• UPDATEABLE_FLAG – indicates whether the attribute may be modified by users; typically Y for editable and N for read-only or system-derived attributes. This flag is central to controlling the content authoring experience.
• Standard WHO and concurrency columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER), plus SECURITY_GROUP_ID for multi-tenant security.

Common Use Cases and Queries

Typical uses include auditing which attributes are user-editable, generating attribute catalogues for a content type, and driving integration extracts. The following query lists editable attributes for all content types:

SELECT CONTENT_TYPE_NAME, ATTRIBUTE_TYPE_NAME, DATA_TYPE_CODE, UPDATEABLE_FLAG
FROM APPS.IBC_ATTRIBUTE_TYPES_VL
WHERE UPDATEABLE_FLAG = 'Y'
ORDER BY CONTENT_TYPE_NAME, ATTRIBUTE_TYPE_NAME;

To inspect the cardinality and value set binding of attributes for a specific content type:

SELECT ATTRIBUTE_TYPE_CODE, ATTRIBUTE_TYPE_NAME, FLEX_VALUE_SET_ID,
      MIN_INSTANCES, MAX_INSTANCES, DEFAULT_VALUE
FROM APPS.IBC_ATTRIBUTE_TYPES_VL
WHERE CONTENT_TYPE_CODE = :p_content_type;

Because the view enforces the session language, reports run under different language settings will render translated names accordingly, making it suitable for multilingual deployments on both 12.1.1 and 12.2.2.