Results for “maximum_wrkr_thrds”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_FM_DISPATCHERS_V is a read-only database view owned by the APPS schema within the JTF – CRM Foundation product family. In Oracle EBS 12.1.1 and 12.2.2, the CRM Foundation provides the shared infrastructure used by CRM applications such as TeleSales, Service, and Field Service, and the dispatcher construct is a key component of that infrastructure. A dispatcher represents a controlled pool of concurrent worker threads (or "worker threads") that the CRM Foundation framework allocates to process resource-intensive or asynchronous operations. This view surfaces the dispatcher definitions registered in the system, exposing the identity of each dispatcher, its thread capacity thresholds, its server assignment, and standard audit columns.
The view is commonly encountered by technical and functional users searching on dispatcher_name, since that column is the user-facing identifier for a dispatcher. Because the object is a view rather than a base table, it is intended for querying, reporting, and integration lookups; insertions, updates, and deletes must be performed against the underlying base table. The ETRM metadata confirms the object is VALID, meaning its definition compiles cleanly against the referenced base objects at the documented release level.
Underlying Base Objects
JTF_FM_DISPATCHERS_V is defined directly over the base object JTF_FM_DISPATCHERS, which in the APPS schema is typically exposed through a synonym. The view is a straightforward projection of the base table; no joins, aggregations, or filters are applied. Every column in the view maps one-to-one to a column in the base table, and the view text exposes the complete set of attributes present in the underlying record.
Because the definition involves no transformation, the view inherits all data and row-level behavior of the base table. This means that row counts, deletion flags, and versioning semantics observed in the view reflect the base table exactly. The view serves primarily as a convenience or interface layer, allowing CRM Foundation components and external integrations to reference a stable, named object while the physical storage remains in JTF_FM_DISPATCHERS.
Key Columns
- DISPATCHER_ID — Primary identifier for the dispatcher record; used for foreign-key relationships with other CRM Foundation objects.
- DISPATCHER_NAME — The user-facing name of the dispatcher; the field most frequently queried and referenced in integrations and reports.
- OPTIMUM_WRKR_THRDS — The target or optimum number of worker threads the dispatcher should maintain under normal operating conditions.
- MAXIMUM_WRKR_THRDS — The upper bound on worker threads the dispatcher may spawn, providing capacity control.
- SERVER_ID — Identifier of the server or node associated with the dispatcher, relevant in multi-node deployments.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking who created and last modified the record and when.
- F_DELETEDFLAG — Deletion indicator; records flagged as deleted may remain physically present and must be excluded from active-result queries.
- OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent modifications.
Common Use Cases and Queries
Typical uses include looking up a dispatcher by name, reviewing thread thresholds for capacity planning, and auditing dispatcher definitions by creation or modification date. Because the view does not filter deleted rows, queries should generally exclude records where F_DELETEDFLAG indicates deletion.
Retrieve a dispatcher by name:
SELECT dispatcher_id, dispatcher_name, optimum_wrkr_thrds, maximum_wrkr_thrds, server_id FROM apps.jtf_fm_dispatchers_v WHERE dispatcher_name = :p_dispatcher_name AND NVL(f_deletedflag, 'N') = 'N';
List all active dispatchers with their capacity settings:
SELECT dispatcher_name, optimum_wrkr_thrds, maximum_wrkr_thrds FROM apps.jtf_fm_dispatchers_v WHERE NVL(f_deletedflag, 'N') = 'N' ORDER BY dispatcher_name;
Audit recently changed dispatcher definitions:
SELECT dispatcher_name, last_updated_by, last_update_date FROM apps.jtf_fm_dispatchers_v WHERE last_update_date >= SYSDATE - 30 ORDER BY last_update_date DESC;
-
View: JTF_FM_DISPATCHERS_V 12.2.2
View referring to the JTF_FM_DISPATCHERS table
APPS.JTF_FM_DISPATCHERS_V·↳ JTF_FM_DISPATCHERS·Explore JTF module →
-
View: JTF_FM_DISPATCHERS_V 12.1.1
View referring to the JTF_FM_DISPATCHERS table
APPS.JTF_FM_DISPATCHERS_V·↳ JTF_FM_DISPATCHERS·Explore JTF module →
-
This table stores fulfillment dispatchers for each server
-
This table stores fulfillment dispatchers for each server
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel