Results for “jtf_fm_file_jtf_fm_groups”

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

Overview

JTF_FM_FILE_JTF_FM_GROUPS is a cross-reference (intersection) table owned by the JTF schema within the CRM Foundation product family. Its documented purpose is to store cross-reference information linking batch files to file groups. In the Oracle EBS 12.1.1 and 12.2.2 footprints, this object supports the JTF File Manager subsystem, which manages the lifecycle of files produced by concurrent and batch processes and their association with logical groupings for downstream retrieval, routing, and dispatch.

From a Data Vault modeling perspective, the mined FK structure yields a heuristic classification of link. The table carries no descriptive attributes beyond audit and versioning columns; its functional identity derives entirely from the combination of foreign keys it holds. It therefore behaves as a many-to-many resolution table between JTF_FM_FILE and JTF_FM_GROUPS_ALL, with additional partitioning by dispatcher and server context.

Key Information Stored

The documented physical schema at 12.2.2 contains thirteen columns. The most significant are:

• OUTPUT_ID — Identifies the batch file (output) associated with a group; participates in the foreign key to JTF_FM_FILE.
• OUTPUT_TYPE — Classifies the output record type, qualifying OUTPUT_ID within the file foreign key.
• DISPATCHER_ID — Identifies the dispatcher context under which the file-to-group association was created.
• SERVER_ID — Identifies the application server node owning the batch file.
• GROUP_ID — Identifies the file group; foreign key to JTF_FM_GROUPS_ALL.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM layer.
• F_DELETEDFLAG — Soft-delete indicator.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the association.

The surrogate primary key is documented as JTF_FM_FILE_FG_PK, comprising OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, SERVER_ID, and GROUP_ID. A second documented primary key, JTF_FM_FILE_JTF_FM_GROUPS_PK, carries the identical column set. Because the PK columns are themselves the foreign key columns, no independent business-key candidate exists; uniqueness is defined entirely by the composite relationship tuple.

Common Use Cases and Queries

Typical scenarios include determining which groups contain a given batch file, listing all files assigned to a specific group, and auditing associations by server or dispatcher for capacity and routing analysis.

• Resolve files to groups: SELECT GROUP_ID FROM JTF.JTF_FM_FILE_JTF_FM_GROUPS WHERE OUTPUT_ID = :id AND OUTPUT_TYPE = :type AND SERVER_ID = :srv;
• List files within a group: SELECT f.* FROM JTF_FM_FILE f, JTF_FM_FILE_JTF_FM_GROUPS x WHERE f.OUTPUT_ID = x.OUTPUT_ID AND f.OUTPUT_TYPE = x.OUTPUT_TYPE AND f.DISPATCHER_ID = x.DISPATCHER_ID AND f.SERVER_ID = x.SERVER_ID AND x.GROUP_ID = :gid;
• Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the caller's security context.
• Housekeeping: filter on F_DELETEDFLAG = 'N' for active associations and use LAST_UPDATE_DATE for incremental extracts.

Related Objects

• JTF_FM_FILE — parent table of the batch file; joined on OUTPUT_ID, OUTPUT_TYPE, DISPATCHER_ID, and SERVER_ID.
• JTF_FM_GROUPS_ALL — parent table of file groups; joined on GROUP_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for access control.
• JTF_FM_FILE_JTF_FM_GROUPS_PK / JTF_FM_FILE_FG_PK — documented primary key constraints enforcing uniqueness of the association tuple.
• JTF File Manager concurrent programs and APIs that populate and purge batch file associations at runtime.