Search Results purge_personal_metadata




Overview
Explore in AI Chat

Overview

APPS.FEM_DIM_PRS_UTILS_PVT is a private (PVT classification) PL/SQL package in the Oracle E-Business Suite Applications schema. It forms part of the Enterprise Territory Management (ETRM) / FEM (Financial Enterprise Management) dimension processing infrastructure. The package is a utility-layer component whose primary responsibility is the maintenance and cleansing of dimensional personalization metadata — the user- or responsibility-specific overrides, preferences, and cached dimension attributes that applications layer on top of the base ETRM dimension definitions.

Within the ETRM architecture, dimensional data such as budgets, calendar periods, cost center organizations, channels, and customers are stored in paired base and translation tables (_B and _TL) with matching _ATTR side tables. Business users frequently personalize how these dimensions appear and behave in their UI sessions. The personalization records accumulate over time and must be periodically purged when responsibilities change, when users are removed, or when customization data becomes stale. FEM_DIM_PRS_UTILS_PVT encapsulates that housekeeping logic.

The package has no known dependency on other application PL/SQL packages at the object level; its dependencies resolve to the SYS.STANDARD package only, indicating a self-contained implementation that relies solely on the PL/SQL runtime. It is not referenced by any other documented package, and there are no documented callers in the ETRM dependency chain. Validation status is VALID, confirming that the package compiles and is present in a supported state in the EBS instance.

Key Procedures and Functions

The documented interface exposes one public program unit:

  • PURGE_PERSONAL_METADATA — Removes personalization metadata records associated with ETRM dimensions. This procedure is the core maintenance routine of the package and is intended to be invoked when a user, responsibility, or personalization context must be reset. Because it is defined inside a _PVT package, it is expected to be treated as an internal utility rather than a public API; callers outside the ETRM product family should not invoke it directly. No parameter list is published in the ETRM metadata, and none should be assumed.

The package body may contain additional private helpers, but only PURGE_PERSONAL_METADATA is documented. Its narrow scope — a single cleanup entry point — is consistent with the PVT naming convention, which typically designates packages whose sole purpose is to support a parent processing flow.

Tables Accessed

The package touches the attribute and base/translation tables underlying five ETRM dimension families. Accesses are made through APPS synonyms.

The recurring pattern — an attribute table plus a base table plus a translation table per dimension — indicates the procedure locates personalization rows via the attribute table and then cascades or validates against the base and translated dimension definitions before removal.

Usage Notes

Direct invocation by end users is not expected. Typical invocation paths for a package of this class include:

  • Concurrent programs: administrative purge or cleanup concurrent requests that clear stale ETRM personalization data across a set of dimensions.
  • Internal ETRM processing: called from within the ETRM product code when a responsibility or personalization context is reset.
  • Custom code: supported only for controlled maintenance scripts written by implementers who understand the FEM data model; the PVT classification means Oracle does not warrant the interface.

Because the package carries no documented external dependents, implementers modifying or wrapping it should verify all call sites directly in the deployed schema. As with any _PVT utility, Oracle may change its signature without notice in future releases, so custom code should avoid binding to it where a supported public API exists.