Search Results update_policyset

Overview

FND_OAM_DSCRAM is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that implements the server-side API layer for the Oracle Applications Manager (OAM) Data Scrambling and Data Privacy framework. The package name, historically derived from "Data SCRAMbling," reflects its original purpose of defining and maintaining scrambling policies used to obfuscate sensitive production data before it is copied into non-production environments. Over successive releases the framework was extended to cover personally identifiable information (PII) attributes, and FND_OAM_DSCRAM consequently manages policies, policy sets, attributes, PII extensions, deletion elements, and purge table mappings. It declares AUTHID CURRENT_USER, so all SQL executes with the privileges of the calling session rather than the package owner.

The package is classified as API classification OTHER in ETRM 12.2.2 and is referenced by no other documented packages, indicating it is a top-level administrative API invoked directly rather than a shared library. The header identifies the shipped source as AFOAMDSS.pls, version 120.6.12000000.3, dated 2007/04/21.

Key Procedures and Functions

The documented procedures fall into four functional groups.

• Policy management: INSERT_POLICY creates a scrambling policy in the base and translation tables; UPDATE_POLICY modifies an existing policy; DELETE_POLICY removes one. ADD_POLICY_ATTRI_ELEMENT attaches an attribute to a policy as a scramble element, and ADD_POLICY_DEL_ELEMENT attaches a deletion element. REMOVE_POLICY_ELEMENTS clears all elements for a given policy identifier.
• Policy set management: INSERT_POLICYSET and UPDATE_POLICYSET create and maintain named groupings of policies; ADD_PSET_ELEMENT attaches a policy to a set; REMOVE_PSET_ELEMENTS clears membership; DELETE_PSET removes a set.
• Attribute management: ADD_ATTRIBUTE_COL registers a column as a scramblable attribute; INSERT_PII_ATTRIBUTE, UPDATE_PII_ATTRIBUTE, PRE_UPDATE_PII_ATTRIBUTE, and DELETE_PII_ATTRIBUTE maintain the PII extension definitions that mark attributes as containing personal data.
• Delete element maintenance (the area surfaced by the "remove_delete" search): ADD_DELETE registers a delete rule, UPDATE_DELETE modifies it, and REMOVE_DELETE removes a delete element from the FND_OAM_DS_DELETES data. DELETE_TBL_TO_PURGE removes a table mapping from the purge list. These procedures are the counterpart to ADD_POLICY_DEL_ELEMENT and REMOVE_POLICY_ELEMENTS, which operate at the policy-to-element association level rather than on the delete definition itself.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• Policy tables: FND_OAM_DS_POLICIES_B, FND_OAM_DS_POLICIES_S (sequence surrogate), and FND_OAM_DS_POLICIES_TL (translated descriptions) store policy headers and names.
• Policy element tables: FND_OAM_DS_POLICY_ELMNTS and FND_OAM_DS_POLICY_ELMNTS_S hold the attribute and delete elements attached to each policy.
• Policy set tables: FND_OAM_DS_PSETS_B and FND_OAM_DS_PSETS_S store named policy groupings.
• Attribute and PII tables: FND_OAM_DS_ATTRI_S stores attribute definitions; FND_OAM_DS_PII_EXTENSIONS and FND_OAM_DS_PII_EXTENSIONS_S store PII extension metadata; FND_COL_PRIV_ATTRIBUTES_B links columns flagged as private; FND_COLUMNS supplies column metadata used when registering attributes.
• Delete tables: FND_OAM_DS_DELETES and FND_OAM_DS_DELETES_S store delete-rule definitions manipulated by ADD_DELETE, UPDATE_DELETE, and REMOVE_DELETE.
• Reference table: FND_LANGUAGES supports translated name and description maintenance.

Usage Notes

FND_OAM_DSCRAM is not exposed to end users through standard EBS forms or concurrent programs in 12.1.1 or 12.2.2. It is invoked by the Oracle Applications Manager Data Scrambling and Data Privacy administrative UI, and by Database Administrator scripts that bulk-load or maintain scramble policies, policy sets, PII attribute definitions, and delete rules prior to cloning production into test instances. Custom code seldom calls this package directly; implementations typically rely on the OAM screens or on direct DML against the underlying tables. Because the package runs with invoker's rights, callers must themselves hold privileges on the touched tables and be connected as APPS or an equivalently privileged account. The procedures carry only one OUT parameter (the generated identifier for new policies and policy sets) and otherwise return no status code, so exceptions are surfaced through standard PL/SQL error handling. Any modification to delete or PII metadata should be performed with the same care applied to any data-privacy configuration change, since these definitions govern what data is masked or purged when environments are refreshed.