Results for “template_catg_id”

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

Overview

PRP_TEMPLATES_B is the base (language-independent) table within the Oracle E-Business Suite Proposals (PRP) module that stores definitional information about proposal templates. In Oracle EBS 12.1.1 and 12.2.2, PRP supports the creation, management, and reuse of proposal content, and templates serve as reusable blueprints that pre-populate a proposal with standard sections, components, language attributes, and structural metadata. PRP_TEMPLATES_B holds the master template record, while translated and descriptive text is maintained separately in the corresponding TL table.

The table resides in the PRP schema and is classified as VALID in the ETRM dictionary. Following Oracle's standard multilingual (MLS) architecture, PRP_TEMPLATES_B stores the template's non-translatable attributes, and PRP_TEMPLATES_TL stores the translatable name and description columns keyed by TEMPLATE_ID and language. This separation permits a single template definition to be presented in multiple installed languages without duplicating the base record.

The ETRM metadata classifies this object heuristically as hub-leaning under a Data Vault model. In practice, this means PRP_TEMPLATES_B behaves as a central business entity (a template hub) whose TEMPLATE_ID is referenced by several dependent satellite or link-style objects such as components, language attributes, and translations. This classification should be treated as a modeling suggestion rather than a mandated Data Vault implementation.

Key Information Stored

The table contains 26 documented columns. The most significant are listed below.

• TEMPLATE_ID — Surrogate primary key defined by the constraint PRP_TEMPLATES_B_PK and unique index PRP_TEMPLATES_B_U1. This is the durable identifier referenced by all child objects.
• TEMPLATE_CODE — Business-key candidate enforced by unique index PRP_TEMPLATES_B_U2. Provides a human-readable, system-unique identifier for the template.
• TEMPLATE_CATG_ID — Foreign key to the template category, used to group and classify templates for selection and filtering.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Object Library (AOL) and OAF/Forms frameworks to detect concurrent updates.
• ADD_FILE_FLAG — Indicator controlling whether files may be attached to proposals generated from the template.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 – ATTRIBUTE15 — The standard Oracle EBS flexfield-enabled descriptive flexfield (DFF) columns, available for customer-specific extensions without schema modification.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and last-update identity and timestamps.

Together, TEMPLATE_ID and TEMPLATE_CODE uniquely identify a template within a deployment; the remaining columns carry classification, extension, and audit context.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing all active templates, resolving a template code to its surrogate identifier, and joining base template data to translated text and component definitions.

• Enumerating templates by code: SELECT template_id, template_code, template_catg_id FROM prp.prp_templates_b;
• Resolving a code to its ID for use in downstream queries: SELECT template_id FROM prp.prp_templates_b WHERE template_code = :p_code;
• Reporting with translated names: join PRP_TEMPLATES_B to PRP_TEMPLATES_TL on TEMPLATE_ID and filter by language.
• Extracting template content: join PRP_TEMPLATES_B to PRP_TEMPLATE_COMPONENTS on TEMPLATE_ID to list the components that make up each template.
• Auditing changes: query LAST_UPDATED_BY, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER to track maintenance activity.
• Reading DFF extensions: select ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for customer-defined template attributes.

Because TEMPLATE_ID is the consistent key across all dependent tables, it is the correct join column for every related-object query.

Related Objects

• PRP_TEMPLATES_TL — Translated template names and descriptions; joined on TEMPLATE_ID.
• PRP_TEMPLATE_COMPONENTS — Component definitions belonging to each template; joined on TEMPLATE_ID.
• PRP_TEMPLATE_LANG_ATTRS — Language-specific attributes for templates; joined on TEMPLATE_ID.
• Template category entity — The parent of the TEMPLATE_CATG_ID foreign key, used to group templates.

These relationships confirm PRP_TEMPLATES_B as the central hub for template configuration in the PRP module, with child objects supplying translation, composition, and language-specific detail.