Search Results fem_dsnp_rule_dims




Overview

The APPS.FEM_DIM_SNAPSHOT_UTIL_PKG package body is a utility package within the Oracle Enterprise Data Management / Enterprise Tax Reporting and Management (ETRM) modules of Oracle E-Business Suite. ETRM is the umbrella terminology for the consolidation, dimensional, and management reporting framework delivered within the EBS 12.1.1 and 12.2.2 applications stack, and its FEM (Financial Enterprise Management) schema hosts the metadata objects that define dimensions, hierarchies, and snapshot rules. This package provides the programmatic scaffolding required to add and remove dimension definitions from the dimensional snapshot model. A snapshot, in this context, is a stored representation of a dimension structure at a point in time, used to support reporting, consolidation, and analytical processing.

The package body was originally authored in July 2005 and has a header version of 120.0, reflecting it is a relatively stable, low-version object. Its declared package constant pc_pkg_name is set to 'fem_object_catalog_util_pkg', and it references FND_LOG.level_unexpected for logging. The package includes a Validate_OA_Params helper procedure that enforces the standard Oracle Applications API parameter contract (p_init_msg_list, p_commit, p_encoded, and x_return_status), including raising exceptions for invalid parameter values and initializing the FND message stack when requested.

Key Procedures and Functions

ETRM documentation lists two documented procedures for this package:

  • ADD_DIMENSION — Adds a dimension definition to the dimensional snapshot context. It is the counterpart to the removal operation and is used when a dimension must be introduced into the snapshot rules maintained against the object catalog and object definition metadata.
  • REMOVE_DIMENSION — The procedure most commonly searched for under the term "remove_dimension." It deletes or de-registers a dimension from the dimensional snapshot configuration. This is the operation invoked when a dimension is no longer required in a snapshot rule, effectively decoupling the dimension from the snapshot definition.

Both procedures operate under the standard OA framework parameter convention validated by Validate_OA_Params, which establishes the expected x_return_status output pattern (c_success or failure) and controls message list initialization and commit behavior. No parameter lists are reproduced here since the ETRM excerpt does not expose the full signatures of ADD_DIMENSION or REMOVE_DIMENSION.

Tables Accessed

The package performs DML and queries against the following documented APPS-synonym tables:

  • FEM_DSNP_RULE_DIMS — The snapshot rule dimension table. This is the primary repository of dimension-to-snapshot-rule associations; ADD_DIMENSION and REMOVE_DIMENSION insert into and delete from this table respectively.
  • FEM_OBJECT_CATALOG_B — The base object catalog, holding registered FEM objects. It provides referential context for the dimensions being manipulated.
  • FEM_OBJECT_DEFINITION_B — The base object definition table, storing definition attributes for catalog objects. It supports validation and lookup of dimension definitions.
  • DBMS_UTILITY and DUAL — Utility package and dual table used for internal PL/SQL support, such as callstack formatting and constant evaluation.

Usage Notes

This package is classified as "OTHER" in the ETRM API classification scheme, indicating it is not a public interface API but an internal utility. It is referenced by zero other packages according to ETRM dependency data, which suggests it is invoked through direct calls from ETRM forms, concurrent programs, or controlled custom extensions rather than through a wide internal call graph. Typical invocation occurs during dimension maintenance workflows in the ETRM setup and administration user interfaces, where an administrator adds or removes dimensions from snapshot rules. Custom code that manipulates snapshot configuration should call the package only after validating the standard OA parameters, and should respect the commit and message-list semantics enforced by Validate_OA_Params. Given the low version number and 2005 origin, the package should be treated as stable but tightly coupled to the FEM dimensional metadata model in 12.1.1 and 12.2.2.