Search Results jfuffe_pk

Overview

JTF_FM_CONTENT_FAILURES is a transactional table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores details of failed content requests processed by the CRM Foundation media and content infrastructure, particularly where content addresses, media types, or delivery jobs could not be resolved or served successfully. Each row captures a single failure event tied to a specific request, content number, and job, allowing administrators and developers to diagnose content delivery problems and record corrections.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone, indicating no foreign key relationships to parent or child tables were mined from the physical schema. In Data Vault terms, this suggests the table behaves more like an isolated record of events rather than a true hub, link, or satellite; if modeled formally, it would most closely resemble a satellite-like failure log keyed by its composite identifier, but no conformed hub or link relationships are documented.

Key Information Stored

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

• REQUEST_ID — Identifier of the originating content request; part of the composite primary key JFUFFE_PK.
• CONTENT_NUMBER — The content item number associated with the failed delivery; also part of the primary key.
• JOB — The job or processing unit that failed; the third component of the composite primary key.
• MEDIA_TYPE — The media type of the content being processed at the time of failure.
• ADDRESS — The address originally supplied for content delivery or resolution.
• FAILURE — Description or code of the failure that occurred.
• CORRECTED_ADDRESS — A corrected or normalized address recorded after the failure was diagnosed.
• CORRECTED_FLAG — Indicates whether a correction has been applied to the failed record.
• CREATED_BY, CREATION_DATE — Standard audit columns recording who created the failure row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification.

The surrogate primary key is JFUFFE_PK, defined as the composite of (REQUEST_ID, CONTENT_NUMBER, JOB). No separate unique business-key indexes are documented in the ETRM metadata beyond this primary key, so these three columns together serve as the effective business identifier for each failure record.

Common Use Cases and Queries

Typical use cases include diagnosing content delivery failures, auditing corrections applied to bad addresses, and reporting failure trends by media type or job. Sample query patterns:

• List recent failures: SELECT request_id, content_number, job, failure FROM jtf.jtf_fm_content_failures WHERE creation_date > SYSDATE - 7;
• Find uncorrected failures: SELECT * FROM jtf.jtf_fm_content_failures WHERE corrected_flag = 'N';
• Aggregate failure counts by media type: SELECT media_type, COUNT(*) FROM jtf.jtf_fm_content_failures GROUP BY media_type;
• Audit corrections: SELECT request_id, address, corrected_address FROM jtf.jtf_fm_content_failures WHERE corrected_flag = 'Y';

Reporting use cases include operational dashboards tracking failure rates, data-quality reviews before reprocessing content, and troubleshooting individual request-Job-Content combinations.

Related Objects

The ETRM relationship data classifies this table as standalone, with no foreign keys mined. Consequently, joins must be inferred logically rather than through documented constraints. Likely related objects include:

• JTF_FM_CONTENT_REQUESTS — presumably joined on REQUEST_ID to link failures to originating requests.
• JTF_FM_CONTENT — linked on CONTENT_NUMBER to resolve the content item.
• JTF_FM_MEDIA — referenced via MEDIA_TYPE for media definitions.
• FND_USER — joined on CREATED_BY or LAST_UPDATED_BY for user names.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN for session context.

Administrators should verify actual join columns against the deployed schema, since the metadata documents no confirmed foreign-key dependencies.