Search Results fem_entities_il

Overview

APPS.FEM_ENTITIES_PKG is a PL/SQL package that owns the data manipulation logic for the Enterprise Performance Foundation (EPF) / Enterprise Planning and Budgeting (EPB) entity definition model within Oracle E-Business Suite 12.1.1 and 12.2.2. In the FEM schema, an "entity" represents an analytical or financial structure definition (such as a ledger-aligned dimension, hierarchy owner, or a calendar/ledger container) used by the FEM engine to resolve dimensional and transactional data across the Analytical Workspace.

The package functions as a low-level table maintenance API, providing the insert, update, delete, locking, and translation operations required to persist entity rows in the FEM_ENTITIES_B base table and its translatable companion FEM_ENTITIES_TL. It is classified as OTHER in the ETRM registry, indicating it is not a public bulk-processing API but an internal repository layer invoked by the entity data loaders and by dependent private utilities. Its status is recorded as VALID, confirming that the compiled specification and body are present and synchronized in the APPS schema.

Key Procedures and Functions

Six documented entry points are exposed by the package:

• INSERT_ROW — Creates a new entity record in the base table. This is the entry point used when a new entity must be registered before it can be referenced by a hierarchy or dimension assignment.
• LOCK_ROW — Acquires a row-level lock on an existing entity record, typically using SELECT ... FOR UPDATE semantics, to serialize concurrent modification attempts by parallel loader sessions.
• UPDATE_ROW — Modifies the attributes of an existing entity row, preserving the surrogate key while refreshing descriptive and control columns.
• DELETE_ROW — Removes an entity record from the base table, subject to referential integrity constraints imposed by dependent FEM objects.
• ADD_LANGUAGE — Inserts a translated (non-base-language) row into FEM_ENTITIES_TL for an entity that already exists in the base table, supporting multi-language deployment.
• TRANSLATE_ROW — Maintains or updates an existing translation row in the TL table, allowing the entity name and description to be adjusted per installed language.

No parameter signatures are documented in the ETRM metadata; consumers should rely on the installed package specification in the APPS schema for exact argument lists.

Tables Accessed

The package operates against three documented tables via APPS synonyms:

• FEM_ENTITIES_B — the base (non-translatable) table holding the primary entity definition, its surrogate identifier, and control attributes.
• FEM_ENTITIES_TL — the translation table holding language-specific entity names and descriptions, keyed by language and the base entity identifier.
• FND_LANGUAGES — the Oracle Applications language registry, consulted when adding or validating translation rows so that only installed languages are permitted.

Usage Notes

FEM_ENTITIES_PKG is referenced by four dependent packages: FEM_DIM_UTILS_PVT, FEM_ENTITIES_DL, FEM_ENTITIES_IL, and FEM_ENTITIES_UL. These correspond to the utility, download, import, and upload paths of the FEM entities migration flow. Consequently the package is invoked indirectly whenever entity metadata is loaded, imported, or extracted through the Analytical Workspace administration functions, rather than being called directly from Oracle Forms or from end-user UI.

Because the package is owned by APPS and its operations are internal, customizations should not invoke it directly unless the calling program fully replicates the validation and locking behavior expected by the FEM loaders. The presence of the LOCK_ROW procedure indicates the intended concurrency model: parallel download or import sessions must lock an entity before updating it. Any custom extension should respect the same sequence—lock, validate, then insert, update, or delete—to avoid corrupting the entity registry shared across the FEM schema.