Search Results oam_dscram_allowed




Overview

FND_OAM_DSCRAM_RUNS_PKG is an Oracle E-Business Suite internal package that manages the lifecycle of database scrambling "runs" executed through the Oracle Applications Manager (OAM) Diagnostics and Scrambling framework. Its central responsibility is to track and validate the operational state of a scrambling run, gating execution against two profile options: OAM_DSCRAM_ENABLED, which determines whether scrambling functionality is active for the product, and OAM_DSCRAM_ALLOWED, which indicates whether the current instance is in a state where scrambling operations may proceed. This second profile, OAM_DSCRAM_ALLOWED, is the value frequently researched under the search term "oam_dscram_allowed," and it is declared within this package body as B_DSCRAM_ALLOWED_PROFILE_NAME. The package caches run metadata in a private PL/SQL record (b_run_info) so that downstream validation and worker-assignment logic can reference run identifiers, statistics identifiers, run mode, and argument context without repeated queries. Because scrambling affects sensitive production-adjacent data, the package enforces eligibility checks before any execution proceeds.

Key Procedures and Functions

Tables Accessed

  • FND_OAM_DSCRAM_RUNS_B — The base table holding run definitions and header attributes; the package caches values such as run_id, run_stat_id, and run_mode from it.
  • FND_OAM_DSCRAM_RUNS_TL — The translation table supplying language-specific run text.
  • FND_OAM_DSCRAM_STATS — Stores per-run statistics referenced through run_stat_id.
  • FND_LANGUAGES — Used by ADD_LANGUAGE to determine valid installed languages.
  • V$DATABASE — Queried to confirm instance identity and state during validation.

Usage Notes

This package is not a public API and carries an API classification of OTHER; it is invoked internally by the OAM Diagnostics and Scrambling infrastructure and is referenced by seven other packages in the application. It is typically called in the context of OAM scrambling concurrent programs and their associated worker processes rather than from standard EBS forms. Customizations should not call these routines directly, since the cached b_run_info record assumes initialization by the framework. Administrators investigating OAM_DSCRAM_ALLOWED should note that its value, alongside OAM_DSCRAM_ENABLED, directly governs whether VALIDATE_START_EXECUTION and VALIDATE_CONTINUED_EXECUTION permit scrambling activity at either Oracle EBS 12.1.1 or 12.2.2.