Search Results g_pkg_name




Overview
Explore in AI Chat

Overview

The APPS.LNS_XLA_EVENTS package body is a Loans (LNS) application component that manages the lifecycle of Subledger Accounting (XLA) events for loan transactions. It serves as the integration bridge between the Oracle Loans business logic and the Oracle Subledger Accounting / E-Business Tax reporting (ETRM) architecture introduced in Oracle E-Business Suite Release 12. In Release 12, the traditional posting and accounting entry creation model was replaced by the Subledger Accounting Engine, under which application modules must register accounting events in the XLA_EVENTS table before the Create Accounting program can process them and generate corresponding journal entries.

This package encapsulates that registration and maintenance logic specifically for the Loans product. It does not perform accounting generation itself; rather, it creates, updates, and deletes event records that instruct the XLA engine on what accounting to create for loan origination, disbursement, funding, and adjustment activities. The presence of the global constant G_PKG_NAME VARCHAR2(30) := 'LNS_XLA_EVENTS' — the term used in the user's search — reflects a standard Oracle EBS instrumentation convention used in FND_LOG.STRING calls, allowing developers and DBAs to isolate log messages emitted by this specific package during debugging.

Key Procedures and Functions

The package exposes three documented public procedures that form its complete API surface:

  • CREATE_EVENT — Writes a new accounting event record into XLA_EVENTS for a given loan transaction. Based on the documented header comments, it accepts identifiers such as a loan ID, disbursement header ID, loan amount adjustment ID, or loan line for additional ERS receivables, together with an event type code, event date (typically the GL date), and event status. Seeded Loans event type codes include APPROVED and IN_FUNDING, while documented event statuses are 'U' (Unprocessed), 'I' (Incomplete), and 'N' (No Action). Subsequent activity by the Create Accounting concurrent program picks up unprocessed events.
  • UPDATE_EVENT — Modifies an existing XLA event record, typically to change the event status or refresh event attributes after the underlying loan transaction has changed. This supports the reversal and re-accounting scenarios common in subledger processing.
  • DELETE_EVENT — Removes an event record from XLA_EVENTS, used when accounting is no longer required for a transaction (for example, a cancelled or reversed loan activity).

An internal (non-public) logMessage routine invokes FND_LOG.STRING and, where a concurrent request ID exists, writes to the concurrent program log file via FND_FILE.PUT_LINE.

Tables Accessed

  • XLA_EVENTS — The primary target table. Events are inserted, updated, and deleted here for downstream accounting creation.
  • XLA_TRANSACTION_ENTITIES — Holds the transaction entity header record that ties the event to its source document and application.
  • XLA_ENTITY_TYPES_B — Supplies the seeded entity type definitions (base table) required to validate the loan entity being accounted.
  • LNS_LOAN_HEADERS / LNS_LOAN_HEADERS_ALL — Provide the loan header context, including organization (operating unit) information, for the event.
  • LNS_SYSTEM_OPTIONS — Provides Loans system setup values that influence processing behavior.
  • GL_LEDGERS — Used to resolve ledger information associated with the event's accounting context.

Usage Notes

LNS_XLA_EVENTS is invoked programmatically rather than from a user-facing form. It is referenced by one other package, which is the typical pattern in Loans: higher-level business flows (loan approval, disbursement, and funding) call these procedures to register or maintain XLA events. It is also executed in batch contexts, evidenced by the package's handling of FND_GLOBAL.CONC_REQUEST_ID and concurrent program log output. Custom development should not bypass the package to manipulate XLA_EVENTS directly, because correct population of the transaction entity and event type relationships is essential for the Create Accounting process. The current header revision, 120.17 (dated 2010/12/28), reflects the last shipped version and includes MultiDisbursement support added in 2010.