Search Results clear_event




Overview

PA_EVENT_PUB is the public (PUB-classified) PL/SQL API package in the Oracle EBS Projects (PA) schema responsible for managing project events. In Oracle Projects, an "event" is a business or financial occurrence recorded against a project — for example, a change order, a customer billing event, or a revenue/cost adjustment trigger — that drives downstream processing such as revenue generation, invoicing, or costing. The PA_EVENT_PUB package exposes the supported, externally callable interface for creating, maintaining, and retrieving these event records in the PA_EVENTS table. Its naming convention — the "_PUB" suffix, an API classification confirmed by ETRM documentation — signals that it is a published, supported interface intended for use by other Oracle Applications modules and by customer extension code, rather than an internal helper. The documented procedures and functions and the package's status as VALID in the APPS schema confirm it is an active, supported component in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents ten callable units within PA_EVENT_PUB. They fall into three functional groups:

  • CREATE_EVENT — Creates a new project event record, validating and populating the event header in PA_EVENTS.
  • UPDATE_EVENT — Modifies an existing event record's attributes.
  • DELETE_EVENT — Removes an event record, subject to the package's own validation.
  • CHECK_DELETE_EVENT_OK — A validation function that determines whether a given event may be safely deleted (for example, whether it has already been processed or referenced downstream).
  • INIT_EVENT — Initialises an in-memory event record structure for subsequent processing, part of the standard Oracle API "init / load / execute / clear" calling convention.
  • LOAD_EVENT — Loads existing event data into the in-memory structure for update or enquiry.
  • EXECUTE_CREATE_EVENT — Performs the actual insert of the event record previously prepared via INIT_EVENT/LOAD_EVENT.
  • EXECUTE_UPDATE_EVENT — Performs the actual update of the event record prepared in the same manner.
  • FETCH_EVENT — Retrieves an event record's attributes for display or processing.
  • CLEAR_EVENT — Resets the in-memory structure after processing is complete.

No parameter lists are asserted here; only purposes are stated, consistent with the documented metadata.

Tables Accessed

Per ETRM, PA_EVENT_PUB references the following tables through APPS synonyms:

  • PA_EVENTS — The principal event table, holding event headers and status. Read, written, and validated by CREATE_EVENT, UPDATE_EVENT, DELETE_EVENT, and FETCH_EVENT.
  • PA_EVENT_TYPES — The event type definition table, providing valid event classifications and their attributes.
  • PA_PROJECTS_ALL — The projects master table, used to validate the project context against which an event is recorded.
  • PLITBLM — A standard Oracle Applications PL/SQL table type used as an in-memory PL/SQL index-by table (typically as a persistent global or message buffer), supporting the package's internal data-handling logic.

Usage Notes

PA_EVENT_PUB is invoked whenever an application or extension must create, change, delete, or query a project event record through a supported interface. Typical callers include other PA packages — the metadata confirms PA_EVENT_PUB is referenced by four other packages, including PA_ACTIONS_PUB, PA_EVENT_CORE, PA_EVENT_PVT, and PA_EVENT_UTILS — as well as Oracle Projects forms and concurrent programs that process events for revenue, billing, or costing. Custom code should always call PA_EVENT_PUB rather than manipulating PA_EVENTS directly, since the package enforces validation and preserves data integrity. Users searching for "pa_event_pvt" are typically looking at the private helper package PA_EVENT_PVT, which is the internal counterpart to this public package; PA_EVENT_PVT references and is referenced by PA_EVENT_PUB and should not be called directly. All calls should be issued in the APPS schema context, and standard PL/SQL commit handling should be observed as appropriate to the integrating process.