Search Results fem_global_vs_combos_pkg

Overview

FEM_GLOBAL_VS_COMBOS_PKG is the PL/SQL package that maintains master reference data for global value set combinations within Oracle Enterprise Taxation and Revenue Management (ETRM), a module delivered on the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack. A global value set combination associates a value set with configuration rules that apply consistently across jurisdictions and registration contexts, which is fundamental to ETRM's tax determination and revenue registration logic. The package body, owned by the APPS schema and documented as VALID, provides the data-access layer over the underlying base and translation tables of the entity. Its procedures implement standard Oracle Forms-compatible DML semantics alongside a multi-language translation mechanism, allowing the ETRM application to present global value set combination definitions in the languages enabled in FND_LANGUAGES. The object is classified as an OTHER API in the ETRM repository, indicating that it is primarily an internal data-maintenance layer invoked by ETRM forms and concurrent utilities rather than a public integration API intended for third-party callers.

Key Procedures and Functions

The package body exposes six documented procedures:

• INSERT_ROW — Creates a new global value set combination record in the base table, populating the identifier and attribute columns required for the definition. It exists to give form-based maintenance a single controlled entry point for inserts rather than allowing direct table manipulation.
• UPDATE_ROW — Modifies attributes of an existing global value set combination, such as its associated value set or configuration attributes, while preserving the record identity.
• DELETE_ROW — Removes a global value set combination and is responsible for cascading the deletion to the associated translation rows so no orphaned language records remain.
• LOCK_ROW — Acquires a row-level lock on a combination record prior to modification. This enforces the optimistic locking pattern used throughout Oracle Forms with ETRM, preventing concurrent users from overwriting one another's changes.
• ADD_LANGUAGE — Seeds translation rows in FEM_GLOBAL_VS_COMBOS_TL for newly installed or enabled languages, ensuring the entity carries entries for every language defined in FND_LANGUAGES.
• TRANSLATE_ROW — Inserts or updates the translated description text for a given combination in a specific language, supporting the multilingual presentation of global value set combinations.

Tables Accessed

The package reads and writes through APPS synonyms over three base objects:

• FEM_GLOBAL_VS_COMBOS_B — the base table holding the untranslated, language-independent definition of each global value set combination. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW operate directly on this table.
• FEM_GLOBAL_VS_COMBOS_TL — the translation table storing language-specific descriptive text keyed to FEM_GLOBAL_VS_COMBOS_B. ADD_LANGUAGE and TRANSLATE_ROW write here, and DELETE_ROW maintains referential integrity against it.
• FND_LANGUAGES — the Oracle Applications language repository, queried to determine which installed, enabled languages require translation rows.

Additional dependencies recorded in the ETRM dependency listing include APP_EXCEPTION, FND_MESSAGE, and FND_LOAD_UTIL, confirming that the package raises standardized application errors and participates in Oracle's language-loading and patch utilities.

Usage Notes

FEM_GLOBAL_VS_COMBOS_PKG is invoked whenever global value set combinations are maintained through ETRM setup forms, which call INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW from their block-level triggers. ADD_LANGUAGE is typically run from language installation or upgrade paths, while TRANSLATE_ROW is used both by translation maintenance forms and by FND_LOAD_UTIL-driven translation loads during patching. The ETRM metadata records that the package is referenced by four other packages, so its behavior also propagates indirectly into higher-level ETRM processing. Under EBS 12.1.1 and 12.2.2 these tables reside in the APPS schema with the ONLINE editioning and synonym conventions typical of the E-Business Suite, meaning the package must be patched through standard AD utilities rather than compiled ad hoc. Custom code should generally not call these procedures directly; interaction with global value set combinations is safer through the ETRM-supported setup forms, because the procedures assume the locks, IDs, and language context established by the calling form or loader.