Search Results execute_role




Overview
Explore in AI Chat

Overview

WF_ITEM_TYPES_VL is a translatable (VL, "view language") view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND – Application Object Library product and is registered as a VALID database object. The view functions as the descriptive-flexfield-style interface to the Oracle Workflow item type repository. In the Workflow architecture, an "item type" defines a reusable business object—such as a requisition, an order, or an approval process—together with the roles and persistence rules that govern access to it. WF_ITEM_TYPES_VL presents one row per item type in the session's language, combining the operational and security attributes stored in the base table with the translated display name and description. Because it is a VL view, Oracle Applications exposes it to reporting tools (Oracle Reports, BI Publisher, OA Framework, and ad hoc SQL), and it is the preferred access point over the underlying base table whenever display text is required. The view is most commonly encountered in Workflow administration, notification configuration, and security audits in which the READ_ROLE, WRITE_ROLE, and EXECUTE_ROLE assignments must be reviewed. The user search term "write_role" maps directly to one of the view's exposed columns, indicating that this object is the canonical source for determining which role has update authority over a given Workflow item type.

Underlying Base Objects

The view is defined over two documented base objects, both of which are exposed through synonyms in the APPS schema:

The view joins these two tables on NAME and filters the translation table by the session language using the USERENV('LANG') function, so that each query returns the display text appropriate to the runtime environment. The ROW_ID column is derived from the ROWID of the base WF_ITEM_TYPES row, providing a stable row identifier for the joined result set. The VL construct is standard Oracle Applications translated-view design: the base (non-VL) table remains the update target, while the VL view serves as the read interface that presents language-appropriate content. Because both referenced objects are synonyms, the view resolves against the Workflow schema objects without exposing that schema directly to the APPS user.

Key Columns

  • ROW_ID — ROWID of the underlying WF_ITEM_TYPES row; useful for row-level identification.
  • NAME — the internal, untranslated identifier of the item type (for example, standard Workflow item types such as those used for notifications and approval flows).
  • PROTECT_LEVEL — the protection level controlling whether the item type may be modified or deleted.
  • CUSTOM_LEVEL — the customization level permitted for the item type.
  • WF_SELECTOR — the selector function or callback used to resolve the item type at runtime.
  • READ_ROLE — the role granted read access to items of this type.
  • WRITE_ROLE — the role granted update authority; this is the column most relevant to the user's "write_role" search and is central to Workflow security configuration.
  • EXECUTE_ROLE — the role permitted to execute activities within the item type.
  • PERSISTENCE_TYPE and PERSISTENCE_DAYS — define how long item data is retained and the persistence model applied.
  • DISPLAY_NAME and DESCRIPTION — language-specific text drawn from WF_ITEM_TYPES_TL.

Common Use Cases and Queries

The view is typically queried to audit role-based access, to catalogue item types, or to feed integration and reporting layers. A frequent pattern is a security review of write authority across all active item types:

  • SELECT NAME, DISPLAY_NAME, READ_ROLE, WRITE_ROLE, EXECUTE_ROLE FROM WF_ITEM_TYPES_VL ORDER BY NAME;
  • SELECT NAME, DISPLAY_NAME, WRITE_ROLE FROM WF_ITEM_TYPES_VL WHERE WRITE_ROLE IS NOT NULL; — identifies every item type whose write access has been explicitly restricted.
  • SELECT NAME, DISPLAY_NAME, PERSISTENCE_TYPE, PERSISTENCE_DAYS FROM WF_ITEM_TYPES_VL WHERE PERSISTENCE_DAYS IS NOT NULL; — supports retention and purge planning.

Because the view filters on USERENV('LANG'), display names and descriptions automatically return in the language of the connected session, making it suitable for multilingual reporting without additional joins. When the metadata or configuration itself must be modified, the underlying WF_ITEM_TYPES and WF_ITEM_TYPES_TL tables are the appropriate targets; WF_ITEM_TYPES_VL should be treated as a read-only reporting and integration interface.