Search Results date_default




Overview
Explore in AI Chat

Overview

WF_ITEM_ATTRIBUTES_VL is a validated, multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product family and exposes the attributes defined for Oracle Workflow item types. In the Workflow architecture, an item type represents a business object (for example, an order or a requisition), and each attribute of that item type describes a data element carried by the workflow process. Because attribute display names and descriptions are translatable, the view joins the base attribute definition table with its translation table and presents the result in the language of the current session.

The view functions as the reporting and integration surface for Workflow attribute metadata. Rather than querying the underlying tables directly and manually resolving the language join, developers, report authors, and interface builders can select from WF_ITEM_ATTRIBUTES_VL and receive a single, language-appropriate row per attribute. This makes it suitable for data dictionary reports, attribute pick lists, XML Publisher or BI Publisher data models, and validation logic that must resolve an attribute's data type or default value. Notably, the view exposes DATE_DEFAULT, which is the column most directly relevant to the user search term "date_default" — it stores the default value applied to attributes whose declared TYPE is a date attribute.

Underlying Base Objects

Per the documented view text, WF_ITEM_ATTRIBUTES_VL is defined over two base objects, both referenced through APPS synonyms:

The join is performed on ITEM_TYPE and NAME, with the additional predicate T.LANGUAGE = USERENV('LANG'). This restricts the result to the single language row matching the session language, which is the defining characteristic of a _VL view. The view additionally selects B.ROWID as ROW_ID, giving each row a stable identifier tied to the base table row. Because the _VL pattern filters rather than aggregates, each base attribute maps to exactly one row in the view for a given session language.

Key Columns

  • ROW_ID — the ROWID of the underlying WF_ITEM_ATTRIBUTES row.
  • ITEM_TYPE — the internal name of the Workflow item type that owns the attribute.
  • NAME — the internal attribute name, unique within the item type.
  • SEQUENCE — the ordering of the attribute within the item type.
  • TYPE — the attribute's data type (for example, text, number, or date). This determines which default column is relevant.
  • PROTECT_LEVEL / CUSTOM_LEVEL — protection and customization settings governing whether the attribute may be modified.
  • SUBTYPE — an optional subtype classification for the attribute.
  • FORMAT — the display or validation format string associated with the attribute.
  • TEXT_DEFAULT, NUMBER_DEFAULT, DATE_DEFAULT — the typed default values. DATE_DEFAULT holds the default for date-typed attributes.
  • DISPLAY_NAME — the translated, user-facing label from WF_ITEM_ATTRIBUTES_TL.
  • DESCRIPTION — the translated description from WF_ITEM_ATTRIBUTES_TL.

Common Use Cases and Queries

Typical scenarios include listing all attributes of an item type, locating the default assigned to a date attribute, and building attribute lookup lists for forms or integrations.

List all attributes for a given item type, ordered by sequence:

SELECT ITEM_TYPE, NAME, SEQUENCE, TYPE, DISPLAY_NAME, DESCRIPTION
FROM   APPS.WF_ITEM_ATTRIBUTES_VL
WHERE  ITEM_TYPE = 'WFERROR'
ORDER  BY SEQUENCE;

Retrieve the default values, including DATE_DEFAULT, for attributes of an item type:

SELECT NAME, TYPE, TEXT_DEFAULT, NUMBER_DEFAULT, DATE_DEFAULT
FROM   APPS.WF_ITEM_ATTRIBUTES_VL
WHERE  ITEM_TYPE = 'WFERROR'
AND    TYPE = 'DATE';

Search for attributes whose display name contains a keyword, respecting session language:

SELECT ITEM_TYPE, NAME, DISPLAY_NAME
FROM   APPS.WF_ITEM_ATTRIBUTES_VL
WHERE  UPPER(DISPLAY_NAME) LIKE '%DATE%';

Because the view already resolves language via USERENV('LANG'), results automatically reflect the language of the connected session, eliminating the need for manual joins in downstream reports.