Results for “ams_met_tpl_headers_b”

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

Overview

AMS_MET_TPL_HEADERS_B is the base (language-independent) table that stores Metric Template Headers for default metrics within the Oracle Marketing (AMS) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, it functions as the master definition table for metric templates — reusable configurations that determine which metrics are applied to marketing objects and how those metrics are enabled and associated. Each row represents a single metric template header record, identified by a surrogate key and qualified by a language-independent business definition, while descriptive, translatable text is held in the companion "_TL" table.

From a Data Vault modeling perspective, the mined relationship classification for this table is hub-leaning. This suggests modeling AMS_MET_TPL_HEADERS_B as a hub, anchored on its unique business key, with surrounding attributes and foreign-key references represented as satellites or links for historical tracking. The physical schema is owned by the AMS user and exposes 15 documented columns.

Key Information Stored

The table's core identifier is the surrogate primary key METRIC_TPL_HEADER_ID, enforced by the constraint AMS_MTH_B_PK. A unique index, AMS_MET_TPL_HEADERS_B_U1, spans METRIC_TPL_HEADER_ID and ZD_EDITION_NAME, which acts as the documented business-key candidate and supports editioning/multi-version semantics in 12.2.2.

• METRIC_TPL_HEADER_ID — surrogate primary key uniquely identifying each metric template header.
• ENABLED_FLAG — indicates whether the template header is active and available for use.
• APPLICATION_ID — identifies the owning Oracle application context.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level security and data partitioning.
• USED_BY_ID / USED_BY_CODE — reference the consuming entity, linking to AMS_CUSTOM_SETUPS_B via USED_BY_ID.
• OBJECT_TYPE / ASSOCIATION_TYPE — classify the object and the association behavior associated with the metric template.
• ZD_EDITION_NAME — editioning qualifier supporting the unique key.

Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — provide change tracking and optimistic locking. Descriptive text is not stored here and must be retrieved from the "_TL" table.

Common Use Cases and Queries

The table is typically queried to enumerate available metric templates, verify enablement, and resolve the objects or setups that consume each template. A common pattern joins the base table to its translation table to retrieve user-facing names:

SELECT b.metric_tpl_header_id,
       t.metric_tpl_header_name,
       b.enabled_flag,
       b.application_id
FROM   ams.ams_met_tpl_headers_b b,
       ams.ams_met_tpl_headers_tl t
WHERE  b.metric_tpl_header_id = t.metric_tpl_header_id
AND    t.language = USERENV('LANG')
AND    b.enabled_flag = 'Y';

Reporting scenarios include auditing which templates are active, tracing template usage through AMS_MET_TPL_ASSOCS, and confirming security-group alignment. Analysts resolving the consuming setup can join USED_BY_ID to AMS_CUSTOM_SETUPS_B.

Related Objects

• AMS_MET_TPL_HEADERS_TL — translation table joined on METRIC_TPL_HEADER_ID, supplying language-specific descriptive text.
• AMS_MET_TPL_ASSOCS — child table referencing METRIC_TPL_HEADER_ID, holding metric template associations.
• AMS_CUSTOM_SETUPS_B — referenced via USED_BY_ID, identifying the setup that uses the template.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for row-level security.

These relationships confirm the table's hub role, governing dependent associations, translations, and security scoping within the Marketing data model.