Search Results create_events

Overview

PA_XLA_INTF_REV_EVENTS is an Oracle EBS Projects (PA) package owned by the APPS schema that acts as the integration bridge between Project Billing revenue data and the Subledger Accounting (SLA / XLA) engine. Its purpose is to identify project draft revenue distributions eligible for transfer to the Subledger Accounting ledger and to create the corresponding accounting events by invoking the XLA Create_Event API. The package header is defined with AUTHID CURRENT_USER, meaning its database objects are resolved using the privileges of the calling user rather than the package owner.

In the EBS architecture, project revenue generated by the Project Billing module must ultimately be accounted in the general ledger. Rather than posting directly, revenue lines are transformed into subledger accounting events that flow through the Create Accounting process. PA_XLA_INTF_REV_EVENTS performs the event-creation step of that pipeline, ensuring revenue distributions that have passed the eligibility and transfer-status checks become XLA events. The $Header reveals this is a legacy component (version 120.5, last modified 2005), consistent with the transition to the SLA framework introduced in Release 11i/12.

Key Procedures and Functions

• CREATE_EVENTS — A procedure whose documented purpose is to create accounting events for revenues eligible for transfer to SLA by calling the XLA Create_Event API. It accepts an input request ID identifying the concurrent program run and returns an output status indicating the result of the API call. It is the primary entry point of the package and is intended to be executed as part of a bulk revenue-to-SLA transfer process.
• GET_SLA_CCID — A function returning a NUMBER. Based on its parameters, it resolves the Subledger Accounting code combination identifier for a given accounting event, transfer status, source distribution identifiers, distribution type, and ledger. It supports the mapping of project revenue distributions to the correct GL accounting flexfield combination used when constructing the SLA event and its accounting entries.

Tables Accessed

• PA_DRAFT_REVENUES_ALL / PA_DRAFT_REVENUES — Source of project draft revenue distributions, including Event_Id and Transfer_Status_Code, which determine which revenues are eligible for event creation.
• PA_IMPLEMENTATIONS_ALL / PA_IMPLEMENTATIONS — Provides the set of books / ledger context (Set_Of_Books_Id) used in SLA code combination resolution.
• XLA_DISTRIBUTION_LINKS — Supplies source distribution identifiers and distribution type used to link project distributions to SLA events.
• XLA_EVENTS_INT_GT and XLA_EVENTS_S — The XLA event interface table and event entity table populated as events are created and stored.
• XLA_AE_HEADERS and XLA_AE_LINES — Receiving structures for subledger accounting entry headers and lines generated from the events.
• PA_COST_DISTRIBUTION_LINES_ALL — Cost distribution detail referenced during revenue-to-accounting mapping.
• PA_PROJECTS and HR_ORGANIZATION_INFORMATION — Project and organization attributes used for context and validation.
• PLITBLM — A PL/SQL utility table (index-by/log table) used internally for bulk processing.

Usage Notes

PA_XLA_INTF_REV_EVENTS is not typically called directly by end users. It is invoked programmatically by concurrent programs within the Project Billing and Subledger Accounting flow — most notably the process that transfers project revenue to SLA. The p_request_id parameter ties each invocation to a specific concurrent request run, and p_return_status reports success or failure back to the caller.

Because the package is referenced by zero other documented packages, its public API surface is limited and callers depend on it through the concurrent manager rather than through a broad internal call hierarchy. Customizations that need to drive revenue event creation should invoke CREATE_EVENTS within the same concurrent-request context, passing a valid request ID to preserve traceability. Direct invocation outside the supported concurrent flow risks inconsistent XLA event data and is not recommended. The package remains identical in Oracle EBS 12.1.1 and 12.2.2, and the GET_SLA_CCID function can be useful in custom code when the correct SLA code combination must be determined for a given accounting event and ledger.