Search Results as_merge_files

Overview

AS_MERGE_FILES is a Sales Foundation (AS) view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that exposes the merge file registry used by the Sales Foundation document merge and word processing infrastructure. It presents the records associated with merge file generation — the physical or logical output files produced when Oracle EBS merges transactional data with word processor templates for activities such as sales letters, quotes, and personalized correspondence. The view is multi-org enabled, meaning its result set is filtered by the operating unit or organization context stored in the Oracle session's CLIENT_INFO value. It is documented in the ETRM as "Merge files (multi-org)" and is not implemented as a standalone database object in the reference environment; it is a compatibility view intended for query and reporting purposes.

From a reporting and integration standpoint, AS_MERGE_FILES provides a stable, security-aware interface over the underlying merge file data. Applications and interfaces should query the view rather than the base table directly, because the view enforces the multi-org access predicate. Users searching for guidance on "how to merge two excels" should note that this object is unrelated to spreadsheet manipulation; it is the EBS mechanism for merging structured application data into word processing documents, not for combining Microsoft Excel workbooks.

Underlying Base Objects

The view is defined over a single base object, AS_MERGE_FILES_ALL, which stores merge file records across all organizations. The ETRM metadata documents no other referenced base objects. The defining query selects from AS_MERGE_FILES_ALL and applies a multi-org filter using the ORG_ID column. The predicate decodes the first ten characters of USERENV('CLIENT_INFO') to determine the current organization; when the session has no valid org context, the value defaults to -99, matching rows with a null or sentinel ORG_ID. This mirrors the standard Oracle multi-org view pattern found in many R12 objects, where the _ALL table holds the full dataset and the operational view restricts visibility to the current operating unit.

Key Columns

• MERGE_FILE_ID — Primary identifier for the merge file record.
• FILE_NAME — Name of the generated merge file.
• BATCH_ID, LIST_ID, WORD_PROCESSOR_ID — Links to the merge batch, distribution list, and word processor template or document definition that drove the merge.
• DATE_TO_SEND, DATE_SENT, NUMBER_SENT — Scheduling and fulfillment attributes tracking when the merged output should be or was sent, and how many copies were dispatched.
• ORG_ID — Operating unit that owns the record; drives the multi-org filtering.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the request that created or updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who/audit columns.

Common Use Cases and Queries

Typical use cases include auditing merge output by operating unit, reconciling send counts against distribution lists, and tracing merge files back to the concurrent request that produced them. The following query lists recent merge files for the current org context:

SELECT merge_file_id, file_name, batch_id, list_id, date_to_send, date_sent, number_sent
FROM as_merge_files
ORDER BY creation_date DESC;

A second query correlates merge files with their originating concurrent request and program:

SELECT m.merge_file_id, m.file_name, m.request_id, m.program_id, m.org_id
FROM as_merge_files m
WHERE m.request_id IS NOT NULL;

Because access is filtered by ORG_ID, cross-organization reporting requires either setting the correct multi-org context or querying AS_MERGE_FILES_ALL directly with appropriate privileges.