Search Results fem_mapping_preview_util_pkg




Overview
Explore in AI Chat

Overview

FEM_MAPPING_PREVIEW_UTIL_PKG is an Oracle Enterprise Business Suite (EBS) PL/SQL utility package owned by the APPS schema and classified under the ETRM (Enterprise Taxation and Reporting Management / Enterprise Performance Foundation) module. It supports the mapping preview capability of the Enterprise Performance Foundation (FEM) application, which underpins ledger-based allocations, balances, and mapping definitions in Oracle EBS 12.1.1 and 12.2.2. Its primary business function is to manage the lifecycle of mapping preview results—the simulation output that allows users to validate how source dimension members map to target members before committing an allocation or mapping definition. By centralizing preview processing logic, the package ensures that preview computations, cleanup of stale preview data, and post-processing cleanup occur in a consistent, API-driven manner rather than through ad hoc SQL.

Key Procedures and Functions

The package exposes three documented procedures, each corresponding to a stage of the preview lifecycle:

  • PRE_PROCESS — Prepares the environment and staging structures prior to executing a mapping preview. It establishes the context in which preview computations run, ensuring that prior or conflicting preview data does not corrupt the new run.
  • POST_PROCESS — Executes after the preview computation completes, finalizing statistics, consolidating results, and performing any required housekeeping so that the preview output is in a stable, reportable state.
  • REMOVE_RESULTS — Deletes preview artifacts for a given context, purging temporary mapping preview rows, maps, and statistics when a preview is no longer required. This procedure supports the cleanup of superseded or abandoned preview runs.

The package depends on FND_API for Oracle Application Object Library error handling, and it is referenced by FEM_BR_MAP_PREVIEW_PVT, indicating it serves as a supporting utility invoked by the higher-level business rule mapping preview private API. Its procedures are called internally and are not intended as documented public entry points for end users.

Tables Accessed

The package operates against APPS synonyms spanning the FEM schema. The preview-specific tables—FEM_ALLOC_PREVIEWS, FEM_ALLOC_PREVIEW_MAPS, and FEM_ALLOC_PREVIEW_STATS—store the generated preview results, the mapping relationships produced, and processing statistics respectively. Configuration and definition tables referenced include FEM_ALLOC_BR_DIMENSIONS, FEM_ALLOC_BR_FORMULA, and FEM_ALLOC_BR_OBJECTS (allocation business rule definitions), FEM_DIMENSIONS_B, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, and FEM_DIM_TEMPLATE (dimension and attribute metadata), FEM_FUNCTION_CD_MAPPING and FEM_GLOBAL_VS_COMBO_DEFS (mapping and combination definitions), and FEM_CAL_PERIODS_ATTR and FEM_LEDGERS_ATTR (calendar period and ledger attribute context). FEM_BALANCES provides the source balance data against which mappings are previewed. These references reflect the package's role in reading definitional metadata and balances while writing preview output and statistics to the preview staging tables.

Usage Notes

FEM_MAPPING_PREVIEW_UTIL_PKG is typically invoked indirectly through the FEM mapping preview framework rather than by direct user action. In Oracle EBS, mapping preview is exposed through the Enterprise Performance Foundation responsibility, where users simulate dimension mappings for allocations and business rules. The FEM_BR_MAP_PREVIEW_PVT package calls this utility to manage the preview lifecycle. Concurrent programs and forms that trigger a mapping preview rely on PRE_PROCESS and POST_PROCESS to bracket the computation, while REMOVE_RESULTS is invoked during cleanup or when a preview is discarded. Custom code should not call these procedures directly unless simulating the same framework, because they assume the caller has established the FEM security context and required FND_API state. As with all APPS-owned packages, direct modification is unsupported; any extension should wrap the documented procedures and preserve the standard preview processing sequence.