Search Results complete_actmetric_rec

Overview

OZF_ACTMETRIC_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) Trading Community and channel revenue management schema (OZF/AMS). It is declared with AUTHID CURRENT_USER and provides the internal implementation layer for the Activity Metrics API used by Oracle Trade Management and related marketing and channel programs. Activity metrics represent quantified business measurements associated with a marketing activity, such as forecasted, committed, and actual values tracked against budgets, scenarios, and metric definitions. The package centralizes constant definitions, record and type declarations, and the core CRUD and validation logic required to create, maintain, and validate activity metric records.

As a private (PVT) package, it is not intended to be called directly by external integrators. Instead, it typically sits behind a public API wrapper, and three other packages reference it as part of the internal call chain. The naming and header comments indicate it was migrated from the legacy AMS_ACTMETRICS_ALL structures into the OZF schema, and the record type act_metric_rec_type mirrors that table's column layout, including audit columns, currency and value fields (trans_forecasted_value, trans_committed_value, trans_actual_value), functional currency equivalents, metric UOM, organization context (org_id), and rollup and summarization attributes.

Key Procedures and Functions

The documented packaged API exposes seven members, each responsible for a discrete step in the activity metric lifecycle:

• INIT_ACTMETRIC_REC — Initializes an activity metric record structure, populating default or null values before use by the other routines.
• CREATE_ACTMETRIC — Inserts a new activity metric record into the underlying tables, applying the package's standard business validation.
• UPDATE_ACTMETRIC — Modifies an existing activity metric record, preserving audit columns and revalidating the affected attributes.
• VALIDATE_ACTMETRIC — Performs the primary validation logic for an activity metric record prior to persistence.
• VALIDATE_ACTMETRIC_ITEMS — Validates the individual field-level items comprising an activity metric record. This member is the internal target of searches for "validate_actmetric_items" and is the granular validation routine for the record's constituent columns.
• VALIDATE_ACTMETRIC_RECORD — Validates the record as a whole, coordinating field-level checks and cross-field consistency rules.
• COMPLETE_ACTMETRIC_REC — Finalizes or populates the remaining attributes of an activity metric record, ensuring it is complete before insertion or update.

Tables Accessed

The package references the following tables through APPS synonyms:

• OZF_ACT_METRICS_ALL — The primary activity metrics table; the target of inserts and updates performed by CREATE_ACTMETRIC and UPDATE_ACTMETRIC.
• OZF_ACT_METRICS_ALL_S — The sequence used to generate primary key identifiers for new activity metric rows.
• AMS_METRICS_ALL_B — Provides metric definitions that qualify the measurement being recorded.
• OZF_FUNDS_ALL_B — Supplies fund and budget context associated with metrics linked to marketing funds.
• DUAL — Used for lightweight lookups and date or value evaluation within the PL/SQL logic.

Usage Notes

OZF_ACTMETRIC_PVT is invoked indirectly rather than by end users. It is normally reached through public OZF activity metric APIs and internal callers; the metadata notes that three other packages reference it. Typical triggers include Oracle Trade Management forms that maintain activity metrics and associated concurrent or backend processes that calculate and refresh metric values, such as the calculated, forecasted, committed, and actual value columns. Because the package is declared AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying OZF and AMS synonyms at runtime rather than relying on definer rights. Customizations should call the public wrapper rather than this private package to remain upgrade-safe. The date-specific header comment and API classification confirm this is an internal, non-shipped interface subject to change across releases.