Results for “jtf_fm_email”

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

Overview

JTF_FM_EMAIL is a CRM Foundation (JTF) configuration table that stores information about the fulfillment email servers used by Oracle E-Business Suite's fulfillment management infrastructure. It defines the email server endpoints, return addresses, and dispatcher associations that the fulfillment engine uses when processing outbound and inbound email-based fulfillment requests. The table resides in the JTF schema and is valid in both EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined FK structure suggests this object is satellite-leaning. It carries descriptive attributes (server names, addresses, flags) that attach to parent entities such as JTF_FM_DISPATCHERS and FND_SECURITY_GROUPS, and it is itself referenced by a group-mapping table. Rather than acting as an independent hub of business events, JTF_FM_EMAIL functions as a dependent descriptor set.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• OUTPUT_ID — Identifier for the fulfillment output configuration; part of the composite primary key.
• OUTPUT_TYPE — Type discriminator for the output; part of the composite primary key.
• DISPATCHER_ID — Foreign key to JTF_FM_DISPATCHERS; identifies the dispatcher responsible for this email output. Part of the composite primary key.
• SERVER_ID — Foreign key column linking to the email server definition. Part of the composite primary key.
• OUTGOING_SERVER and INCOMING_SERVER — SMTP and inbound mail server hostnames/addresses used for delivery and receipt.
• RETURN_ADDRESS — The "from" address applied to outbound fulfillment email.
• PHYSICAL_NAME and OUTPUT_DESC — Descriptive name and human-readable description of the output.
• DEFAULT_FLAG — Indicates whether this email configuration is the default for its context.
• PORT — Network port used by the associated mail server.
• F_DELETEDFLAG — Logical deletion indicator used by the fulfillment framework.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for multi-org/security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent update control.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The surrogate/composite primary key is JTF_FM_EMAIL_PK, defined over (OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, SERVER_ID) columns. No separate unique business-key index is documented beyond this composite PK. These four columns together form the effective business identifier, since they uniquely tie an email server configuration to a specific output and dispatcher combination.

Common Use Cases and Queries

Typical usage includes reviewing or troubleshooting fulfillment email routing, verifying the default server for a given dispatcher, and joining to group mappings. Common query patterns:

• List all active (non-deleted) email configurations: SELECT OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, OUTGOING_SERVER, RETURN_ADDRESS FROM JTF_FM_EMAIL WHERE F_DELETEDFLAG = 'N';
• Find the default server per dispatcher: SELECT DISPATCHER_ID, OUTGOING_SERVER, INCOMING_SERVER, PORT FROM JTF_FM_EMAIL WHERE DEFAULT_FLAG = 'Y';
• Join to the parent dispatcher for context: SELECT e.OUTPUT_ID, d.DISPATCHER_NAME, e.OUTGOING_SERVER FROM JTF_FM_EMAIL e, JTF_FM_DISPATCHERS d WHERE e.DISPATCHER_ID = d.DISPATCHER_ID;
• Resolve group-to-output mappings referencing this table via JTF_FM_EMAIL_JTF_FM_GROUPS on OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, and SERVER_ID.

Reporting use cases include auditing email server configuration across security groups and confirming which return address is applied to outbound fulfillment notifications.

Related Objects

• JTF_FM_DISPATCHERS — Parent table; joined via DISPATCHER_ID.
• FND_SECURITY_GROUPS — Joined via SECURITY_GROUP_ID for security partitioning.
• JTF_FM_EMAIL_JTF_FM_GROUPS — Mapping table referencing JTF_FM_EMAIL via OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, and SERVER_ID.
• JTF_FM_GROUPS — Fulfillment group definitions indirectly linked through the email-group mapping.