Search Results fnd_oam_ds_psets_s

Overview

FND_OAM_DSCRAM is a private Oracle E-Business Suite PL/SQL package body that implements the server-side data scrambling framework used by Applications Manager (OAM). Its purpose is to define, maintain, and apply policies that mask or substitute sensitive column data—most notably Personally Identifiable Information (PII)—so that cloned, test, or non-production copies of an EBS database can be scrubbed of confidential values. The package name itself reflects the runtime profile option that governs whether scrambling is active, commonly referenced as oam_dscram_enabled. When that setting is enabled, the DSCRAM layer becomes the mechanism through which EBS identifies which columns hold regulated data and how those columns should be transformed.

The body operates against a normalized set of FND_OAM_DS_* tables that store policies, policy elements, policy sets, PII extensions, and delete/purge rules. It is declared as an APPS-owned package with an API classification of OTHER, indicating it is an internal utility rather than a formally published public API. The header comment block shows the package as a long-lived component of the OAM toolset, with the oldest revision dating to the 2000s and carrying forward into the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented interface exposes twenty-two procedures spanning three functional areas:

• Policy lifecycle: INSERT_POLICY creates a new scrambling policy, seeding both the base table (FND_OAM_DS_POLICIES_B) and the translation table (FND_OAM_DS_POLICIES_TL). UPDATE_POLICY modifies an existing policy definition, while DELETE_POLICY removes one.
• Policy elements and attributes: ADD_POLICY_ATTRI_ELEMENT, ADD_POLICY_DEL_ELEMENT, ADD_ATTRIBUTE_COL, and REMOVE_POLICY_ELEMENTS manage the individual attributes or columns attached to a policy. INSERT_PII_ATTRIBUTE, UPDATE_PII_ATTRIBUTE, PRE_UPDATE_PII_ATTRIBUTE, and DELETE_PII_ATTRIBUTE handle the registration and maintenance of PII-designated columns.
• Policy sets and deletions: INSERT_POLICYSET, UPDATE_POLICYSET, ADD_PSET_ELEMENT, REMOVE_PSET_ELEMENTS, and DELETE_PSET manage groupings of policies. ADD_DELETE, UPDATE_DELETE, REMOVE_DELETE, and DELETE_TBL_TO_PURGE maintain the set of tables and rows targeted for deletion during scrambling.

The source excerpt for INSERT_POLICY confirms the pattern: it obtains a primary key from FND_OAM_DS_POLICIES_S, writes the base row, then populates the translation row for every installed language in FND_LANGUAGES where a translation does not already exist. The B_DSCRAM_LEVEL_USER_DEFINED constant ('USER_DEFINED') marks attributes and column privileges that originated from the OAM user interface.

Tables Accessed

The package reads and writes several APPS synonyms. FND_OAM_DS_POLICIES_B, _TL, and _S hold policy headers, translations, and the sequence. FND_OAM_DS_POLICY_ELMNTS and its sequence store the attribute/column elements that make up a policy. FND_OAM_DS_PSETS_B and _S store policy sets. FND_OAM_DS_PII_EXTENSIONS and _S hold PII extension definitions. FND_OAM_DS_ATTRI_S supplies attribute sequence values. FND_OAM_DS_DELETES and _S track tables and rows scheduled for purge. FND_COLUMNS and FND_COL_PRIV_ATTRIBUTES_B provide the EBS data dictionary context that maps scrambling targets to physical columns and privileges, while FND_LANGUAGES drives translation row creation.

Usage Notes

FND_OAM_DSCRAM is invoked indirectly by the OAM Data Scrambling UI and accompanying concurrent programs rather than by ad hoc application code. Administrators define policies and PII attributes through the scrambling setup forms; those forms call this package to persist the configuration. Actual scrambling execution is performed by the OAM scrambling engine, which reads the policies and elements maintained here. Because the package is classified OTHER and referenced by zero other packages, it should be treated as internal: customizations that call it directly risk breaking on patch application. The oam_dscram_enabled profile option controls whether the resulting policy definitions take effect at runtime.