Search Results fem_loader_eng_util_pkg




Overview
Explore in AI Chat

Overview

FEM_LOADER_ENG_UTIL_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Enterprise Performance Foundation (EPF) / Financial Enterprise Management (FEM) engine framework, which underpins the ETRM (Enterprise Tax, Risk, and Management) and related financial consolidation and analytical applications in releases 12.1.1 and 12.2.2. The package serves a utility role within the loader engine subsystem: it resolves and returns the execution mode that governs how different categories of loader processes -- dimension, hierarchy, cross-GL (XGL), and fact loaders -- are run by the FEM loading engine. The package is classified as an "OTHER" API (not a public, externally supported interface), meaning it is intended for internal use by the FEM engine rather than for direct invocation by end users or third-party integrations. Its documented status is VALID, confirming that it compiles without error in the reference environment.

Key Procedures and Functions

The package body exposes four documented program units, all of which are execution-mode accessors:

  • GET_DIM_LOADER_EXEC_MODE — Returns the execution mode applicable to dimension loaders. This mode determines how the engine schedules and processes dimension member loading operations.
  • GET_HIER_LOADER_EXEC_MODE — Returns the execution mode for hierarchy loaders, which govern the loading of hierarchical relationship structures within a dimension.
  • GET_XGL_LOADER_EXEC_MODE — Returns the execution mode for cross-GL (XGL) loaders, used where data is sourced or reconciled across general ledgers.
  • GET_FACT_LOADER_EXEC_MODE — Returns the execution mode for fact loaders, which populate the numeric fact data associated with loaded dimensions and hierarchies.

These functions centralize the logic that the FEM engines use to decide whether a given loader should execute in a particular mode, such as synchronous versus parallel or online versus batch. No parameter lists are documented, and callers should treat these as internal helpers rather than a stable public contract.

Tables Accessed

The package references the following tables through APPS synonyms:

  • FEM_DATA_LOADER_OBJECTS — Defines the loader objects available to the engine and likely supplies the object context used when resolving execution modes.
  • FEM_OBJECT_CATALOG_B — The base catalog of FEM objects, used to identify the object being loaded.
  • FEM_PL_OBJECT_EXECUTIONS — Records of prior or current execution instances for loader objects.
  • FEM_PL_REQUESTS — Request records that drive loader execution within the FEM processing framework.
  • FEM_PL_TABLES — Metadata about the physical tables involved in the loading process.
  • FEM_XDIM_DIMENSIONS — Dimension definitions used by the cross-dimensional and dimension loaders.
  • FND_LOG_MESSAGES — The Oracle Application Object Library logging table, written for diagnostic tracing.

Supporting dependencies include FEM_ENGINES_PKG, FND_API, FND_LOG, FND_MSG_PUB, and the STANDARD package.

Usage Notes

FEM_LOADER_ENG_UTIL_PKG is not intended for direct end-user invocation. It is typically called internally by the FEM loading engine (notably FEM_ENGINES_PKG) and by three other APPS packages that reference it. In practice, administrators and developers encounter it indirectly when running FEM loader concurrent programs or when tracing loader behavior through FND_LOG output. Because the ETRM metadata records it as an "OTHER" API and documents no external entry points, custom code should avoid calling these functions directly; instead, invoke the supported loader engine interfaces that in turn use this utility. When troubleshooting loader execution, the key diagnostic path is to review FND_LOG_MESSAGES entries generated by this package and to inspect FEM_PL_REQUESTS and FEM_PL_OBJECT_EXECUTIONS for the associated request and execution records. The package is not referenced by any database object outside the APPS schema, confirming its position as a private implementation detail of the FEM engine layer.