Search Results xla_acctg_methods




Overview
Explore in AI Chat

Overview

The APPS.XLA_ACCTG_METHODS_F_PKG package is the Forms PL/SQL wrapper for the Accounting Methods setup entity within the Oracle E-Business Suite Subledger Accounting (SLA) architecture. As documented in the package header comment, it is a "Forms PL/SQL Wrapper for xla_acctg_methods" and was generated from the Oracle Application Object Library (XLAUTB) forms generation tool. Its primary business function is to provide the server-side data manipulation layer that the Accounting Methods Setup form (XLATHAGM, referenced in the header as xlathagm.pkh) invokes to maintain the definition of accounting methods used by Subledger Accounting.

In EBS Release 12.1.1 and 12.2.2, accounting methods define the rules that determine how subledger transactions are converted into accounting entries. Each method pairs a transaction chart of accounts with an accounting chart of accounts and is identified by an accounting method type code and an accounting method code. This wrapper package encapsulates the insert, update, delete, locking, translation, and loading logic required to maintain these definitions in a controlled, multi-language environment. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer.

Key Procedures and Functions

The package exposes seven documented procedures, all corresponding to standard Oracle Forms-generated wrapper operations:

  • INSERT_ROW — Creates a new accounting method definition record. It populates the base table with the accounting method type code, accounting method code, transaction and accounting chart of accounts identifiers, enabled flag, descriptive attributes, and the standard WHO audit columns, and returns the new row identifier.
  • UPDATE_ROW — Modifies an existing accounting method definition, updating the descriptive and enabled-flag attributes along with the audit columns for the last update.
  • DELETE_ROW — Removes an accounting method definition, identified by its accounting method type code and accounting method code.
  • LOCK_ROW — Acquires a pessimistic lock on the definition record to enforce concurrency control. It validates that the row has not been changed by another user since it was queried, preventing lost updates during form editing.
  • ADD_LANGUAGE — Inserts translated rows for any languages installed in the environment but not yet represented in the translation table, ensuring the definition is available across all active languages.
  • TRANSLATE_ROW — Maintains the translatable descriptive text for an existing accounting method definition for a given language.
  • LOAD_ROW — Loads a complete accounting method definition, typically used during setup migration or seeding scenarios to insert a full record in a single operation.

Tables Accessed

The package operates against three documented tables, accessed through APPS synonyms:

  • XLA_ACCTG_METHODS_B — The base table holding the non-translatable attributes of each accounting method definition, including the method type code, method code, transaction and accounting chart of accounts identifiers, enabled flag, and WHO audit columns. All insert, update, delete, lock, and load operations target this table.
  • XLA_ACCTG_METHODS_TL — The translation table storing language-specific descriptive text (name and description) for each accounting method. The ADD_LANGUAGE and TRANSLATE_ROW procedures write to this table.
  • FND_LANGUAGES — The Oracle Application Object Library table of installed languages. It is referenced by ADD_LANGUAGE to determine which languages require translation rows for the definition.

Usage Notes

This package is a forms-support wrapper and is not part of the public Subledger Accounting application programming interface. It is invoked almost exclusively by the Accounting Methods Setup form (XLATHAGM) during interactive maintenance of accounting method definitions. Direct invocation from custom code is discouraged: the package assumes form-layer context, including row identifier handling and lock semantics, and provides no validation logic beyond persistence.

The documented procedures reflect standard Oracle Forms behavior — insert, update, delete, lock, translate, and load — and the package neither declares nor depends on any other package, as it is referenced by zero other packages in the ETRM inventory. As with all generated forms wrappers, the procedures accept optional parameters (indicated by default values), allowing callers to pass FND_API.G_MISS_* constants for columns that should be left untouched during an update. The package is a generated artifact; it should not be modified manually, because regeneration from the underlying form definition would overwrite any changes.