Results for “wf_item_types_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WF_ITEM_TYPES_TL is the translation table for the Oracle Workflow item type definition stored in WF_ITEM_TYPES. It resides in the APPLSYS schema and belongs to the FND – Application Object Library product family. An item type is the fundamental unit of workflow definition in Oracle EBS: it groups together the attributes, messages, functions, notifications, and process activities that constitute a workflow-enabled business object, such as an order, a requisition, or an expense report. Because item types must be presented to users in their own language, the base WF_ITEM_TYPES table holds language-independent definition data, while WF_ITEM_TYPES_TL holds the translatable text used at runtime and in the Workflow Builder interface.
The table is classified heuristically as standalone under the Data Vault modeling scheme mined from its foreign key structure. In practice this classification suggests the object behaves as a standalone descriptive table rather than a pure hub or satellite, though a modeler may reasonably treat it as a satellite of the WF_ITEM_TYPES hub keyed by NAME, since its rows carry attribute-level text (display name, description) that varies over language and edition rather than representing a distinct business entity.
Key Information Stored
The table contains nine documented columns. The most important are:
- NAME — the internal item type identifier (for example, FND_STANDARD or PO_APPROVAL). This is the value that links the translation row back to the base item type definition.
- LANGUAGE — the language code of the translated text, stored as an NLS language identifier such as US or DE.
- DISPLAY_NAME — the user-visible name of the item type in the given language. This is the translatable attribute most commonly surfaced in Workflow Builder and in notification headers.
- DESCRIPTION — a longer free-text explanation of the item type's purpose, translated per language.
- SOURCE_LANG — the language from which the row was originally derived, used by the translation and patching infrastructure to track translation provenance.
- SECURITY_GROUP_ID — the security group under which the item type is visible; this column carries a foreign key to FND_SECURITY_GROUPS and participates in the multi-org/security filtering applied by Workflow.
- PROTECT_LEVEL and CUSTOM_LEVEL — protection and customization levels that govern whether Oracle-supplied or customer-modified definitions may be altered or overwritten during upgrades.
- ZD_EDITION_NAME — an editioning column present in the 12.2.2 online patching architecture, used to segregate editions during the adop cycle.
The surrogate primary key WF_ITEM_TYPES_TL_PK is defined on NAME and LANGUAGE, extended by ZD_EDITION_NAME in the 12.2.2 physical schema. A second unique index, WF_ITEM_TYPES_TL_U2 (documented as WF_ITEM_TYPES_TL_UK2 in some listings), is defined on DISPLAY_NAME, LANGUAGE, and ZD_EDITION_NAME, making DISPLAY_NAME a business-key candidate. Together these constraints ensure one translation row per item type per language and prevent duplicate display names within a language.
Common Use Cases and Queries
The most frequent use of this table is resolving the display name of an item type for a given session language when reporting on workflow activity. A typical join retrieves the translated name alongside the base definition:
- Joining WF_ITEM_TYPES_TL to WF_ITEM_NOTIFICATIONS or WF_ITEM_ACTIVITY_STATUSES to produce language-appropriate workflow status and notification reports.
- Filtering by SECURITY_GROUP_ID to restrict output to the security groups visible to a given responsibility or operating unit.
- Auditing translation coverage — identifying item types that have a base row in WF_ITEM_TYPES but no corresponding row in WF_ITEM_TYPES_TL for a target language.
- Detecting duplicate DISPLAY_NAME values across languages to pre-empt the unique key violation on WF_ITEM_TYPES_TL_U2 before importing custom translations.
A representative query pattern selects NAME, DISPLAY_NAME, and DESCRIPTION from WF_ITEM_TYPES_TL where LANGUAGE equals the session language, and joins to WF_ITEM_TYPES on NAME to obtain the runnable item type rows. Because the table is keyed on NAME and LANGUAGE, lookups should always supply both predicates to guarantee a single-row result.
Related Objects
The following objects are most significant in relation to WF_ITEM_TYPES_TL:
- WF_ITEM_TYPES — the base, language-independent definition table; join on NAME.
- FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key; join on SECURITY_GROUP_ID.
- FND_LANGUAGES — provides validation and description for the LANGUAGE column.
- WF_ITEM_ATTRIBUTES — attributes belonging to each item type, joined on the item type NAME.
- WF_ITEM_ACTIVITY_STATUSES — runtime workflow state per item, frequently reported alongside the translated item type name.
- WF_ITEM_NOTIFICATIONS — notifications generated for an item type; the translated name appears in notification subject text.
- WF_PROCESS_ACTIVITIES — process definitions scoped to an item type.
- WF_ITEM_TYPE_USAGES and the Workflow Builder API (WF_ITEM_TYPE_API) — used to define and maintain item types and their translations.
Consult the APPLSYS schema directly for authoritative column definitions, as the translation table is subject to change across EBS releases and online patching editions.
-
Translations for WF_ITEM_TYPES
-
Translations for WF_ITEM_TYPES
-
View: WF_ITEM_TYPES_VL 12.2.2
APPS.WF_ITEM_TYPES_VL·↳ WF_ITEM_TYPES·↳ WF_ITEM_TYPES_TL·Explore FND module →
-
View: WF_ITEM_TYPES_VL 12.1.1
APPS.WF_ITEM_TYPES_VL·↳ WF_ITEM_TYPES·↳ WF_ITEM_TYPES_TL·Explore FND module →
-
View: WF_WORKLIST_V 12.2.2
Public view for worklist
APPS.WF_WORKLIST_V·↳ WF_ITEM_TYPES_TL·↳ WF_LOOKUPS_TL·↳ WF_NOTIFICATIONS·Explore FND module →
-
View: WF_WORKLIST_V 12.1.1
Public view for worklist
APPS.WF_WORKLIST_V·↳ WF_ITEM_TYPES_TL·↳ WF_LOOKUPS_TL·↳ WF_NOTIFICATIONS·Explore FND module →
-
plan element actions view for electronic records
APPS.QA_ERES_PLAN_CHAR_ACTIONS_V·↳ ALR_ACTIONS·↳ ALR_DISTRIBUTION_LISTS·↳ FND_APPLICATION_TL·Explore QA module →
-
View: OKE_CHG_STATUSES_VL 12.1.1
Contract change request status multi-lingual view
APPS.OKE_CHG_STATUSES_VL·↳ FND_LOOKUP_VALUES_VL·↳ OKE_CHG_STATUSES_B·↳ OKE_CHG_STATUSES_TL·Explore OKE module →
-
plan element actions view for electronic records
APPS.QA_ERES_PLAN_CHAR_ACTIONS_V·↳ ALR_ACTIONS·↳ ALR_DISTRIBUTION_LISTS·↳ FND_APPLICATION_TL·Explore QA module →
-
View: OKE_HOLD_STATUSES_VL 12.1.1
Contract hold statuses multi-lingual view
APPS.OKE_HOLD_STATUSES_VL·↳ OKE_HOLD_STATUSES_B·↳ OKE_HOLD_STATUSES_TL·↳ WF_ITEM_TYPES_TL·Explore OKE module →
-
View: OKE_HOLD_STATUSES_VL 12.2.2
Contract hold statuses multi-lingual view
APPS.OKE_HOLD_STATUSES_VL·↳ OKE_HOLD_STATUSES_B·↳ OKE_HOLD_STATUSES_TL·↳ WF_ITEM_TYPES_TL·Explore OKE module →
-
PACKAGE: APPS.PO_WF_FUN 12.1.1
-
VIEW: APPS.WF_ITEM_TYPES_VL 12.2.2
-
VIEW: APPS.WF_ITEM_TYPES_VL 12.1.1
-
View: OKE_CHG_STATUSES_VL 12.2.2
Contract change request status multi-lingual view
APPS.OKE_CHG_STATUSES_VL·↳ FND_LOOKUP_VALUES_VL·↳ OKE_CHG_STATUSES_B·↳ OKE_CHG_STATUSES_TL·Explore OKE module →
-
View: OKE_COMM_ACTIONS_VL 12.2.2
Contract communications actions multi-lingual view
APPS.OKE_COMM_ACTIONS_VL·↳ OKE_COMM_ACTIONS_B·↳ OKE_COMM_ACTIONS_TL·↳ PER_ALL_PEOPLE_F·Explore OKE module →
-
View: OKE_COMM_ACTIONS_VL 12.1.1
Contract communications actions multi-lingual view
APPS.OKE_COMM_ACTIONS_VL·↳ OKE_COMM_ACTIONS_B·↳ OKE_COMM_ACTIONS_TL·↳ PER_ALL_PEOPLE_F·Explore OKE module →
-
PACKAGE BODY: APPS.PO_WF_FUN 12.2.2
-
PACKAGE: APPS.PO_WF_FUN 12.2.2
-
VIEW: APPS.WF_WORKLIST_V 12.2.2
-
PACKAGE BODY: APPS.PO_WF_FUN 12.1.1