Search Results jtf_fm_template_contents




Overview

JTF_FM_TEMPLATE_CONTENTS is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores cross-reference information between fulfillment templates and the content items those templates deliver. It functions as an association table within the fulfillment management subsystem, allowing a single template defined in JTF_FM_TEMPLATE_ALL to be linked to one or more logical content entries that drive document generation, correspondence, or message output.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as a link table. This classification is appropriate because the table resolves a many-to-many style relationship between fulfillment templates and content definitions, carrying descriptive attributes alongside the associative keys. The table is owned by the JTF schema and is marked VALID in the ETRM registry.

Key Information Stored

The composite primary key JTF_FM_TEMPLATE_CONTENTS_PK is defined over (CONTENT_NUMBER, TEMPLATE_ID). Neither column is a system-generated surrogate; both are business-key candidates that together guarantee uniqueness of a template-to-content assignment.

The table contains 15 documented columns in total per the ETRM 12.2.2 physical schema.

Common Use Cases and Queries

Typical usage centers on reporting which content items belong to a given fulfillment template and validating template configuration before deployment. A common pattern joins the contents to the template master:

  • List content for a template: SELECT c.CONTENT_NUMBER, c.CONTENT_NAME, c.OUTPUT_TYPE FROM JTF.JTF_FM_TEMPLATE_CONTENTS c WHERE c.TEMPLATE_ID = :template_id AND NVL(c.F_DELETEDFLAG,'N') = 'N';
  • Content with message definition: join MES_DOC_ID to JTF_FM_QUERY_MES to identify the underlying message or query driving each content item.
  • Security-filtered reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the appropriate operating unit or security group.
  • Migration and configuration audits: compare CONTENT_NUMBER values across environments to detect template drift between instances.

Because the table is a link object, queries almost always drive from JTF_FM_TEMPLATE_ALL and fan out to contents, rather than the reverse.

Related Objects

  • JTF_FM_TEMPLATE_ALL — Parent template master; joined via TEMPLATE_ID.
  • JTF_FM_QUERY_MES — Message/query definition; joined via MES_DOC_ID.
  • FND_SECURITY_GROUPS — Security group definition; joined via SECURITY_GROUP_ID.
  • JTF_FM_TEMPLATE_CONTENTS_PK — Composite primary key constraint over CONTENT_NUMBER and TEMPLATE_ID.

These relationships establish JTF_FM_TEMPLATE_CONTENTS as the associative bridge within the CRM Foundation fulfillment template model.