Results for “wfpref_mailp”

6 results




Overview
Explore in AI Chat

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

Overview

APPS.JTA_UM_MAIL_PREFERENCE_V is a reporting view in Oracle E-Business Suite that exposes the set of seeded and user-selectable mail preference codes maintained by the Oracle Workflow notification mailer. It is one of a family of lookups (the "UM" prefix denotes user management) used by the Oracle Application Object Library and the Workflow user interface to render the mail-processing preference list boxes seen in the Workflow Administrator and personal notification preference pages.

The name JTA_UM_MAIL_PREFERENCE_V is the identifier returned when a user searches ETRM for the term wfpref_mailp, because the view's defining predicate is NAME LIKE 'WFPREF_MAILP%'. The view is therefore the EBS-facing façade over a specific slice of the WF_RESOURCES table rather than a distinct physical object. It presents two derived columns: a short code extracted from the resource name and a truncated description taken from the resource text. Because it is defined with USERENV('LANG'), the rows returned are automatically filtered to the session's current language, giving the view multilingual behavior without additional coding.

Underlying Base Objects

The view is owned by APPS and is defined over a single referenced base object: WF_RESOURCES, accessed through a synonym. WF_RESOURCES is the Oracle Workflow repository of named, language-specific string resources. Each row carries a NAME, a TEXT value, and a LANGUAGE attribute; the naming convention used by the Workflow mailer encodes the preference identifier after a hyphen. The view filters on the prefix WFPREF_MAILP and on the session language, so the effective join is a single-table projection with a LIKE predicate rather than a multi-table join.

Key Columns

  • CODE — Derived as SUBSTR(NAME, INSTR(NAME,'-')+1). This strips the WFPREF_MAILP- prefix and yields the bare mail preference token, which is the value stored against a user's notification preference.
  • DESCRIPTION — Derived as SUBSTR(TEXT, 1, 40). This is the first forty characters of the localized resource text, providing the displayable label for the preference.

No other columns are projected by the view. The underlying WF_RESOURCES columns NAME, TEXT, and LANGUAGE are consumed internally for filtering and derivation but are not exposed directly.

Common Use Cases and Queries

The view is typically used to populate LOVs and validation lists for notification mail preferences, and to resolve a stored preference code back to a readable description for reporting.

  • Populating a preference list of valid mail-processing options for a personalization or administrator page.
  • Translating a stored preference token into a human-readable label on a Workflow notification report.
  • Auditing which mail preferences are seeded in the current language after a patch or upgrade.

A basic retrieval of all available mail preference codes in the session language:

SELECT code, description
FROM   apps.jta_um_mail_preference_v
ORDER BY code;

Resolving a single preference token to its description:

SELECT description
FROM   apps.jta_um_mail_preference_v
WHERE  code = :p_preference_code;

Where the target code is unknown, the same result can be obtained directly from the base resource table by matching the full resource name:

SELECT SUBSTR(name, INSTR(name,'-')+1) code,
       SUBSTR(text, 1, 40) description
FROM   wf_resources
WHERE  name LIKE 'WFPREF_MAILP-' || :p_preference_code
AND    language = USERENV('LANG');

Because the view depends on USERENV('LANG'), callers must ensure the session language is initialized (for example via FND_GLOBAL or the EBS session context) before querying, otherwise rows for the expected language may be absent.