Search Results get_pref2

Overview

WF_PREF is an Oracle Workflow utility package owned by the APPS schema and maintained as a VALID database object across Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to manage user-level workflow preferences, controlling how notifications, electronic mail delivery, and related workflow behavior are presented and applied for individual Oracle EBS users. The package acts as the persistence and rendering layer behind the Workflow Preferences user interface, translating form submissions and framework-based (OA Framework / OAF) page requests into rows within the FND_USER_PREFERENCES store, and retrieving those settings when workflow components require them. Because preferences govern notification routing, language, territory, and document-management behavior, WF_PREF sits between end-user configuration screens and the workflow runtime components that consume those settings. The object is classified as OTHER in the ETRM API registry and exposes a documented surface of twelve procedures and functions.

Key Procedures and Functions

The documented interface contains twelve callable units. GET_PREF and GET_PREF2 are accessor functions that retrieve stored preference values for a given user and preference context; GET_PREF2 provides an alternate signature used by later framework variants. UPDATE_PREF persists individual preference changes, while UPDATE_PREF_FWK and UPDATE_PREF_FWK2 perform the equivalent persistence logic for the Oracle Applications Framework-based preferences pages. EDIT and EDIT_FORM render the preferences editing experience itself — EDIT_FORM is the form-based entry point invoked from the Workflow preferences form, and EDIT supports the corresponding editing flow. LANG_LOV, TERR_LOV, and DM_LOV supply list-of-values data for language, territory, and document-management (DM) node selection respectively, populating the LOV windows attached to the preferences interface. CREATE_REG_BUTTON builds the HTML for the "Register" style button rendered on preference pages, and GET_OPEN_LOV_WINDOW_HTML returns the HTML markup used to open an LOV window. Collectively these units separate read, write, form-rendering, framework-rendering, and LOV/HTML presentation concerns.

Tables Accessed

WF_PREF reads and writes a small, focused set of tables through APPS synonyms. FND_USER_PREFERENCES is the principal data store: individual preference name/value pairs for each user are written by the UPDATE_PREF family and read by GET_PREF and GET_PREF2. FND_DM_NODES is queried to populate the document-management LOV (DM_LOV), reflecting the integration between workflow notification preferences and document management node selection. WF_RESOURCES is accessed for messages and resource lookups used when rendering labels and prompts in the preferences UI. DUAL is used for scalar evaluation and default retrieval, and HTP is referenced for HTML generation routines used by CREATE_REG_BUTTON and GET_OPEN_LOV_WINDOW_HTML.

Usage Notes

WF_PREF is normally invoked indirectly rather than called from custom code. Its most common callers are the Workflow preferences form and the OA Framework preferences pages, which drive EDIT, EDIT_FORM, the LOV procedures, and the UPDATE_PREF variants, while WFA_HTML and WFA_SEC invoke it when rendering self-service workflow administration HTML. Workflow runtime packages such as WF_INITIATE, WF_ROUTE, WF_QUEUE, and WF_PREF itself consult it when notification delivery or routing behavior depends on user preferences. It is also referenced by FND_DOCUMENT_MANAGEMENT, ICX_QUESTIONS_ADMIN, OKC_ASYNC_PVT, and the HR position/role packages PQH_POS_ROLES and PQH_ROLE_ROLES. Because it is referenced by fourteen other packages, customizations should call the documented GET_PREF and UPDATE_PREF entry points rather than modifying FND_USER_PREFERENCES directly, ensuring that framework and form behavior remain consistent. No standalone concurrent program is documented for this package.