Search Results msg_pub

Overview

APPS.AMS_ACTMETRIC_PVT is a private PL/SQL package body in the Oracle E-Business Suite (EBS) Marketing (AMS) module, classified as a PVT (private) API. It implements the business logic for activity metrics — the measurable outcomes associated with marketing activities such as campaigns, events, deliverables, and offers. Activity metrics capture quantities, costs, and forecasted versus actual values that marketing users track against an activity, and this package is the engine that creates, validates, persists, and maintains those records.

The package acts as the internal implementation layer behind the public activity-metric API surface. It provides record initialization, validation, insertion, update, deletion, locking, currency conversion, cost posting, and rollup maintenance routines. Because it is an internal package, it is not intended to be called directly by external integrations; instead it is invoked by the higher-level AMS public APIs and concurrent processes that manage the activity metric lifecycle. The package body is documented as VALID and references 9+ sibling AMS packages, confirming its role as a hub for activity-metric processing.

Key Procedures and Functions

The package exposes 32 documented procedures and functions covering the full metric record lifecycle:

• HAVE_PUBLISHED, GET_OBJECT_INFO — Query helper routines that determine whether a related object has been published and retrieve descriptive metadata for an activity metric.
• INIT_ACTMETRIC_REC — Initializes the in-memory activity metric record structure prior to creation or update.
• CREATE_ACTMETRIC, UPDATE_ACTMETRIC, DELETE_ACTMETRIC — Core DML routines for inserting, modifying, and logically removing activity metric rows.
• LOCK_ACTMETRIC — Obtains a row-level lock to enforce concurrency control during modification.
• VALIDATE_ACTMETRIC, VALIDATE_ACTMETRIC_ITEMS, VALIDATE_ACTMETRIC_RECORD — Layered validation routines that check the header record, line items, and overall record integrity before persistence.
• COMPLETE_ACTMETRIC_REC, SETCOMMITTEDVAL — Finalize a record for commit and set committed value attributes.
• DEFAULT_FUNC_CURRENCY, CONVERT_CURRENCY, CONVERT_CURRENCY2, SYNC_ROLLUP_CURRENCY — Currency derivation and conversion utilities that apply functional currency defaults and translate metric amounts.
• CHECK_FORECASTED_COST, POST_COSTS — Evaluate forecasted cost figures and post activity costs to the relevant cost/budget structures.
• MAKE_ACTMETRIC_DIRTY, INVALIDATE_ROLLUP — Flag metrics and their rollups as stale so downstream aggregations are recalculated.

Tables Accessed

• AMS_ACT_METRICS_ALL / _S — Primary storage for activity metric definitions and history; the package performs its core inserts, updates, and deletes here.
• AMS_ACT_METRIC_HST / _S — History tables capturing metric changes for audit and rollup purposes.
• AMS_ACT_LISTS — Activity list membership used to associate metrics with activities.
• AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES_B — Campaign and schedule definitions from which metric context is derived.
• AMS_DELIVERABLES_ALL_B, AMS_EVENT_HEADERS_ALL_B, AMS_EVENT_OFFERS_ALL_B — Deliverable, event, and offer entities that carry activity metrics.
• AMS_METRICS_ALL_B, AMS_METRICS_VL, AMS_METRIC_FORMULAS — Metric definitions and the formulas used to calculate derived values.
• AMS_LOOKUPS — FND lookup validation for coded attributes.
• FND_CURRENCIES, MTL_UNITS_OF_MEASURE — Currency and unit-of-measure reference data for conversions.
• OZF_ACT_BUDGETS — Budget records against which cost posting reconciles activity spend.

Usage Notes

AMS_ACTMETRIC_PVT is invoked indirectly. Marketing forms and the public AMS activity APIs call into this package to persist metric changes, while concurrent programs such as cost rollup, currency synchronization, and budget reconciliation jobs invoke the posting and invalidation routines. It also depends on FND_API, FND_MSG_PUB, FND_MESSAGE, and JTF_PLSQL_API, indicating that it uses the standard EBS error-handling and message stack rather than raising raw Oracle errors. Custom code should target the public AMS APIs rather than this PVT package, since its signature and internal calls are subject to change across 12.1.1 and 12.2.2. Developers extending activity metrics should reuse the validation and currency-conversion routines to preserve rollup integrity.