Search Results jtf_fm_template_all

Overview

The view APPS.IES_SVY_JTF_FM_TEMPLATE_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite. It belongs to the IES product family, which corresponds to the Scripting module (Oracle Scripting / iScript). The view exposes template definition data used by the Scripting survey and feedback framework. Its defining characteristic is that it is a thin, pass-through view: it selects a fixed set of columns directly from the underlying table JTF_FM_TEMPLATE_ALL without joins, aggregations, or filter predicates. This design makes it a convenient, stable interface for consumers that require template header information — template identity, descriptive attributes, ownership, and multi-org context — without querying the transactional base table directly.

In Oracle EBS environments, such views are commonly used by forms, concurrent programs, OAF pages, and integration extracts to provide a read-consistent, pre-validated projection over a core table. Because the view carries the ORG_ID column, it participates in the multi-org (Operating Unit) security model characteristic of EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The ETRM metadata documents a single referenced base object:

• JTF_FM_TEMPLATE_ALL (SYNONYM)

The view definition confirms this dependency: the SELECT list reads exclusively from JTF_FM_TEMPLATE_ALL, and the synonym resolves, in the APPS schema, to the physical table owned by the underlying CRM/Foundation schema. No other tables, views, or joins are involved. Consequently, the view inherits the row population, partitioning, and column semantics of the base table verbatim. The _ALL suffix in the base object name conventionally signals that the table stores data across all operating units, with ORG_ID distinguishing each row's owning organization. The view does not restrict or transform this data, so it presents exactly the rows present in the base table, subject only to any security policies (such as VPD/RLS) that may be attached to the base table.

Key Columns

The view exposes sixteen columns, mirroring the base table projection:

• TEMPLATE_ID — Primary identifier for the template header row.
• TEMPLATE_NAME and TEMPLATE_DESC — The template's display name and descriptive text.
• STATUS — Lifecycle/activation state of the template (for example, active or inactive).
• OBJECT_TYPE and OBJECT_ID — Polymorphic reference describing the business object the template is associated with.
• SOURCE_CODE_ID and SOURCE_CODE — The source identifier and code that classify the template's origin or category.
• ORG_ID — Operating Unit identifier supporting multi-org data segregation.
• F_DELETEDFLAG — Deletion indicator; a set value typically marks logically deleted records.
• OBJECT_VERSION_NUMBER — Optimistic locking version, used to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS Who columns for audit and accountability.

Common Use Cases and Queries

Typical scenarios include reporting on available templates, validating template configuration before a survey deployment, and extracting template metadata for integration or migration. Because the view is a straight projection, queries should explicitly filter on F_DELETEDFLAG and optionally on STATUS and ORG_ID.

Retrieve all active, non-deleted templates for the current operating unit:

• SELECT template_id, template_name, template_desc, status
• FROM apps.ies_svy_jtf_fm_template_v
• WHERE f_deletedflag = 'N'
• AND status = 'ACTIVE'
• AND org_id = :p_org_id;

Locate a template by source classification or associated object:

• SELECT template_id, template_name, object_type, object_id
• FROM apps.ies_svy_jtf_fm_template_v
• WHERE source_code = :p_source_code
• AND object_id = :p_object_id;

Audit recent changes to template definitions using the Who columns:

• SELECT template_id, template_name, last_updated_by, last_update_date
• FROM apps.ies_svy_jtf_fm_template_v
• WHERE last_update_date >= :p_since_date
• ORDER BY last_update_date DESC;

In all cases, callers should select from APPS.IES_SVY_JTF_FM_TEMPLATE_V (or reference the synonym) rather than the base table, preserving the documented interface contract. Developers seeking the underlying storage should be aware that the view and JTF_FM_TEMPLATE_ALL are always synchronized, as the view definition contains no independent logic.