Search Results merge_xml




Overview
Explore in AI Chat

Overview

The JTF_FM_PROCESSED_V view is a CRM Foundation (JTF) database object owned by the APPS schema and delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. It is defined as a view over the base table JTF_FM_PROCESSED, which stores the results of processed fulfillment and merge activities executed by the CRM Foundation "FM" (Fulfillment/Merge) framework. Its status is VALID in the ETRM repository.

The view exposes processed-party records together with their delivery details (email, fax, print), the outcome of the processing run, and — most significantly for the term searched — the MERGE_XML payload. This column holds the XML content used to render personalized documents or merge output during bulk correspondence processing. In integration and reporting scenarios, the view allows concurrent programs and external interfaces to read merge results without directly touching the base table.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced object:

  • JTF_FM_PROCESSED (referenced via SYNONYM) — the physical table holding processed fulfillment/merge rows.

The view is a straightforward projection: it selects a subset of columns from JTF_FM_PROCESSED and appends one derived column, PK_ID, computed as REQUEST_ID || JOB. No joins to other tables are present in the documented view text, so the view simply presents a denormalized, read-friendly slice of the base table.

Key Columns

  • REQUEST_ID — The concurrent program request identifier under which the merge/fulfillment run executed.
  • JOB — The job identifier associated with the processing batch.
  • PARTY_ID / PARTY_NAME — The trading party (customer/contact) targeted by the merge.
  • EMAIL_ADDRESS, FAX_ADDRESS, PRINT_ADDRESS — Delivery addresses for each channel supported by the fulfillment framework.
  • OUTCOME_CODE — The result status of the processing attempt for that party.
  • MERGE_XML — The XML payload produced for the merge/document, central to the searched term "merge_xml".
  • EMAIL_STATUS — Status of email delivery specifically.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns tracking record audit lineage.
  • PK_ID — Synthetic primary key formed by concatenating REQUEST_ID and JOB, useful as a unique row identifier in ad-hoc queries.

Common Use Cases and Queries

Typical uses include auditing merge output, troubleshooting failed deliveries, and extracting XML payloads for downstream integrations or archiving. Because MERGE_XML may be large, projections should avoid selecting it in list-style reports.

Sample query — retrieve processed parties for a specific request:


SELECT REQUEST_ID, JOB, PARTY_ID, PARTY_NAME, OUTCOME_CODE, EMAIL_STATUS
FROM   APPS.JTF_FM_PROCESSED_V
WHERE  REQUEST_ID = :p_request_id
ORDER  BY PARTY_NAME;

Sample query — inspect the XML merge payload for a given party:


SELECT PK_ID, PARTY_NAME, MERGE_XML
FROM   APPS.JTF_FM_PROCESSED_V
WHERE  PARTY_ID = :p_party_id
AND    JOB      = :p_job;

Sample query — summarize outcomes by request:


SELECT REQUEST_ID, OUTCOME_CODE, COUNT(*)
FROM   APPS.JTF_FM_PROCESSED_V
GROUP  BY REQUEST_ID, OUTCOME_CODE;

These queries mirror the view's intended role: a transparent, read-only access point into the CRM Foundation merge-processing results store.