Results for “jtf_fm_email_v”

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

Overview

JTF_FM_EMAIL_V is an Oracle E-Business Suite database view owned by the APPS schema and defined within the JTF (CRM Foundation) product module. It is documented as a view referring to the JTF_FM_EMAIL table, and its purpose is to present the email account configuration records used by the CRM Foundation email framework in a stable, queryable form. The view is a thin projection: it does not alter or transform the underlying data, but exposes a defined column list that includes the RETURN_ADDRESS attribute frequently sought by implementers and support personnel. Because it resides in the APPS schema and is registered as VALID in ETRM, it is treated as a supported read interface for reporting, diagnostics, and integrations that need to resolve outbound email account details.

In both EBS 12.1.1 and 12.2.2 the object carries the same documented status and structure. Its role is primarily informational: it answers questions about which email accounts have been configured, which server and dispatcher each account uses, and which address is used as the return (from) address when messages are dispatched.

Underlying Base Objects

The documented referenced base object is JTF_FM_EMAIL, accessed through a synonym. The view definition is a direct SELECT from JTF_FM_EMAIL with no joins, unions, or aggregation, and no filtering predicates are documented. Consequently, every row in JTF_FM_EMAIL is exposed, including soft-deleted records, because the deletion indicator is carried forward as a column rather than applied as a WHERE clause. The view therefore inherits row-for-row cardinality with the base table and imposes no additional performance overhead beyond that of the base table access itself. Any index or partitioning strategy defined on JTF_FM_EMAIL remains the relevant factor for query performance.

Key Columns

• OUTPUT_ID — Primary identifier for the email output/account record.
• RETURN_ADDRESS — The return address associated with the account; the column most commonly searched for in this object.
• PHYSICAL_NAME and OUTPUT_DESC — Descriptive attributes identifying the account to users.
• OUTPUT_TYPE — Classifies the email output configuration.
• SERVER_ID and DISPATCHER_ID — References to the server and dispatcher definitions that process messages.
• OUTGOING_SERVER and INCOMING_SERVER — SMTP/POP or IMAP endpoint details; PORT supplies the corresponding network port.
• DEFAULT_FLAG — Indicates whether the account is the default for its context.
• F_DELETEDFLAG — Soft-delete indicator; must typically be filtered to exclude inactive records.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the underlying framework.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent scenario is locating the return address configured for an email account, or confirming the default account and its server settings. Diagnostics for message dispatch failures rely on the same columns to verify that an outgoing server and port are populated.

To search for a specific return address:

• SELECT output_id, physical_name, return_address, outgoing_server, port, default_flag FROM jtf_fm_email_v WHERE return_address = :return_address;

To list all active accounts and identify the default:

• SELECT output_id, output_desc, return_address, default_flag FROM jtf_fm_email_v WHERE NVL(f_deletedflag, 'N') = 'N' AND NVL(default_flag, 'N') = 'Y' ORDER BY output_desc;

Because the view exposes no filtering of its own, callers should always restrict on F_DELETEDFLAG and, where relevant, DEFAULT_FLAG to avoid returning stale configuration rows during reporting or integration lookups.