Results for “resubmitted_job_count”

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

Overview

The view APPS.JTF_FM_EMAIL_STATS_V is a reporting and integration object within the JTF – CRM Foundation product of Oracle E-Business Suite, valid across releases 12.1.1 and 12.2.2. As documented in the ETRM metadata, its purpose is to "display statics of the email sent for specific requests." In practice, it exposes aggregated email-delivery statistics for individual e-mail campaign or fulfillment requests, allowing administrators, CRM users, and downstream consumers to monitor the outcome of outbound e-mail dispatches without querying the transactional base table directly.

The view is owned by the APPS schema and is classified as a VIEW object with VALID status. It is a thin, read-oriented projection rather than a stored dataset, and therefore inherits its currency from the underlying table at the moment of query execution. This makes it suitable for ad-hoc reporting, Oracle Discoverer-style analytics, custom concurrent programs, and embedded integrations that need per-request e-mail metrics. Because the view is a simple select over a synonym, no materialization or refresh schedule applies; results always reflect the current state of the base data. This behavior should be accounted for in any integration where snapshot consistency is required.

Underlying Base Objects

The documented referenced base object is JTF_FM_EMAIL_STATS, accessed through a synonym. The view definition performs a straightforward projection:

• SELECT ... FROM JTF_FM_EMAIL_STATS STATS

Because the view selects directly from the base object without joins, filters, or aggregation clauses, the relationship is one-to-one at the row level: each row in JTF_FM_EMAIL_STATS_V corresponds to exactly one row in JTF_FM_EMAIL_STATS. Consequently, all columns exposed by the view are pass-through columns from the base table, and no data transformation, decoding, or derived values are applied. Any data quality issue or constraint behavior present in the base table—including who may insert or update it—flows directly into the view's visible content.

Key Columns

The view exposes the following documented columns, all inherited unchanged from JTF_FM_EMAIL_STATS:

• REQUEST_ID — Identifier of the specific request whose e-mail statistics are being tracked; the primary grouping key for reporting.
• TOTAL — Total volume of e-mails associated with the request.
• SENT, MALFORMED, BOUNCED, OPENED, UNSUBSCRIBED, DO_NOT_CONTACT — Delivery and response outcome counters, describing successful sends and various failure or suppression states.
• RESUBMITTED_MALFORMED — Count of malformed records that were resubmitted for processing.
• RESUBMITTED_JOB_COUNT — Number of jobs resubmitted for the request, directly relevant to the search term that led to this view.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording actor and timestamp information.

Common Use Cases and Queries

Typical scenarios include auditing e-mail delivery performance for a campaign, identifying requests with abnormal bounce or malformed counts, and locating requests that required resubmission. A representative query returning per-request metrics is:

• SELECT REQUEST_ID, TOTAL, SENT, BOUNCED, MALFORMED, OPENED, RESUBMITTED_MALFORMED, RESUBMITTED_JOB_COUNT FROM APPS.JTF_FM_EMAIL_STATS_V WHERE REQUEST_ID = :p_request_id;
• SELECT REQUEST_ID, RESUBMITTED_JOB_COUNT FROM APPS.JTF_FM_EMAIL_STATS_V WHERE RESUBMITTED_JOB_COUNT > 0 ORDER BY RESUBMITTED_JOB_COUNT DESC;
• SELECT REQUEST_ID, BOUNCED, MALFORMED, SENT FROM APPS.JTF_FM_EMAIL_STATS_V WHERE BOUNCED > 0 OR MALFORMED > 0;

Standard EBS access rules apply: responsibility-level grants and the APPS schema determine visibility, and queries should be executed with the appropriate MO or APPS context.