Search Results user_dim2_id




Overview
Explore in AI Chat

Overview

APPS.FEM_USER_DIM2_PKG is a PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that supports the Enterprise Territory and Resource Management (ETRM) / Enterprise Planning and Budgeting (EPB) family of products. It manages the persistence layer for user-defined dimension type 2 records, which allow customers to extend the analytical model of the application with their own dimensions beyond the seeded standard dimensions. Because Oracle EBS stores such dimensional metadata as application data rather than as database objects, this package provides the programmatic interface through which user dimension 2 definitions are created, queried, locked, modified, deleted, translated, and propagated across installed languages.

The package adheres to the standard Oracle EBS table-handler pattern: one base table (FEM_USER_DIM2_B) stores language-independent attributes, while a translation table (FEM_USER_DIM2_TL) stores language-dependent attributes such as the dimension name and description. The object version number and read-only flag columns confirm that the standard Oracle EBS optimistic-locking and concurrency model is applied to these records.

Key Procedures and Functions

ETRM documents six procedures in this package body. They constitute a complete CRUD-plus-translation API:

  • INSERT_ROW — Creates a new user dimension 2 definition. It first verifies that no existing base row matches the supplied USER_DIM2_ID and VALUE_SET_ID combination, then inserts the language-independent attributes into FEM_USER_DIM2_B and inserts a corresponding translation row into FEM_USER_DIM2_TL for every installed language (L.INSTALLED_FLAG in 'I' or 'B'), seeded from FND_LANGUAGES using the session language as SOURCE_LANG.
  • LOCK_ROW — Acquires a row-level lock on the target user dimension 2 record to serialize concurrent updates and enforce the optimistic-locking contract before modification.
  • UPDATE_ROW — Modifies an existing user dimension 2 definition in the base table, and updates or inserts the associated translation rows as required.
  • DELETE_ROW — Removes the user dimension 2 definition and its associated translation rows from the underlying tables.
  • ADD_LANGUAGE — Propagates a newly installed language to existing user dimension 2 records. This procedure is invoked when an additional language is installed in the EBS instance, ensuring every existing base row receives a corresponding TL row for the new language.
  • TRANSLATE_ROW — Updates the translated name and description of an existing user dimension 2 record for the current session language.

The insert interface accepts, among other values, X_USER_DIM2_ID, X_VALUE_SET_ID, X_DIMENSION_GROUP_ID, X_USER_DIM2_DISPLAY_CODE, X_ENABLED_FLAG, X_PERSONAL_FLAG, X_OBJECT_VERSION_NUMBER, X_READ_ONLY_FLAG, X_USER_DIM2_NAME, and X_DESCRIPTION, together with the standard WHO audit columns.

Tables Accessed

  • FEM_USER_DIM2_B — The base table holding language-independent user dimension 2 attributes. Inserted and updated by INSERT_ROW and UPDATE_ROW and secured by LOCK_ROW via a ROWID cursor.
  • FEM_USER_DIM2_TL — The translation table holding USER_DIM2_NAME and DESCRIPTION per language. Written on insert, update, delete, language addition, and translation events.
  • FND_LANGUAGES — The Oracle Application Object Library language registry, queried during INSERT_ROW to drive multi-language seeding of the translation table.

Usage Notes

This package is a program unit rather than an end-user interface. It is referenced by four other packages within the ETRM schema, which act as higher-level business APIs and forms-based handlers. Typical invocation paths include:

  • Oracle Forms and OAF pages through which administrators define or maintain user dimension 2 members, where the form block calls these procedures rather than issuing direct DML.
  • Concurrent programs and setup utilities performing bulk loading of user dimension definitions.
  • Language installation and patching routines that call ADD_LANGUAGE to back-fill translations.

Because these procedures implement the supported table-handler interface, customizations and integrations should invoke them rather than writing directly to the FEM_USER_DIM2_B and FEM_USER_DIM2_TL tables, thereby preserving audit columns, object versioning, and translation integrity.