Results for “wf_core”

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

Overview

WF_CORE is the foundational utility package of the Oracle Workflow engine in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It resides in the APPS schema and holds a status of VALID. Unlike functional packages that implement a specific business process, WF_CORE provides the low-level infrastructure services that every other Workflow component depends upon: token substitution, resource lookups, error handling, date and context retrieval, hashing, and miscellaneous string manipulation routines. Because Oracle Workflow underpins a large proportion of EBS subsystems — including approvals, notifications, and event subscriptions — WF_CORE is effectively a shared services layer.

The metadata classifies the package as API classification OTHER, reflecting its role as an internal support library rather than a subscriber-facing API. The very high reference count — 793 dependent packages — confirms its position as one of the most widely consumed utilities in the APPS schema. No database object references WF_CORE within the documented dependency set, indicating that it sits near the bottom of the Workflow dependency chain and consumes only a small, stable set of resources and system views.

Key Procedures and Functions

The ETRM documentation lists 33 documented procedures and functions. Representative members include:

• TOKEN — Core token substitution routine used to replace message tokens with runtime values during notification generation and message rendering.
• SUBSTITUTE and SUBSTITUTESPECIALCHARS — Perform substitution of token placeholders, including handling of special or reserved characters that could otherwise corrupt message text.
• TRANSLATE — Applies language translation to Workflow text elements.
• GETRESOURCE and GETRESOURCES — Retrieve string resources from the WF_RESOURCES repository.
• GET_ERROR — Returns error information for the calling Workflow context.
• RAISE — Raises a Workflow-defined error, integrating with the engine's error-handling framework.
• CONTEXT — Returns the current Workflow execution context.
• ACTIVITY_RESULT — Obtains or records the result of a Workflow activity.
• RANDOM — Generates a random value, commonly used for identifiers or selection logic.
• HASHKEY — Produces a hash value for keys, supporting internal lookup and integrity logic.
• CLEAR — Clears cached or held state.
• INITCACHE — Initialises the package cache used by resource and context routines.
• NLS_DATE_FORMAT — Exposes the session NLS date format for use in message formatting.
• NEWLINE, TAB, CR, and LOCAL_CHR — Character constants and conversion helpers for formatting message bodies.
• CHECKILLEGALCHARS — Validates input for characters that are not permitted in Workflow text.

Many of these routines are overloaded and are called by hundreds of dependent packages, so their signatures are effectively frozen in supported releases.

Tables Accessed

WF_CORE reads and writes through APPS synonyms. The principal objects are:

• WF_RESOURCES — The Workflow string resource repository, consumed by GETRESOURCE and GETRESOURCES and INITCACHE.
• FND_SVC_COMPONENTS — The service component registry, used to determine component context.
• DBA_EDITIONS — The edition registry, consulted to detect Edition-Based Redefinition state during 12.2.x operation.
• V$INSTANCE, V$NLS_PARAMETERS, V$PARAMETER, V$SESSION — Dynamic performance views read for instance identity, NLS settings, and session context.
• DBMS_UTILITY, DBMS_APPLICATION_INFO — Supplied PL/SQL packages invoked for utility services and session activity registration.

Usage Notes

WF_CORE is almost always invoked indirectly. Functional Workflow packages, notification mailers, approval management forms, and event subscription routines call its procedures rather than applications calling WF_CORE directly. Custom PL/SQL that needs to resolve a Workflow resource string or format a message token should use the documented interfaces rather than query WF_RESOURCES directly, because WF_CORE applies caching, NLS handling, and special-character substitution that ad hoc SQL would bypass. Direct invocation is common only in diagnostics, and is generally restricted to read-only helpers such as GET_ERROR, GETRESOURCE, and NLS_DATE_FORMAT.

Because the package body is VALID and referenced by 793 database objects, it should be treated as sealed production infrastructure. Modifications invalidate a substantial proportion of the APPS schema and are unsupported under the Oracle EBS patch and support model.