Search Results pa_event_pub




Overview
Explore in AI Chat

Overview

PA_EVENT_PUB is the public PL/SQL API package for Oracle Projects event processing within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Events in Oracle Projects represent billable or revenue-generating transactions that are not derived from expenditure or labor — for example, milestones, progress payments, or manual billing events raised against a project or a task. The package body APPS.PA_EVENT_PUB exposes a documented, supported interface for creating, maintaining, and querying these event records without requiring callers to manipulate the underlying tables directly.

The package follows the standard Oracle Applications three-layer API architecture. PA_EVENT_PUB acts as the public wrapper, delegating validation and business logic to the private package PA_EVENT_PVT and the utility routines in PA_EVENT_UTILS. Error reporting and message handling are routed through FND_MSG_PUB, FND_MESSAGE, and FND_API, providing consistent concurrency handling and error-stack behaviour across the EBS technology stack. The object is classified as a PUB API in the ETRM repository and holds a VALID status in the APPS schema.

Key Procedures and Functions

The ETRM documentation records ten procedures and functions in the package specification:

  • CREATE_EVENT — Creates a new project event record, applying the standard validation and defaulting rules defined by the event business logic.
  • UPDATE_EVENT — Modifies an existing event, enforcing the same validation and concurrency controls used during creation.
  • DELETE_EVENT — Removes an event record, subject to the deletion eligibility rules enforced by the package.
  • INIT_EVENT — Initialises the event record structure in preparation for a create or update call, populating defaults on the in-memory record.
  • LOAD_EVENT — Retrieves an existing event from the database into the API record structure for subsequent processing or update.
  • EXECUTE_CREATE_EVENT — Performs the actual insertion and downstream processing associated with a new event after initialisation.
  • EXECUTE_UPDATE_EVENT — Performs the actual update and associated processing for an existing event.
  • FETCH_EVENT — Reads event data for query and display purposes, returning attribute values to the caller.
  • CLEAR_EVENT — Resets the API record structure, releasing the working record between calls.
  • CHECK_DELETE_EVENT_OK — Validates whether an event may be deleted, returning the outcome so callers can prevent invalid removals.

The INIT/LOAD/EXECUTE pattern is characteristic of Oracle Projects public APIs, allowing callers to stage an event, let the API apply defaults and validation, and then commit the operation through a controlled execution step.

Tables Accessed

The package body references the following tables through APPS synonyms:

  • PA_EVENTS — The primary event table, holding the event header records created, updated, fetched, and deleted by the API.
  • PA_EVENT_TYPES — Stores event type definitions used to validate and classify events during processing.
  • PA_PROJECTS_ALL — Provides project and task context, used for validation of the project organisation and related attributes.
  • PLITBLM — The standard Oracle Applications PL/SQL index-by table used for message and error stack handling.

Additional dependencies include PA_EVENT_PVT, PA_EVENT_UTILS, PA_INTERFACE_UTILS_PUB, PA_MULTI_CURRENCY_BILLING, PA_CONVERSION_TYPES_V, PA_DEBUG, and PA_EVENTS_PKG, which supply validation, currency conversion, debugging, and message-publishing services. The package also depends on FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and FND_PROFILE for the standard EBS API infrastructure.

Usage Notes

PA_EVENT_PUB is typically invoked from Oracle Projects forms, from concurrent programs that import or generate events, and from custom extensions that need to create or maintain project events programmatically. It is the supported entry point for event maintenance and should be used in preference to direct DML against PA_EVENTS. The ETRM repository records that the package is referenced by four other database objects and is not itself referenced by additional dependent objects, confirming its role as a top-level public API.

Callers should expect standard EBS API conventions: a message list and return status from each procedure, profile-driven behaviour via FND_PROFILE, and concurrency checking on updates. Because the package body is documented as VALID in the APPS schema, no recompilation or remediation is required on 12.1.1 or 12.2.2; any custom code should be verified against the documented procedure names before use.