Results for “jtf_fm_file_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view JTF_FM_FILE_V is a reporting and integration object owned by the APPS schema within the JTF – CRM Foundation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented status is VALID, and the ETRM description states that it is a "view referring to the JTF_FM_FILE table." In practical terms, this view exposes the file-registration records maintained by the CRM Foundation file management (FM) subsystem, allowing concurrent programs, forms, and external integrations to read configured output/dispatcher file definitions without touching the base table directly. Because the view is a thin, pass-through projection rather than a join or aggregation, it preserves row-for-row correspondence with the underlying storage while presenting the columns required by the CRM Foundation file-management layer.

Underlying Base Objects

According to the documented ETRM metadata, the sole referenced base object is JTF_FM_FILE, which is accessed through a synonym. The view text confirms this: it performs a straightforward SELECT of fourteen business columns plus the standard WHO audit columns and OBJECT_VERSION_NUMBER from JTF_FM_FILE, with no WHERE clause, no joins, and no functions applied. Consequently, the view does not filter, transform, or denormalize the data in any way; any filtering or ordering must be supplied by the calling query. Because the view references a synonym in the APPS schema, the actual underlying table is resolved at runtime by the synonym definition, which is the standard Oracle EBS pattern for isolating application code from physical table ownership.

Key Columns

The view exposes the following documented columns:

• OUTPUT_ID – Primary identifier for the file/output definition record.
• OUTPUT_TYPE – Classifies the output or file type handled by the definition.
• DEFAULT_FLAG – Indicates whether the record is the default definition for its type.
• DISPATCHER_ID – Identifier of the dispatcher associated with the output.
• SERVER_ID – Identifier of the server on which the file is processed or stored.
• F_DELETEDFLAG – Soft-delete indicator; rows flagged as deleted remain physically present.
• OUTPUT_DESC – Descriptive text for the output definition.
• PHYSICAL_NAME – The physical file name used on the file system.
• DIRECTORY – The directory path associated with the file.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard Oracle WHO audit columns.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework.

Common Use Cases and Queries

Typical usage involves reading active file definitions for a given dispatcher or server, verifying the physical name and directory before an output process runs, or reconciling configured definitions against the file system during support and migration activities. Because the view does not filter deleted records, queries should generally exclude rows where F_DELETEDFLAG is set.

Example — list all active file definitions for a dispatcher:

SELECT output_id, output_type, physical_name, directory, server_id
FROM apps.jtf_fm_file_v
WHERE dispatcher_id = :p_dispatcher_id
AND NVL(f_deletedflag, 'N') = 'N';

Example — retrieve the default definition for a specific output type:

SELECT output_id, output_desc, physical_name, directory
FROM apps.jtf_fm_file_v
WHERE output_type = :p_output_type
AND default_flag = 'Y'
AND NVL(f_deletedflag, 'N') = 'N';

Because the view carries no built-in filtering or joins, it is safe to use in reports, data extracts, and integration queries where a complete, unmodified picture of the CRM Foundation file configuration is required.