Search Results jtf_fm_processed




Overview
Explore in AI Chat

Overview

The JTF.JTF_FM_PROCESSED table is a CRM Foundation (JTF) object within Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, it stores information for all requests that have been processed, functioning as a persistent record of completed processing activity within the JTF Foundation processing framework. The table is owned by the JTF schema and is marked VALID in the documented instances. It is physically wide, carrying 116 documented columns, the majority of which are generic COL1 through COL100 placeholders used to absorb varying payload shapes across processing request types.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is assessed as standalone, indicating it does not serve as a classic hub, link, or satellite in a normalized integration model. It is better understood as a denormalized audit/outcome store keyed by a composite business key, with a single outbound reference to the partition layer.

Key Information Stored

The primary key is the composite constraint JFUFPD_PK, defined over REQUEST_ID and JOB. Together these two columns form the business key identifying a single processed request instance for a given job. The documented unique index SYS_IL0000243055C00009$$ is a system-managed LOB index and does not itself constitute a business-key candidate.

Common Use Cases and Queries

Typical usage centers on audit and reconciliation of completed processing runs, delivery status reporting, and troubleshooting failed or misrouted communications.

  • Retrieve the outcome of a specific request: SELECT REQUEST_ID, JOB, OUTCOME_CODE, EMAIL_STATUS FROM JTF.JTF_FM_PROCESSED WHERE REQUEST_ID = :request_id;
  • Report processed volume by job over a period using CREATION_DATE.
  • Join to the partition layer for correlation: SELECT p.*, r.* FROM JTF.JTF_FM_PROCESSED p JOIN JTF.JTF_FM_PARTITION_X_REQUEST r ON p.PARTITION_ID = r.PARTITION_ID;
  • Analyze email dispatch quality via EMAIL_STATUS and OUTCOME_CODE groupings.
  • Extract MERGE_XML for document regeneration or content audits, taking care with LOB reads.

Related Objects

The documented relationship data identifies JTF_FM_PARTITION_X_REQUEST as the referenced table, joined on PARTITION_ID. Related objects in the same framework include the partition definitions and request queue infrastructure that feed processed records, the FND concurrent request tables that supply REQUEST_ID context, and the JTF party and contact tables underlying PARTY_ID, PARTY_NAME, and the address columns. Development and reporting should also account for the large object storage implied by MERGE_XML and the standard WHO audit columns when designing extracts.