Search Results p_num_of_workers

Overview

XLA_GL_LEDGERS_PVT is a private (PVT) PL/SQL package in the Application Object Library (APPS) schema that belongs to the Subledger Accounting (XLA) product family. Its stated purpose, taken directly from the package header, is to contain "all the logic required to maintain ledger level options." In the Oracle E-Business Suite architecture, XLA sits between the subledgers (Payables, Receivables, Assets, and others) and the General Ledger, and it requires per-ledger configuration to govern how accounting entries are generated, transferred, and reported for each ledger. This package provides the low-level data-access layer for one specific slice of that configuration — the trial balance ledger options stored in the XLA_GL_LEDGERS table.

The package is classified as PVT, meaning it is not a public, supported API. It is intended for internal invocation by XLA product code and by generated or higher-level APIs rather than by external integration developers. The package body carries a header revision of xlathtbled.pkb 120.0, dated 07-Oct-2005, with authorship attributed to M.Asada and a creation entry in the history block. This revision lineage is consistent with the XLA architecture delivered in the 11.5.10 and 12.x code lines, including EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package exposes three public procedures, forming a standard insert/update/delete triad over the ledger options record:

• INSERT_ROW — Creates a new trial balance ledger options row in XLA_GL_LEDGERS for a given ledger. The procedure accepts the ledger identifier along with the work unit and worker count configuration values, plus standard WHO audit columns (creation date, created by, last update date, last updated by, and last update login). It returns the ROWID of the newly inserted row to the caller through an IN OUT NOCOPY parameter. Notably, the procedure raises NO_DATA_FOUND when the ledger identifier is null, and it explicitly sets OBJECT_VERSION_NUMBER to 1, ignoring any value passed in for that parameter.
• UPDATE_ROW — Modifies the existing ledger-level option record for a ledger, supporting maintenance of the work unit and worker count values and refreshing the WHO audit columns to reflect the change.
• DELETE_ROW — Removes the ledger options row, logically reversing or tearing down the configuration that INSERT_ROW established.

The parameter p_num_of_workers, which appears in the user's search, is a configuration input to INSERT_ROW and UPDATE_ROW. It corresponds to the NUM_OF_WORKERS column of XLA_GL_LEDGERS and expresses how many parallel workers should process the ledger's subledger accounting data. It is paired with WORK_UNIT, which identifies the specific work unit assignment for that ledger.

Tables Accessed

The package operates against a single documented table, XLA_GL_LEDGERS, referenced through its APPS synonym. All three procedures read or write this table: INSERT_ROW performs a direct INSERT and uses RETURNING ROWID to hand the row identifier back to the caller; UPDATE_ROW modifies the ledger's option values in place; DELETE_ROW removes the row entirely. Because the table holds one row per ledger, the package effectively acts as the persistence layer for per-ledger trial balance and worker-parallelism settings used by the XLA engine.

Usage Notes

XLA_GL_LEDGERS_PVT is invoked internally by XLA components rather than by end users directly. Typical call paths include the XLA ledger setup and maintenance flows, where a ledger's accounting options are created or changed, and concurrent program logic that needs to persist or refresh worker and work unit assignments before launching parallel subledger accounting processing. The ETRM metadata records that the package is referenced by zero other packages, indicating it is a leaf-level utility in the dependency graph rather than a shared service. The presence of the object version number and WHO audit columns confirms the table follows standard Oracle EBS concurrency and auditing conventions. Because the package is classified PVT, customizations should call supported public XLA APIs instead; direct invocation carries upgrade risk, as the private interface may change without notice between 12.1.1 and 12.2.2.