Results for “jtf_fm_file”

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

Overview

JTF_FM_FILE is a table owned by the JTF schema within the CRM Foundation product family of Oracle E-Business Suite. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, it stores information about batch files processed by the CRM Foundation file management subsystem. The table sits at the center of the batch file dispatch model, recording each output file produced by a dispatcher and the server on which it resides. Its role is largely operational: it enables the applications to track the physical location, naming, and dispatch context of generated batch artifacts so that downstream processes and grouping logic can retrieve them reliably.

From a dimensional modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This suggests that JTF_FM_FILE is best modeled as a satellite attached to the dispatcher hub, because it carries descriptive attributes (file names, directories, descriptions) keyed by DISPATCHER_ID and SERVER_ID rather than acting as an independent business hub. Analysts building a Data Vault layer should treat the dispatcher reference as the hub link and the remaining descriptive columns as satellite payload.

Key Information Stored

The table contains sixteen documented columns at the 12.2.2 schema level. The most significant are outlined below.

• OUTPUT_ID – Surrogate identifier for the batch output record; part of the composite primary key.
• OUTPUT_TYPE – Classifies the output (for example the file format or output category); part of the composite primary key.
• DISPATCHER_ID – Foreign key to JTF_FM_DISPATCHERS; identifies the dispatcher process that generated the output.
• SERVER_ID – Foreign key to JTF_FM_DISPATCHERS; identifies the server on which the batch file resides.
• DEFAULT_FLAG – Indicates whether this output serves as the default for its dispatcher/type combination.
• OUTPUT_DESC – Descriptive text for the output file.
• PHYSICAL_NAME – The physical filename used by the operating system.
• DIRECTORY – The directory path in which the batch file is stored.
• F_DELETEDFLAG – Soft-delete indicator maintained by the CRM Foundation framework rather than by physical row removal.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, enforcing multi-org style data security.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard audit columns.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the OAF/BC4J framework.

The surrogate primary key is JTF_FM_FILE_PK, defined over the composite of OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, and SERVER_ID. There is no separate single-column business key documented; the composite PK itself functions as the natural identifier for a batch file record.

Common Use Cases and Queries

Typical scenarios involve troubleshooting batch dispatch failures, auditing where generated files were written, and reporting on dispatcher activity. A common query joins the dispatcher table to resolve dispatcher context:

• Locate files for a dispatcher: SELECT f.OUTPUT_ID, f.PHYSICAL_NAME, f.DIRECTORY FROM JTF_FM_FILE f WHERE f.DISPATCHER_ID = :dispatcher_id AND NVL(f.F_DELETEDFLAG,'N') = 'N';
• Find the default output: SELECT * FROM JTF_FM_FILE WHERE DEFAULT_FLAG = 'Y' AND OUTPUT_TYPE = :type;
• Audit recent activity: SELECT OUTPUT_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM JTF_FM_FILE WHERE LAST_UPDATE_DATE > SYSDATE - 7;
• Security-scoped reporting using SECURITY_GROUP_ID to restrict rows to the current operating unit.

Related Objects

• JTF_FM_DISPATCHERS – Parent table; joined on DISPATCHER_ID and SERVER_ID.
• JTF_FM_FILE_JTF_FM_GROUPS – Intersection table referencing JTF_FM_FILE via OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, and SERVER_ID; links batch files to file groups.
• FND_SECURITY_GROUPS – Referenced through SECURITY_GROUP_ID for data security.
• JTF_FM_GROUPS – Grouping entity reachable through the intersection table.
• FND_SERVER – Related server metadata referenced by SERVER_ID.