Search Results fem_dimensions_ul

Overview

FEM_DIMENSIONS_PKG is a procedural PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Enterprise Tax, Reporting, and Management (ETRM) product family, which underpins Oracle Financial Services applications such as Profitability Manager, Transfer Pricing, and Allocations Manager. The package provides the core data manipulation and concurrency-control logic for the FEM_DIMENSIONS entity, which stores the definition of dimensions used throughout the ETRM analytical model. Dimensions in this context represent the configurable axis values — such as organizational unit, product, customer, or channel — against which balances and financial results are aggregated and analyzed.

The package is classified under the ETRM API classification of "OTHER," indicating that it is an internal implementation package rather than a formally published public API. Its primary role is to encapsulate the standard insert, update, delete, lock, and language-translation operations performed against the base and translated dimension tables. By centralizing these operations, the package ensures consistent behavior, referential integrity, and multilingual support across all callers.

Key Procedures and Functions

• INSERT_ROW — Creates a new dimension definition record. It writes the primary row into the base table and, where applicable, seeds corresponding translated rows, establishing a new dimension entry within the analytical model.
• LOCK_ROW — Acquires a row-level lock on an existing dimension record to enforce concurrency control, preventing conflicting modifications by simultaneous sessions.
• UPDATE_ROW — Modifies the attributes of an existing dimension record, applying the validated changes to the base table and reflecting them in dependent translated rows as required.
• DELETE_ROW — Removes a dimension definition and its associated translated records, subject to the integrity rules governing dimension usage.
• ADD_LANGUAGE — Inserts translated dimension rows for a specified language, enabling the dimension name and description to be presented in additional installed languages.
• TRANSLATE_ROW — Populates or refreshes the translatable columns of an existing dimension row for a given language, maintaining synchronization between the base definition and its translations.

Tables Accessed

• FEM_DIMENSIONS_B — The base table holding the language-independent definition of each dimension, including its identifying attributes and operational flags. It is the primary target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
• FEM_DIMENSIONS_TL — The translated table storing language-specific name and description values. It is written by ADD_LANGUAGE and TRANSLATE_ROW and maintained in tandem with changes to the base row.
• FND_LANGUAGES — The Oracle Application Object Library table of installed and active languages, consulted to validate that a requested translation language is available before inserting into FEM_DIMENSIONS_TL.

All three tables are referenced through APPS synonyms, consistent with standard EBS coding conventions.

Usage Notes

FEM_DIMENSIONS_PKG is an internal package and is not intended for direct invocation by end users or external integrations. It is referenced by three dependent database objects — FEM_DIMENSIONS_DL, FEM_DIMENSIONS_IL, and FEM_DIMENSIONS_UL — which are the entity's standard Data Layer, Interface Layer, and Update Layer packages forming part of the ETRM-generated table handler architecture. It is also self-referenced, indicating internal calls between its procedures.

In practice, the package is typically invoked indirectly through the ETRM dimension setup forms and concurrent programs, or through the surrounding table handler stack when dimension metadata is created or maintained. The DL, IL, and UL packages layer validation, business rules, and database operations on top of this package, with the DL providing query access, the IL handling inserts, and the UL managing updates and deletes. Custom development should call those higher-level handler packages rather than FEM_DIMENSIONS_PKG directly, to preserve the validation and integrity logic that the handler layer enforces.