Results for “custom_level”

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

Overview

The WF_RESOURCES table is a core repository object owned by the APPLSYS schema and exposed through the FND – Application Object Library product within Oracle E-Business Suite 12.1.1 and 12.2.2. Although the metadata labels it an "Internal messages table," WF_RESOURCES functions more broadly as the central registry of translatable text resources consumed by the Oracle Workflow engine. It stores the internal messages, notification body templates, lookup text, and other named text resources that Workflow components resolve at runtime by TYPE, NAME, and LANGUAGE. Because workflow definitions and notifications are multilingual, the table maintains one row per resource per language, enabling seeded translations and customer-defined overrides to coexist without recompiling the underlying Workflow objects.

The heuristic Data Vault classification mined from the foreign-key structure identifies WF_RESOURCES as a standalone object. In Data Vault terms this suggests it behaves as a satellite-style reference table rather than a classic hub or link: it is keyed by a natural composite business key, depends on an external reference (FND_SECURITY_GROUPS), and holds descriptive attributes (TEXT, SOURCE_LANG). Modeling it as a standalone reference or satellite artefact is therefore a defensible suggestion.

Key Information Stored

The documented physical schema contains ten columns. The composite business key is defined by the unique index WF_RESOURCES_PK over TYPE, NAME, LANGUAGE, and ZD_EDITION_NAME. The columns of greatest functional importance are:

• TYPE – classifies the resource (for example message, notification subject, or error text). Part of the business key.
• NAME – the logical identifier by which Workflow code requests the resource. Part of the business key.
• LANGUAGE – the NLS language code, permitting parallel translated rows. Part of the business key.
• ID – a surrogate numeric identifier used for internal referential stability.
• TEXT – the actual message or resource body resolved at runtime.
• PROTECT_LEVEL – controls whether the seeded row may be modified or deleted by customers.
• CUSTOM_LEVEL – indicates the degree of customer customization applied to the row.
• SOURCE_LANG – the language of the original text, used by the translation/derivation process.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, isolating resources by security group.
• ZD_EDITION_NAME – the editioning column required for EBS 12.2 online patching and part of the unique key.

Common Use Cases and Queries

Typical uses include diagnosing missing or mismatched Workflow messages, auditing untranslated resources, and reviewing customer modifications to seeded text. A basic retrieval by business key:

• SELECT id, text FROM wf_resources WHERE type = :p_type AND name = :p_name AND language = :p_lang;
• Finding all languages for a resource: SELECT language, text FROM wf_resources WHERE name = :p_name ORDER BY language;
• Detecting overridden seeded content: SELECT name, type, custom_level FROM wf_resources WHERE custom_level > 0;
• Auditing by security group: SELECT r.name, r.language FROM wf_resources r, fnd_security_groups g WHERE r.security_group_id = g.security_group_id;

Related Objects

The documented foreign key binds WF_RESOURCES.SECURITY_GROUP_ID to FND_SECURITY_GROUPS, which partitions resources across security domains. Beyond that relationship, the table is consumed by the Oracle Workflow engine and related AOL objects—including the Workflow message and notification APIs (WF_NOTIFICATION, WF_MESSAGE), the WF_LOOKUP_TYPES/WF_LOOKUP_VALUES reference structures that mirror resource-style naming, and the FND_APPLICATION table through product ownership. Maintenance is typically performed through the Oracle Workflow Builder and FNDLOAD, which write new TYPE/NAME/LANGUAGE rows under editioning rules (ZD_EDITION_NAME). When querying during patching windows, always constrain the edition to the active edition name to avoid reading stale or shadow rows.