Search Results is_event_billed

Overview

PA_EVENTS_PKG is the core PL/SQL package within the Oracle EBS Projects (PA) application responsible for managing the lifecycle of project billing events stored in the PA_EVENTS table. A billing event represents a milestone, work completion, or other billable occurrence against a project or task that ultimately drives invoice generation through Oracle Receivables. The package is declared with AUTHID CURRENT_USER and resides in the APPS schema, exposing both a set of standard DML operations and query-style validation functions that other modules call to determine the state of a given event. Its header, dated 2007, reflects the multi-currency billing (MCB2) enhancements that introduced the large block of transactional, project, and project functional currency columns visible in the INSERT_ROW signature. In EBS 12.1.1 and 12.2.2, PA_EVENTS_PKG acts as the principal API layer through which forms, concurrent programs, and dependent packages create, modify, and interrogate project billing events.

Key Procedures and Functions

• INSERT_ROW — Creates a new billing event record. It accepts the full set of event attributes, including event type, bill amount, revenue amount, distribution flags, billing assignment, project and organization identifiers, and the extended multi-currency amount and exchange rate columns.
• LOCK_ROW — Obtains a row-level lock on an existing event, typically used to serialize concurrent updates before an UPDATE_ROW call.
• UPDATE_ROW — Modifies an existing event record, allowing changes to bill amounts, revenue amounts, hold flags, completion dates, rejection codes, and descriptive flexfield attributes.
• DELETE_ROW — Removes an event record from the underlying tables.
• IS_EVENT_PROCESSED — A validation function that reports whether an event has already been processed (for example, picked up by revenue distribution or invoicing logic), allowing callers to guard against reprocessing.
• IS_EVENT_BILLED — A validation function that determines whether a given event has already been billed. This is the function most relevant to the search term “is_event_billed,” and it is used to prevent double billing or to gate logic that should only execute on unbilled events.

Tables Accessed

• PA_EVENTS / PA_EVENTS_S — The primary event entity and its translation table, holding the event header attributes that INSERT_ROW, UPDATE_ROW, and DELETE_ROW manipulate.
• PA_EVENT_TYPES — Defines the valid event type classifications referenced by event records.
• PA_CUST_EVENT_REV_DIST_LINES — Contains customer event revenue distribution lines; the package consults these to determine revenue distribution state and whether an event has been processed.
• PA_DRAFT_INVOICE_ITEMS — Stores draft invoice item lines; the presence of a related draft invoice item is central to determining whether an event has been billed, supporting IS_EVENT_BILLED.

Usage Notes

PA_EVENTS_PKG is invoked primarily from the Projects Billing forms when users enter or adjust billable events, and from concurrent programs that process revenue distribution, generate draft invoices, and interface events to Oracle Receivables. Because its DML procedures are documented APIs rather than private routines, custom extensions and integration code commonly call INSERT_ROW and UPDATE_ROW to load events programmatically, using LOCK_ROW first to ensure data integrity. The validation functions IS_EVENT_PROCESSED and IS_EVENT_BILLED are typically called in conditional logic to ensure an event is not billed or processed twice; IS_EVENT_BILLED is especially useful when custom code must branch on prior billing status. With six dependent packages referencing it, PA_EVENTS_PKG sits at the center of event-driven billing flows, and any upgrade or customization affecting its behavior should account for those downstream consumers.