Search Results xla_journal_entries_pub_pkg




Overview
Explore in AI Chat

Overview

XLA_JOURNAL_ENTRIES_PUB_PKG is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Subledger Accounting (XLA) product family and is classified as a public API (OTHER classification in ETRM). Its core business purpose is to provide a programmatic, supported interface for creating and completing subledger accounting journal entries — the accounting representations that Subledger Accounting generates before they are transferred to and posted in the General Ledger. The package encapsulates the logic required to build journal entry headers and lines against the XLA accounting model, and to finalize (complete) a journal entry so that it becomes a valid accounting artifact. Because it is a public package rather than an internal worker, it is the sanctioned entry point for external or custom code that needs to emit subledger journal entries without directly manipulating the underlying XLA tables. The package is documented as VALID and carries only a standard dependency on the SYS STANDARD package, indicating it is self-contained with respect to its declared dependencies and does not depend on other APPS packages. It is, however, referenced by itself in the dependency listing, reflecting internal recursive or overloaded references within the package body.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within the package. Parameter lists are not published in the available metadata and are therefore not reproduced here.

  • CREATE_JOURNAL_ENTRY_HEADER — Establishes the journal entry header record for a subledger accounting entry. This routine is responsible for defining the top-level attributes of the journal entry, such as its association to an accounting event and the ledger context under which the entry is being created. It is the first step in the create-and-complete lifecycle exposed by the package.
  • CREATE_JOURNAL_ENTRY_LINE — Adds an individual journal entry line (accounting distribution) to a journal entry previously created via the header routine. Each line carries the accounting flexfield combination and monetary amounts, forming the debit and credit components of the entry.
  • COMPLETE_JOURNAL_ENTRY — Finalizes the journal entry so that it is treated as a completed subledger accounting entry. Completion typically validates the accumulated header and line data and marks the entry ready for downstream processing such as transfer to and posting in General Ledger.

Tables Accessed

The package references the following tables through APPS synonyms:

  • XLA_AE_HEADERS — The primary table for subledger journal entry headers. CREATE_JOURNAL_ENTRY_HEADER writes to this table to persist the header record.
  • XLA_EVENTS — Stores subledger accounting events that originate in the source subledgers. Journal entries are associated with these events, so the package reads event information to link the created entry to its originating event.
  • XLA_SUBLEDGERS — Contains the subledger definitions and application context. It is read to determine the subledger for which the journal entry is being generated.
  • GL_PERIOD_STATUSES — Holds General Ledger period open/close status. It is read to validate or determine the appropriate accounting period and ledger context for the entry.

Usage Notes

XLA_JOURNAL_ENTRIES_PUB_PKG is intended to be called from custom PL/SQL code, concurrent programs, or integration routines that need to create subledger accounting entries programmatically. The documented metadata shows zero other APPS packages referencing this package, which indicates it is not consumed by standard Oracle application packages but is exposed for external or customer use. Typical invocation follows the sequence implied by the procedures: create the header, add one or more lines, then complete the entry. Because the package is documented as a public interface, it is the recommended alternative to inserting directly into XLA_AE_HEADERS and related tables. In both Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and should be invoked with the APPS schema or a synonym in scope. The absence of documented parameters in the ETRM extract means callers should consult the package specification in the database for exact signatures before coding against it.