Results for “ref_template_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CZ_UI_REF_TEMPLATES is a Configurator (CZ) module table in Oracle E-Business Suite, owned by the CZ schema. It stores template-to-template references, capturing the relationships that one user-interface configuration template establishes with another. In the Configurator data model, this table functions as an intersection or association entity that links UI definition templates together, enabling dependent and nested template structures used when configuring complex, customizable products.
Under the heuristic Data Vault classification derived from its foreign key structure, CZ_UI_REF_TEMPLATES is modeled as a link table. This classification is a modeling suggestion rather than a documented Oracle designation; it reflects the table's role as an associative structure connecting template entities by way of foreign keys rather than storing descriptive attributes of a single business entity.
Key Information Stored
The table's primary key, CZ_UI_REF_TEMPLATES_PK, is composite and comprises TEMPLATE_ID, TEMPLATE_UI_DEF_ID, REF_TEMPLATE_ID, REF_TEMPLATE_UI_DEF_ID, and ZD_EDITION_NAME. This composite key makes explicit that a reference is defined by both the owning template and the referenced template, each qualified by its own UI definition identifier, within a specific edition context.
- TEMPLATE_ID and TEMPLATE_UI_DEF_ID — identify the owning template and its UI definition instance.
- REF_TEMPLATE_ID and REF_TEMPLATE_UI_DEF_ID — identify the template and UI definition being referenced.
- DELETED_FLAG — logically marks the reference as removed without physical deletion; it participates in the unique index CZ_UI_REF_TEMPLATES_U1.
- SEEDED_FLAG and REF_TEMPL_SEEDED_FLAG — indicate whether the template and the referenced template originate from Oracle seed data rather than customer-defined configuration.
- REF_COUNT — records an occurrence count associated with the reference.
- ZD_EDITION_NAME — the editioning column supporting Oracle's online patching (edition-based redefinition) model, present in the 12.2.x releases.
- Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) capture row-level change tracking.
The secondary unique index CZ_UI_REF_TEMPLATES_U1 combines DELETED_FLAG, TEMPLATE_UI_DEF_ID, TEMPLATE_ID, REF_TEMPLATE_UI_DEF_ID, REF_TEMPLATE_ID, REF_TEMPL_SEEDED_FLAG, and ZD_EDITION_NAME, providing an alternate business-key candidate that guarantees at most one live reference per template pairing.
Common Use Cases and Queries
Typical usage centers on resolving which templates reference one another at runtime or during setup, and on validating that no dangling or duplicated references exist across editions.
-- All live references with owning and referenced templates
SELECT r.TEMPLATE_ID, r.REF_TEMPLATE_ID, r.REF_COUNT
FROM CZ.CZ_UI_REF_TEMPLATES r
WHERE r.DELETED_FLAG = 'N'
AND r.ZD_EDITION_NAME = 'ORA$BASE';
-- References whose referenced template is Oracle-seeded
SELECT r.TEMPLATE_ID, r.REF_TEMPLATE_ID
FROM CZ.CZ_UI_REF_TEMPLATES r
WHERE r.REF_TEMPL_SEEDED_FLAG = 'Y';
-- Count of references per owning template
SELECT TEMPLATE_ID, COUNT(*) ref_total
FROM CZ.CZ_UI_REF_TEMPLATES
WHERE DELETED_FLAG = 'N'
GROUP BY TEMPLATE_ID;
These patterns support impact analysis before updating a shared template, migration auditing when moving configuration between instances, and diagnostic reporting on template dependency depth.
Related Objects
- CZ_UI_TEMPLATES — referenced twice via
TEMPLATE_IDand viaREF_TEMPLATE_ID; the primary parent of both foreign keys. - CZ_UI_TEMPLATES (REF) — the second FK path, resolving the referenced template's attributes.
- CZ_UI_REF_TEMPLATES_PK — the composite primary key constraint on the four template/UI-definition columns plus edition.
- CZ_UI_REF_TEMPLATES_U1 — the unique business-key index combining the template pair, flags, and edition.
- Configurator UI definition tables related through
TEMPLATE_UI_DEF_IDandREF_TEMPLATE_UI_DEF_ID, which qualify each template within its definition context.
Because the table operates within the CZ Configurator schema, joins to CZ_UI_TEMPLATES and related UI definition objects form the standard access path for both reporting and configuration management.
-
Template-to-Template references
-
Lists copy and reference templates for a template
-
Release 11i: Used by Bill Presentment Architecture
-
View: PQH_REF_TEMPLATES_V 12.1.1
Reference Template View
APPS.PQH_REF_TEMPLATES_V·↳ FND_GLOBAL·↳ HR_API·↳ HR_LOOKUPS·Explore PQH module →
-
Lists copy and reference templates for a template
-
View: PQH_REF_TEMPLATES_V 12.2.2
Reference Template View
APPS.PQH_REF_TEMPLATES_V·↳ HR_API·↳ HR_LOOKUPS·↳ PQH_REF_TEMPLATES·Explore PQH module →
-
Template-to-Template references
-
Release 11i: Used by Bill Presentment Architecture
-
View: AR_BPA_TEMPLATES_VL 12.1.1
APPS.AR_BPA_TEMPLATES_VL·↳ AR_BPA_TEMPLATES_B·↳ AR_BPA_TEMPLATES_TL·Explore AR module →
-
View: AR_BPA_TEMPLATES_VL 12.2.2
APPS.AR_BPA_TEMPLATES_VL·↳ AR_BPA_TEMPLATES_B·↳ AR_BPA_TEMPLATES_TL·Explore AR module →
-
TABLE: HR.PQH_REF_TEMPLATES 12.2.2
-
PACKAGE: APPS.PQH_RFT_SHD 12.2.2
-
TABLE: HR.PQH_REF_TEMPLATES 12.1.1
-
VIEW: HR.PQH_REF_TEMPLATES# 12.2.2
-
VIEW: HR.PQH_REF_TEMPLATES# 12.2.2
-
PACKAGE: APPS.PQH_RFT_SHD 12.1.1
-
VIEW: AR.AR_BPA_TEMPLATES_B# 12.2.2
-
VIEW: AR.AR_BPA_TEMPLATES_B# 12.2.2
-
PACKAGE: APPS.PQH_RFT_DEL 12.2.2
-
PACKAGE: APPS.PQH_RFT_INS 12.1.1
-
PACKAGE: APPS.PQH_RFT_UPD 12.2.2
-
PACKAGE: APPS.PQH_RFT_DEL 12.1.1
-
PACKAGE: APPS.PQH_RFT_UPD 12.1.1
-
TABLE: AR.AR_BPA_TEMPLATES_B 12.1.1
-
TABLE: AR.AR_BPA_TEMPLATES_B 12.2.2