Search Results sys_il0000243055c00009

Overview

JTF.JTF_FM_PROCESSED is a transactional table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the outcome of every correspondence request processed by the JTF Fulfillment Manager (FM) engine. It records the recipient, channel address (email, fax, or print), outcome code, and the merge XML payload used to render the document, effectively providing an audit trail of outbound customer communications generated by Oracle Marketing, Oracle Trade Management, and related fulfillment flows.

The table resides in the JTF schema, is registered as FND Design Data JTF.JTF_FM_PROCESSED, and is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10. It is classified as VALID. The table is documented with 116 columns, reflecting a wide merged-column design used to store dynamically named merge fields. Using heuristic Data Vault modeling, the table is best characterized as a satellite attached to a party and request hub: it captures descriptive state (outcome, status, address, merge payload) that changes over the lifecycle of a fulfillment request rather than acting as an independent business entity. The Data Vault classification is provided as a modeling suggestion only, since the heuristic classification is "standalone."

Key Information Stored

The documented primary key is JFUFPD_PK, composed of (REQUEST_ID, JOB). These two columns form the composite surrogate identity for each processed fulfillment record. REQUEST_ID is the unique request identifier, and JOB is the job number or batch that carried the request.

The most significant business columns are:

• REQUEST_ID / JOB — Composite primary key identifying the processed request and its batch.
• PARTY_ID — The recipient's party identifier; indexed by JTF_FM_PROCESSED_N1 and also a foreign key to JTF_FM_PARTITION_X_REQUEST (via PARTITION_ID).
• PARTY_NAME — Recipient party name (VARCHAR2 240).
• EMAIL_ADDRESS, FAX_ADDRESS, PRINT_ADDRESS — Channel-specific delivery addresses (VARCHAR2 400 each).
• OUTCOME_CODE — Result of the fulfillment attempt (VARCHAR2 30).
• EMAIL_STATUS — Email delivery status (VARCHAR2 15).
• MERGE_XML — BLOB containing the rendered request as XML (up to 4000 bytes).
• PARTITION_ID — Links the record to the partition-to-request mapping.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit Who columns.
• COL1 through COL100 — Generic VARCHAR2(2000) columns used to capture merge field names dynamically.

Unique indexes documented include SYS_IL0000243055C00009$$ (LOB, referencing MERGE_XML) and JFUFPD_PK. JTF_FM_PROCESSED_U1 on REQUEST_ID and JFUFPD_PK constitute the documented business-key candidates. A foreign key exists from PARTITION_ID to JTF_FM_PARTITION_X_REQUEST.

Common Use Cases and Queries

Typical uses include auditing outbound correspondence, diagnosing failed deliveries, and reporting fulfillment throughput by job or party.

• Locating processed records for a party: SELECT REQUEST_ID, JOB, PARTY_NAME, EMAIL_ADDRESS, OUTCOME_CODE, EMAIL_STATUS FROM JTF.JTF_FM_PROCESSED WHERE PARTY_ID = :party_id;
• Finding failed or exception deliveries: SELECT REQUEST_ID, JOB, OUTCOME_CODE, EMAIL_STATUS FROM JTF.JTF_FM_PROCESSED WHERE OUTCOME_CODE <> 'SUCCESS';
• Batch reporting by job: SELECT JOB, COUNT(*) FROM JTF.JTF_FM_PROCESSED GROUP BY JOB;
• Extracting the merge payload for a request: SELECT MERGE_XML FROM JTF.JTF_FM_PROCESSED WHERE REQUEST_ID = :request_id AND JOB = :job;
• Joining to partition mapping: SELECT a.REQUEST_ID, b.PARTITION_ID FROM JTF.JTF_FM_PROCESSED a, JTF.JTF_FM_PARTITION_X_REQUEST b WHERE a.PARTITION_ID = b.PARTITION_ID;

Because MERGE_XML is a LOB, it should be handled carefully in high-volume reporting queries to avoid unnecessary LOB reads.

Related Objects

The documented dependency data identifies the following associated objects:

• JTF.JTF_FM_PARTITION_X_REQUEST — Parent mapping table; JTF_FM_PROCESSED.PARTITION_ID references it.
• JFUFPD_PK — Primary key index over (REQUEST_ID, JOB).
• JTF_FM_PROCESSED_N1 — Nonunique index on PARTY_ID.
• JTF_FM_PROCESSED_U1 — Nonunique index on REQUEST_ID.
• SYS_IL0000243055C00009$$ — LOB index for the MERGE_XML BLOB column, matching the searched identifier.

The user's search term "sys_il0000243055c00009" corresponds exactly to the system-generated LOB index for the MERGE_XML column in this table, confirming the object is the Fulfillment Manager processed-request store.