Search Results wf_lookup_types




Overview

WF_LOOKUP_TYPES is a multilingual (translated) view owned by the APPS schema in Oracle E-Business Suite. It exposes the workflow lookup types that drive the Oracle Workflow engine, presenting the surviving language-specific values defined for each lookup type registered against an item type. In the context of FND – Application Object Library, this view serves as the reporting and integration surface for lookup type metadata used throughout workflow-enabled applications. Because it is a view rather than a table, it provides a read-only, language-aware projection of the underlying translation table, allowing reports, concurrent programs, and external integrations to retrieve lookup type definitions without concern for the multi-row storage that exists beneath it. It is documented as VALID and is available in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object: WF_LOOKUP_TYPES_TL. In the APPS schema this base object is accessed through a synonym. WF_LOOKUP_TYPES_TL is the translated (TL) table that stores one row per lookup type per installed language. The view applies a language filter using the session language, shown in the view text as WHERE B.LANGUAGE = USERENV('LANG'). The columns are aliased from the base table (B.ROWID, B.LOOKUP_TYPE, B.ITEM_TYPE, B.PROTECT_LEVEL, B.CUSTOM_LEVEL, B.DISPLAY_NAME, B.DESCRIPTION), with ROW_ID derived from the base table ROWID. Consequently, the view returns only the rows whose LANGUAGE matches the language of the current user session; it does not perform a translated fallback to a base language, which is a behavior worth noting when querying in a language that lacks translations.

Key Columns

  • ROW_ID — The ROWID of the corresponding row in WF_LOOKUP_TYPES_TL, useful as a unique physical row identifier.
  • LOOKUP_TYPE — The internal name identifying the lookup type. This is the key used throughout Workflow APIs and lookup value resolution.
  • ITEM_TYPE — The workflow item type to which the lookup type belongs, establishing the application or workflow context of the lookup.
  • PROTECT_LEVEL — The protection level governing whether the lookup type may be modified, controlling customization safety and upgrade behavior.
  • CUSTOM_LEVEL — The customization level indicating the extent to which the definition has been customized from its seeded state.
  • DISPLAY_NAME — The translated, user-facing name of the lookup type.
  • DESCRIPTION — The translated descriptive text associated with the lookup type.

Common Use Cases and Queries

Typical uses include auditing seeded versus customized lookup types, listing all lookup types for a given item type, and validating that translations exist for the languages in use. A basic query lists all lookup types visible in the current session language:

SELECT lookup_type, item_type, display_name
FROM apps.wf_lookup_types
ORDER BY item_type, lookup_type;

To restrict results to a specific workflow item type:

SELECT lookup_type, display_name, description, protect_level, custom_level
FROM apps.wf_lookup_types
WHERE item_type = 'WFSTANDARD';

To identify customized definitions, filter on the customization level:

SELECT lookup_type, custom_level, protect_level
FROM apps.wf_lookup_types
WHERE custom_level = 'U';

Because the view filters by USERENV('LANG'), queries executed under different session languages may return differing display names or may return no rows where translations are absent. Integrations retrieving lookup type metadata should therefore be run under a known, supported language setting, or query WF_LOOKUP_TYPES_TL directly when all language rows are required.