Search Results ams_eventheader_pvt




Overview
Explore in AI Chat

Overview

AMS_EVENTHEADER_PVT is the private (PVT) application programming interface responsible for managing event headers within the Oracle Marketing (AMS) module of Oracle E-Business Suite. Event headers represent the top-level definition of a marketing event, campaign, or activity, capturing identifying attributes, status, source, budget associations, and multilingual descriptive text. The package encapsulates the business logic required to create, maintain, validate, and delete these header records while preserving data integrity across the underlying event header entities and their language and status dependencies.

As an API-classification PVT package owned by the APPS schema, AMS_EVENTHEADER_PVT is intended to be called by other application components rather than directly by end users. It operates in conjunction with the public wrapper layer and a substantial set of AMS, FND, and JTF dependencies. The metadata confirms the package is VALID, and it is referenced by ten other packages, indicating its central role in the event management call stack.

Key Procedures and Functions

The package exposes ten documented procedures and functions. Their purposes are as follows:

  • CREATE_EVENT_HEADER — Inserts a new event header record, populating the base and translation tables and applying defaulting logic.
  • UPDATE_EVENT_HEADER — Modifies attributes of an existing event header, including language-dependent descriptive columns.
  • DELETE_EVENT_HEADER — Removes an event header and its associated dependent rows, subject to referential checks.
  • LOCK_EVENT_HEADER — Acquires a row-level lock on the header to serialize concurrent modifications.
  • VALIDATE_EVENT_HEADER — Performs business-rule validation on header attributes prior to commit, returning errors via the FND message stack.
  • CHECK_EVH_ITEMS — Verifies the presence and consistency of constituent items associated with the event header.
  • CHECK_EVH_RECORD — Confirms the existence and integrity of the header record being processed.
  • INIT_EVH_REC — Initializes the internal PL/SQL record structure used to stage header data during API processing.
  • COMPLETE_EVH_REC — Populates or finalizes the internal record with derived or defaulted values before persistence.
  • CHECK_EVH_INTER_ENTITY — Validates cross-entity relationships, ensuring the header is consistent with linked marketing entities such as offers and campaigns.

Tables Accessed

The package reads and writes the following documented tables, referenced through APPS synonyms:

  • AMS_EVENT_HEADERS_ALL_B — The base table holding language-independent event header columns; primary target for insert, update, and delete operations.
  • AMS_EVENT_HEADERS_ALL_B_S — The sequence used to generate primary keys for new headers.
  • AMS_EVENT_HEADERS_ALL_TL — The translation table storing language-specific name and description values.
  • AMS_SOURCE_CODES — Lookup source codes used to derive or validate the header source.
  • AMS_USER_STATUSES_B — User-defined status definitions that govern valid header lifecycle states.
  • FND_LANGUAGES — Installed language reference used to validate and default translation rows.
  • OZF_ACT_BUDGETS — Activity budget records associated with event headers during budget-related processing.
  • DUAL — Used for single-row utility selections.

Additional dependencies include AMS_ACCESS_PVT, AMS_ACTMETRIC_PVT, AMS_EVHRULES_PVT, AMS_REFRESHMETRIC_PVT, AMS_SOURCECODE_PVT, AMS_UTILITY_PVT, FND_API, FND_MSG_PUB, FND_PROFILE, and JTF_PLSQL_API, which together supply access control, rules evaluation, messaging, and utility services.

Usage Notes

AMS_EVENTHEADER_PVT is normally invoked indirectly. Oracle Marketing forms, concurrent programs, and higher-level public APIs call into this package to persist event header changes, and the OZF and AMS modules rely on it for budget and metric integration. Because it is a private package, custom code should prefer the corresponding public API or the standard forms. When called directly, callers must first invoke LOCK_EVENT_HEADER, then VALIDATE_EVENT_HEADER, and finally the create, update, or delete routine, inspecting the FND_MSG_PUB message stack for errors. The package is confirmed not to be referenced by any database object, so its invocations originate from application-tier PL/SQL rather than triggers or views.