Results for “wf_lookups”

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

Overview

The WF_LOOKUPS view is a language-resolved reporting layer over the Workflow QuickCode repository within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Owned by the APPS schema and catalogued under the FND — Application Object Library product, it exposes the lookup values that drive Oracle Workflow behavior, including item type attribute validation, notification routing, message attributes, and various seeded configuration lists. Because Workflow relies extensively on QuickCodes for its configurable behavior, this view serves as the canonical read-only access point for inspecting the lookup definitions that the Workflow engine and its dependent modules consult at runtime.

The view is defined in ETRM documentation as a VALID object with the description "Workflow QuickCodes." It is not a transactional table; rather, it is a convenience projection designed to present lookup data already localized to the session's language, making it suitable for reports, diagnostic queries, and integration extracts that must respect the runtime language preference of the user or concurrent process.

Underlying Base Objects

WF_LOOKUPS is documented as being defined over the base object WF_LOOKUPS_TL, referenced through a SYNONYM. The view text confirms this dependency directly:

• WF_LOOKUPS_TL — the translation-level ("TL") table that stores lookup type, code, meaning, and description per language.
• The view filters that table with B.LANGUAGE = USERENV('LANG'), so only rows matching the current session language are returned.
• The ROW_ID column is projected from B.ROWID, providing a pseudo-key into the underlying TL row.

This TL-based design is consistent with the FND lookup architecture in EBS, where the base lookup definition (lookup type, code, protection and customization levels) is held in the language-independent table, while the translated attributes (meaning, description) reside in the _TL companion. WF_LOOKUPS collapses both into a single, language-filtered surface, sparing its consumers the need to join or filter on language themselves.

Key Columns

• ROW_ID — the ROWID of the underlying WF_LOOKUPS_TL row; useful for correlated updates or diagnostics but not a business key.
• LOOKUP_TYPE — the category under which the code is grouped; in the Workflow context this identifies the specific QuickCode set (for example, workflow item states or notification priorities).
• LOOKUP_CODE — the internal code value consumed by Workflow logic and stored in dependent columns.
• MEANING — the user-facing, translated label for the code.
• DESCRIPTION — the translated explanatory text for the code.
• PROTECT_LEVEL — the protection level that governs whether the lookup may be modified in a given environment.
• CUSTOM_LEVEL — indicates the customization access level applicable to the lookup, helping determine whether customer extensions are permitted.

Common Use Cases and Queries

Typical usage centers on presenting Workflow QuickCodes with their translated meanings in reports, LOVs, and integration feeds, and on diagnosing lookup values that drive workflow configuration. To list all codes for a given Workflow lookup type in the current session language:

• SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM APPS.WF_LOOKUPS WHERE LOOKUP_TYPE = :p_type ORDER BY LOOKUP_CODE;
• SELECT LOOKUP_TYPE, COUNT(*) FROM APPS.WF_LOOKUPS GROUP BY LOOKUP_TYPE ORDER BY LOOKUP_TYPE;
• SELECT LOOKUP_CODE, MEANING, PROTECT_LEVEL, CUSTOM_LEVEL FROM APPS.WF_LOOKUPS WHERE LOOKUP_TYPE = :p_type AND LOOKUP_CODE = :p_code;

Because the view filters on USERENV('LANG'), results automatically reflect the language of the invoking session; integrators requiring multi-language output should query WF_LOOKUPS_TL directly and apply their own language predicate. The view is read-only and should be treated strictly as a query surface — modifications to Workflow QuickCodes must be performed through the supported lookup maintenance screens to preserve the integrity of the underlying translation tables.