Search Results jtf_fm_template_all_pk

Overview

JTF_FM_TEMPLATE_ALL is a CRM Foundation table owned by the JTF schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of fulfillment templates used by the CRM Foundation fulfillment management subsystem. Each row represents a template that governs how fulfillment tasks, contents, and related processing are organized and executed within CRM applications such as TeleSales, Sales, and Service. Fulfillment templates act as reusable blueprints that determine which fulfillment contents are generated for a given business object and how those contents are sequenced and managed.

The table carries multi-organization and multi-language characteristics consistent with the "_ALL" naming convention, exposing an ORG_ID column for operating unit scoping and a SECURITY_GROUP_ID column that references FND_SECURITY_GROUPS. A soft-delete indicator, F_DELETEDFLAG, allows logical removal of templates without physical deletion. Based on the documented foreign key structure, the object exhibits hub-leaning characteristics under a heuristic Data Vault classification. In that modeling view, JTF_FM_TEMPLATE_ALL would be treated as a hub containing the durable TEMPLATE_ID business key, with the dependent fulfillment content records modeled as satellites or links rather than as columns on the template itself.

Key Information Stored

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

• TEMPLATE_ID — Surrogate primary key, enforced by the JTF_FM_TEMPLATE_ALL_PK constraint and the JTF_FM_TEMPLATE_ALL_U1 unique index. This value uniquely identifies each fulfillment template.
• TEMPLATE_NAME — Business-friendly name of the template, used for identification and selection in setup and runtime flows.
• TEMPLATE_DESC — Descriptive text explaining the template's purpose or scope.
• OBJECT_TYPE — The CRM entity type to which the template applies (for example, a lead, opportunity, or service request).
• OBJECT_ID — The specific object instance associated with the template, where template scoping is object-specific.
• SOURCE_CODE and SOURCE_CODE_ID — Source classification values indicating the origin of the template definition.
• STATUS — Lifecycle status controlling whether the template is active or inactive for fulfillment processing.
• ORG_ID — Operating unit identifier supporting multi-organization access control.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, governing record-level security visibility.
• F_DELETEDFLAG — Soft-delete flag used to retire templates without removing underlying rows.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns providing audit and user attribution information.

Common Use Cases and Queries

Typical use cases include reviewing which fulfillment templates are active for a given object type, auditing template configuration across operating units, and tracing templates to their associated contents. A representative query lists active templates by object type:

SELECT template_id, template_name, template_desc
FROM jtf.jtf_fm_template_all
WHERE status = 'ACTIVE'
AND object_type = :p_object_type
AND NVL(f_deletedflag, 'N') = 'N';

To identify all contents attached to a template, join to the content table on TEMPLATE_ID:

SELECT t.template_name, c.content_id
FROM jtf.jtf_fm_template_all t,
     jtf.jtf_fm_template_contents c
WHERE t.template_id = c.template_id;

Reporting scenarios commonly include templates by operating unit, templates by security group, and a count of templates per object type. Because the table uses soft deletes, queries should consistently filter on F_DELETEDFLAG to exclude retired templates.

Related Objects

The following objects are most significant to JTF_FM_TEMPLATE_ALL:

• JTF_FM_TEMPLATE_CONTENTS — Child table referencing TEMPLATE_ID; holds the fulfillment content rows that belong to each template.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID to enforce record-level security grouping.
• JTF_FM_TEMPLATE_ALL_PK — Primary key constraint on TEMPLATE_ID, guaranteeing row uniqueness.
• JTF_FM_TEMPLATE_ALL_U1 — Unique index on TEMPLATE_ID supporting the surrogate key lookup.
• JTF_OBJECTS / OBJECT_TYPE-related metadata — Used to interpret the OBJECT_TYPE and OBJECT_ID columns in application context.
• CRM Foundation fulfillment APIs and concurrent programs — Consume template definitions when generating fulfillment content at runtime.

Together these relationships position JTF_FM_TEMPLATE_ALL as the master reference for CRM fulfillment template configuration within Oracle EBS.