Results for “activity_objective_id”

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

Overview

AMS_ACT_OBJ_METRICS is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between the objectives defined for a marketing activity and the metrics used to measure those objectives. In operational terms, it answers the question "which measures are being applied to which activity objective?" — for example, linking an objective such as "increase qualified leads" to a metric such as "number of leads generated." The table is owned by the AMS schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is a link table. Its role is to resolve a many-to-many relationship between activity objectives and activity metrics, and the presence of descriptive and audit columns suggests it also carries satellite-like attributes (for example, a target value and standard WHO columns). This classification is a modeling suggestion only; the table is a conventional relational entity in the EBS schema.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• ACTIVITY_OBJECTIVE_METRIC_ID — the surrogate primary key of the row, enforced by AMS_ACT_OBJ_METRICS_PK and backed by the unique index AMS_ACT_OBJ_METRICS_U1. This is the internal identifier used by dependent objects.
• ACTIVITY_METRIC_ID — foreign key to AMS_ACT_METRICS_ALL, identifying the metric applied to the objective.
• ACTIVITY_OBJECTIVE_ID — foreign key to AMS_ACT_OBJECTIVES, identifying the activity objective being measured.
• TARGET_VALUE — the threshold or goal value that the metric is expected to reach for the objective. This is the principal business attribute of the link and would typically be modeled as a link satellite attribute.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-org / security-group based data isolation and access control.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle ADF/BC4J framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns recording creation and modification audit information.

The composite unique index AMS_ACT_OBJ_METRICS_U2 on (ACTIVITY_METRIC_ID, ACTIVITY_OBJECTIVE_ID) is the business-key candidate: it prevents the same metric from being attached to the same objective more than once.

Common Use Cases and Queries

Typical scenarios include reporting all metrics and target values defined for a given activity objective, or listing every objective measured by a particular metric.

• Metrics for one objective:

  SELECT m.ACTIVITY_METRIC_ID, m.TARGET_VALUE
  FROM   AMS.AMS_ACT_OBJ_METRICS m
  WHERE  m.ACTIVITY_OBJECTIVE_ID = :objective_id;

• Objectives using a given metric:

  SELECT o.ACTIVITY_OBJECTIVE_ID
  FROM   AMS.AMS_ACT_OBJ_METRICS m, AMS.AMS_ACT_OBJECTIVES o
  WHERE  m.ACTIVITY_OBJECTIVE_ID = o.ACTIVITY_OBJECTIVE_ID
  AND    m.ACTIVITY_METRIC_ID = :metric_id;

• Security-filtered extract joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID for a given access group.
• Data-migration or reconciliation queries to confirm u2 uniqueness before bulk load.

Related Objects

• AMS_ACT_OBJECTIVES — referenced via AMS_ACT_OBJ_METRICS.ACTIVITY_OBJECTIVE_ID; parent of the objective side of the relationship.
• AMS_ACT_METRICS_ALL — referenced via AMS_ACT_OBJ_METRICS.ACTIVITY_METRIC_ID; the metric definition master.
• FND_SECURITY_GROUPS — referenced via AMS_ACT_OBJ_METRICS.SECURITY_GROUP_ID; governs record-level access.
• AMS_ACT_OBJ_METRICS_PK / U1 / U2 — primary key and unique index objects enforcing row identity and business-key uniqueness.
• AM_ACTIVITIES / AMS_ACT_METRICS marts — reporting joins typically traverse from this link outward to activity and metric dimensions.
• AMS/AM marketing activity setup and web-ADI interfaces that insert, update, or delete target-value rows through the PL/SQL activity APIs.