Results for “jtf_fm_template_contents_v2”

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

Overview

JTF_FM_TEMPLATE_CONTENTS_V2 is a seeded Oracle E-Business Suite database view owned by the APPS schema and validated in releases 12.1.1 and 12.2.2. It belongs to the JTF product family, commonly identified as CRM Foundation, and serves as a thin presentation layer over the JTF_FM_TEMPLATE_CONTENTS base table. The view exposes template content definitions used by the CRM Foundation document and template generation framework, where "content" refers to the individual output artefacts—letters, documents, messages, and media-enabled deliverables—associated with a template.

Its primary role is to provide a stable, upgrade-safe access point for reports, concurrent programs, personalizations, and integration interfaces that need to read template content metadata without binding directly to the underlying table. Because the view is a simple projection with no joins, filters, or complex predicates, it returns one row for every row in the base table and therefore behaves predictably in reporting contexts. The "_V2" suffix indicates a versioned public interface, allowing Oracle to preserve backwards compatibility while the base table structure evolves.

Underlying Base Objects

The view is defined over a single object: the synonym JTF_FM_TEMPLATE_CONTENTS, which resolves to the APPS-owned table of the same name. The view text is a direct SELECT of every column in the base table with no transformation, aggregation, or WHERE clause:

• DEFAULT_OUTPUT_ID, CONTENT_NUMBER, OUTPUT_TYPE
• MES_DOC_ID, TEMPLATE_ID
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN
• F_DELETEDFLAG, CONTENT_NAME, CONTENT_DESC, OBJECT_VERSION_NUMBER

Because no filtering is applied, deleted or logically removed rows remain visible unless the caller explicitly filters on F_DELETEDFLAG. The referential relationship to the parent template is carried through TEMPLATE_ID, which is expected to match a template identifier in the corresponding template header structures. Callers should treat the view as read-only; DML against it is not supported.

Key Columns

The column of greatest interest to users searching for "content_desc" is CONTENT_DESC, a descriptive text attribute that stores the human-readable description of the template content entry. It complements CONTENT_NAME, which holds the short identifier or title of the content.

• CONTENT_DESC – Free-text description of the template content, used for reporting, selection lists, and user-facing display.
• CONTENT_NAME – Name or short label of the content item.
• CONTENT_NUMBER – Business-facing sequence or reference number for the content.
• TEMPLATE_ID – Foreign reference to the parent template that owns this content row.
• DEFAULT_OUTPUT_ID – Identifier of the default output generated from this content.
• OUTPUT_TYPE – Classifies the output format or delivery mechanism.
• MES_DOC_ID – Reference to the associated media-enabled or document record.
• F_DELETEDFLAG – Logical deletion indicator; "Y" denotes a removed row.
• OBJECT_VERSION_NUMBER – Optimistic locking token used by the framework during concurrent updates.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard WHO information.

Common Use Cases and Queries

Typical usage includes inventorying content descriptions for a template, auditing template configuration, and populating custom reports or LOVs. The following query lists active content descriptions for a given template:

• SELECT content_number, content_name, content_desc FROM apps.jtf_fm_template_contents_v2 WHERE template_id = :p_template_id AND NVL(f_deletedflag,'N') = 'N';
• SELECT template_id, content_name, content_desc FROM apps.jtf_fm_template_contents_v2 WHERE content_desc LIKE '%invoice%';
• SELECT c.content_name, c.content_desc, c.output_type FROM apps.jtf_fm_template_contents_v2 c WHERE c.last_update_date >= TRUNC(SYSDATE)-30 ORDER BY c.last_update_date DESC;

These patterns support impact analysis before template changes, reconciliation of content definitions across environments, and extraction of descriptive metadata for downstream document generation. Always filter on F_DELETEDFLAG where logically removed content must be excluded.