Results for “optimum_wrkr_thrds”

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

Overview

JTF_FM_DISPATCHERS is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores fulfillment dispatchers associated with each server in the Oracle CRM fulfillment manager infrastructure. Fulfillment dispatchers act as background processing agents responsible for routing and delivering outbound messages through specific channels — email, fax, file, and printer — that are registered against a given server instance. The table therefore forms the central definition point that binds a named dispatcher, a processing server, and the worker-thread capacity allocated to that dispatcher.

In Data Vault terms, the FK topology (DISPATCHER_ID, SERVER_ID as the composite primary key, with no dependent child attributes feeding back as business keys in the same shape) suggests a hub-leaning classification. This table behaves as a durable, insert-stable registry of dispatcher identities keyed by (DISPATCHER_ID, SERVER_ID), rather than as a transactional link or a versioned satellite.

Key Information Stored

The table contains 14 documented columns. The most significant include:

• DISPATCHER_ID — the surrogate identifier for the dispatcher; part of the composite primary key JTF_FM_DISPATCHERS_PK (DISPATCHER_ID, SERVER_ID) and the leading column of unique index JTF_FM_DISPATCHERS_U1 (DISPATCHER_ID, ZD_EDITION_NAME).
• SERVER_ID — the server to which the dispatcher belongs; the second PK column and a foreign key to JTF_FM_SERVICE_ALL.
• DISPATCHER_NAME — the human-readable business name of the dispatcher.
• OPTIMUM_WRKR_THRDS — the target/optimum number of worker threads the dispatcher should maintain.
• MAXIMUM_WRKR_THRDS — the ceiling on worker threads the dispatcher may spawn under load.
• F_DELETEDFLAG — a soft-delete indicator; active rows typically carry the non-deleted flag value.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM layer.
• SECURITY_GROUP_ID — the multi-org/security group owning the row; FK to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — editioning column supporting EBR (Edition-Based Redefinition), relevant in 12.2.x.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The composite primary key (DISPATCHER_ID, SERVER_ID) is the true surrogate identifier, while DISPATCHER_ID plus ZD_EDITION_NAME forms the documented business-key candidate via JTF_FM_DISPATCHERS_U1.

Common Use Cases and Queries

Typical use cases include verifying dispatcher capacity settings, auditing which servers carry which dispatchers, and reporting on channel coverage per server. Sample queries:

• List all active dispatchers and their thread limits: SELECT dispatcher_id, server_id, dispatcher_name, optimum_wrkr_thrds, maximum_wrkr_thrds FROM jtf.jtf_fm_dispatchers WHERE f_deletedflag = 'N';
• Join to the parent server: SELECT d.dispatcher_name, s.* FROM jtf.jtf_fm_dispatchers d, jtf.jtf_fm_service_all s WHERE d.server_id = s.server_id;
• Count channel bindings per dispatcher by unioning JTF_FM_EMAIL, JTF_FM_FAX, JTF_FM_FILE, and JTF_FM_PRINTER on DISPATCHER_ID.

Related Objects

• JTF_FM_SERVICE_ALL — parent server table; joined on SERVER_ID.
• JTF_FM_EMAIL — email channel configuration; FK DISPATCHER_ID.
• JTF_FM_FAX — fax channel configuration; FK DISPATCHER_ID.
• JTF_FM_FILE — file channel configuration; FK DISPATCHER_ID.
• JTF_FM_PRINTER — printer channel configuration; FK DISPATCHER_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID.