Results for “template_type_code”

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

Overview

IGP_WZ_TEMPLATES is a table in the IGS (Student System) schema of Oracle E-Business Suite, documented as valid across releases 12.1.1 and 12.2.2. The ETRM metadata describes it as a table "to store the details of Templates," indicating that it serves as the persistence layer for reusable template definitions used by the IGS WZ (wizard or workflow-related) component of the Student System.

In the context of the search phrase "Data Template Infotech," this object is of interest because templates in IGS frequently carry both structural content and descriptive metadata — the table holds a TEMPLATE_CONTENT column alongside naming, status, type, and expiry attributes, making it a candidate source for organizations that manage document, form, or communication templates within the Student System footprint.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as standalone. In Data Vault terms this suggests it behaves as a standalone hub rather than a link or satellite, since no foreign-key dependencies to other tables were identified in the extracted relationship data. The TEMPLATE_ID column functions as the surrogate primary key and would naturally anchor such a hub.

Key Information Stored

The table exposes 15 documented columns. The most significant are summarized below.

• TEMPLATE_ID — Surrogate primary key, enforced by index IGP_WZ_TEMPLATES_PK. It uniquely identifies each template row and is the column most commonly used in joins and application lookups.
• TEMPLATE_NAME — The business-key candidate, protected by the unique index IGP_WZ_TEMPLATES_U1. Because the unique constraint is on the name rather than the ID, applications typically resolve a template by name before retrieving its surrogate key.
• TEMPLATE_TITLE — Human-readable display title, distinct from the internal name.
• DESCRIPTION — Free-text explanation of the template's purpose.
• TEMPLATE_CONTENT — The substantive payload of the template; this is the largest column and is accompanied by a system-managed LOB index (SYS_IL0000402872C00006$$) documented in the physical schema.
• TEMPLATE_TYPE_CODE — Classifies the template into a category, enabling filtering by template class.
• TEMPLATE_STATUS_CODE — Controls whether the template is active, inactive, or otherwise unavailable for use.
• EXTERNAL_FLAG — Indicates whether the template is intended for external rather than internal consumption.
• EXPIRY_DATE — The date after which the template is no longer valid.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle EBS framework to detect concurrent updates.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard EBS who-did-what auditing.

Common Use Cases and Queries

Typical reporting and integration scenarios revolve around enumerating active templates, extracting content for downstream delivery, and auditing template lifecycle changes.

A standard listing query filters on status and expiry:

• SELECT template_id, template_name, template_title, template_type_code FROM igs.igp_wz_templates WHERE template_status_code = 'ACTIVE' AND (expiry_date IS NULL OR expiry_date > SYSDATE);

To retrieve the content of a specific template identified by its unique business name:

• SELECT template_content FROM igs.igp_wz_templates WHERE template_name = :p_template_name;

Audit and change-tracking extracts commonly select the audit columns and OBJECT_VERSION_NUMBER to reconcile template changes between environments or over time. Because TEMPLATE_CONTENT is LOB-backed, extraction scripts should account for the associated LOB index rather than assuming inline storage.

Related Objects

The extracted metadata records no foreign-key relationships for IGP_WZ_TEMPLATES, reinforcing the standalone classification. Consequently, related-object identification must rely on functional association rather than referential integrity. The most significant associations are:

• IGP_WZ_TEMPLATES_PK — The primary key index on TEMPLATE_ID, the primary access path for application and ad-hoc lookups.
• IGP_WZ_TEMPLATES_U1 — The unique index on TEMPLATE_NAME, enforcing the business key and supporting name-based resolution.
• SYS_IL0000402872C00006$$ — The system-managed LOB index supporting TEMPLATE_CONTENT.
• IGS schema siblings — Other IGP_WZ_* objects in the IGS schema that share the wizard/template functional area and are populated concurrently by the same Student System flows.

Because the relationship data is limited to index-level dependencies, downstream joins should be validated against the actual IGS data model in the deployed instance before being treated as authoritative.