Results for “metric_id”

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

Overview

AMS_MET_TPL_DETAILS is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the details on the metrics contained inside a metrics grouping. In practical terms, it functions as the child detail table of a metric template header, recording which individual metrics are assigned to a given template grouping. Each row represents one metric-to-grouping association, which allows the same metric to appear across multiple templates and multiple metrics to be aggregated within a single template.

The table resides in the AMS schema and is classified as VALID in the ETRM data dictionary. Under the heuristic Data Vault classification mined from its foreign key structure, the table is best modeled as a link table: it resolves the many-to-many relationship between metric template headers and the metric definitions themselves, carrying only descriptive and control attributes rather than serving as an independent business entity.

Key Information Stored

The table is documented with 12 physical columns. The most significant are summarized below.

• METRIC_TEMPLATE_DETAIL_ID — surrogate primary key, enforced by the constraint AMS_MET_TPL_DETAILS_PK. It is the identifier returned when the index AMS_MET_TPL_DETAILS_PK is probed, and the value most commonly searched as "ams_met_tpl_details_pk".
• METRIC_TPL_HEADER_ID — foreign key to AMS_MET_TPL_HEADERS. Identifies the owning metric template header (grouping). Part of the unique business key AMS_MET_TPL_DETAILS_U2.
• METRIC_ID — foreign key to AMS_METRICS_ALL_B. Identifies the metric definition included in the template. Also part of AMS_MET_TPL_DETAILS_U2.
• ENABLED_FLAG — controls whether the metric assignment is active within the template.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org/security-group data partitioning.
• ZD_EDITION_NAME — editioning column present in 12.2 online patching architecture; it forms part of both unique indexes U1 and U2.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard EBS who-did-what tracking and optimistic locking.

The surrogate key METRIC_TEMPLATE_DETAIL_ID is distinct from the business-key candidates captured in unique indexes: AMS_MET_TPL_DETAILS_U1 (METRIC_TEMPLATE_DETAIL_ID, ZD_EDITION_NAME) and AMS_MET_TPL_DETAILS_U2 (METRIC_TPL_HEADER_ID, METRIC_ID, ZD_EDITION_NAME). U2 enforces that a given header cannot reference the same metric twice.

Common Use Cases and Queries

Typical usage includes resolving which metrics belong to a template, validating template completeness before campaign execution, and reporting on metric re-use across groupings.

• Retrieve all metrics for a template header:

  SELECT d.metric_id, m.metric_name FROM ams.ams_met_tpl_details d, ams.ams_metrics_all_b m WHERE d.metric_id = m.metric_id AND d.metric_tpl_header_id = :header_id;

• Lookup by surrogate primary key:

  SELECT * FROM ams.ams_met_tpl_details WHERE metric_template_detail_id = :detail_id;

• Identify all templates that include a given metric:

  SELECT metric_tpl_header_id FROM ams.ams_met_tpl_details WHERE metric_id = :metric_id;

• Filter inactive assignments using ENABLED_FLAG, and constrain by SECURITY_GROUP_ID for security-group-aware reporting.

Related Objects

• AMS_MET_TPL_HEADERS — joined on AMS_MET_TPL_DETAILS.METRIC_TPL_HEADER_ID = AMS_MET_TPL_HEADERS.METRIC_TPL_HEADER_ID. Parent template definition.
• AMS_METRICS_ALL_B — joined on AMS_MET_TPL_DETAILS.METRIC_ID = AMS_METRICS_ALL_B.METRIC_ID. Base metric entity.
• AMS_METRICS_ALL_TL — translated metric names, joined through METRIC_ID for multilingual reporting.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security partitioning.
• AMS_MET_TPL_DETAILS_PK and the U1/U2 unique indexes — primary and business-key access paths.