Search Results fem_fin_elems_pkg

Overview

FEM_FIN_ELEMS_PKG is an Oracle Applications (APPS) schema PL/SQL package that provides the low-level data access and language-handling layer for the Financial Element definitions used by Oracle Enterprise Performance Foundation / Enterprise Resource Management (ETRM). Financial Elements represent the account-related dimension members (for example, natural account, cost center, or other segments) that ETRM uses when building Financial Item, dimension, and analytical structures in Oracle E-Business Suite 12.1.1 and 12.2.2.

The package is not a business API in the formal sense. Its ETRM classification is OTHER, meaning it is an internal, generated-style helper package rather than a published interface. It encapsulates the standard "table handler" operations for a translated base/TL table pair: row insert, row lock, row update, row delete, translation insert, and translation maintenance. Application logic and the surrounding ETRM dimension utilities call this package rather than manipulating the underlying tables directly, which centralizes the enforcement of who-columns, language settings, and concurrency checks for Financial Element data.

Key Procedures and Functions

The documented procedures are the six standard operations of the EBS table-handler pattern:

• INSERT_ROW — Creates a new Financial Element record, populating the base table row (and any required TL row) with the attributes and who-column auditing values supplied by the caller.
• LOCK_ROW — Acquires and verifies a lock on an existing Financial Element row to support optimistic concurrency control; it typically raises an error if the row was modified after it was queried, preventing lost updates.
• UPDATE_ROW — Applies modifications to an existing Financial Element row, including re-validating the lock state and refreshing the "who" audit columns for the updating session.
• DELETE_ROW — Removes a Financial Element row (together with related translation rows) from the underlying tables.
• ADD_LANGUAGE — Inserts translated (TL) rows for a Financial Element into FND_LANGUAGES-registered languages, enabling multi-language display of the element name/description.
• TRANSLATE_ROW — Updates or maintains the translated attributes for an existing Financial Element in a specified language.

Per the ETRM documentation, no parameter lists are published for these procedures; they follow the conventional generated signature that takes a row type, a language code, and/or the primary key columns of the Financial Element. Developers should refer to the live package specification in the target instance rather than assume parameters.

Tables Accessed

The package reads and writes three objects, all through APPS synonyms:

• FEM_FIN_ELEMS_B — the base table holding Financial Element definitions; the target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
• FEM_FIN_ELEMS_TL — the translation table holding language-specific names and descriptions; populated by ADD_LANGUAGE and TRANSLATE_ROW and read during translated updates.
• FND_LANGUAGES — the Oracle Application Object Library lookup of installed and active languages, used by ADD_LANGUAGE to determine which languages require translation rows.

Usage Notes

FEM_FIN_ELEMS_PKG is referenced by four other APPS packages: FEM_DIM_UTILS_PVT, FEM_FIN_ELEMS_DL, FEM_FIN_ELEMS_IL, and FEM_FIN_ELEMS_UL. This reference chain indicates that the package is invoked indirectly from ETRM dimension utility logic and from the generated database-layer (DL), installation (IL), and upgrade (UL) scripts for the Financial Elements entity. It is normally executed during:

• ETRM setup and dimension maintenance performed through Enterprise Performance Foundation forms or concurrent programs that add, change, or remove Financial Elements.
• Patch application and upgrade scripts that stage, load, or translate Financial Element definitions via the DL/IL/UL packages.
• Custom integrations that create or maintain Financial Elements programmatically, which should call the DL/DL-adjacent entry points rather than the table handler directly.

Because the package is classified OTHER and writes to configuration tables, direct invocation should be avoided in custom code unless no higher-level API exists. Integrity of FEM_FIN_ELEMS_B and FEM_FIN_ELEMS_TL is critical to downstream Financial Item and dimension processing, so any custom usage must supply correct who-column values, valid language codes, and honor the locking contract enforced by LOCK_ROW.