Search Results account_group_id




Overview
Explore in AI Chat

Overview

FEM_ACCT_GRPS_PKG is the account group maintenance API within the Oracle E-Business Suite applications schema (APPS). Account groups are foundational reference objects in the Enterprise Performance Foundation / Financial Consolidation Hub data model: they define named groupings of natural accounts that drive reporting hierarchies, consolidation mappings, and dimension-based analysis. The package encapsulates the insert, lock, update, delete, translation, and language-expansion operations required to keep the account group definition tables consistent, including the multi-language (translated) layer.

The package follows a strict two-table DDL pattern that is standard throughout Oracle EBS: the base table FEM_ACCT_GRPS_B holds language-independent attributes, while the translation table FEM_ACCT_GRPS_TL holds the user-visible name and description per installed language. The ACCOUNT_GROUP_ID column is the surrogate primary key that joins the two, and it is also the key the user searched for. Callers must obtain or supply this identifier before invoking any of the DML procedures.

Key Procedures and Functions

  • INSERT_ROW — Creates a new account group. It inserts one row into FEM_ACCT_GRPS_B with the primary key, display code, enabled/personal/read-only flags, object version number, and audit columns, then seeds FEM_ACCT_GRPS_TL for every installed language by selecting from FND_LANGUAGES. It returns the ROWID of the newly created base row through an OUT parameter used to position the calling form or API.
  • LOCK_ROW — Acquires a row-level lock on the account group identified by its ID, ensuring that concurrent updates through the same API are serialized and that the in-memory record being edited has not been changed by another session.
  • UPDATE_ROW — Updates the mutable attributes of an existing account group, maintaining the audit columns, the object version number, and the associated translation rows.
  • DELETE_ROW — Removes an account group, cascading the delete across both the base and translation tables so no orphaned translation rows remain.
  • ADD_LANGUAGE — Propagates a newly installed language into FEM_ACCT_GRPS_TL for all existing account groups that do not yet have a row for that language, using the base table's source language values as the seed.
  • TRANSLATE_ROW — Updates the name and description for a specific account group and language combination, supporting the translated display of account groups in different user languages.

Tables Accessed

  • FEM_ACCT_GRPS_B — The base (language-independent) account group table. The package inserts, updates, locks, and deletes rows here; ACCOUNT_GROUP_ID is the joining key.
  • FEM_ACCT_GRPS_TL — The translation table holding ACCOUNT_GROUP_NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG. Seeded on insert, refreshed by ADD_LANGUAGE, and modified by TRANSLATE_ROW.
  • FND_LANGUAGES — The Oracle Application Object Library language registry, read during INSERT_ROW and ADD_LANGUAGE to enumerate installed languages (INSTALLED_FLAG in 'I','B') and to derive each row's language code.

Usage Notes

The package is classified as OTHER in ETRM and is not a public, supported integration API. It is referenced by three other packages within the same product family, indicating that it is invoked indirectly by higher-level setup or maintenance APIs rather than called directly by end users. Typical invocation paths include the Account Groups setup forms in the ETRM Administrator responsibility, which call INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW through the standard Oracle Forms API wrapper pattern, and concurrent language-expansion programs that call ADD_LANGUAGE after a new language is installed.

Custom code should use the corresponding _PUB or wrapper package where one exists, and must supply a valid ACCOUNT_GROUP_ID obtained from a sequence or the parent API. Because audit columns and the object version number are managed internally, callers must pass consistent X_CREATION_DATE, X_CREATED_BY, X_LAST_UPDATE_DATE, X_LAST_UPDATED_BY, and X_LAST_UPDATE_LOGIN values. The package behaves identically on EBS 12.1.1 and 12.2.2, as the underlying table structures were unchanged across those releases.