Search Results g_stage_cleanup




Overview

FND_OAM_DSCFG_API_PKG is a public PL/SQL package in the APPS schema that provides the programmatic interface for Oracle EBS Applications Data Scrambling Configuration. The package governs the definition, staging, and maintenance of data scrambling configuration entities used when cloning or copying an E-Business Suite environment. Its API classification is OTHER, and it is declared with AUTHID CURRENT_USER, meaning all unqualified object references resolve to the calling schema rather than to APPS. The package header identifies it as AFOAMDSCAPIS.pls (revision 120.3), owned historically by the Applications Framework group.

The package organizes scrambling configuration into a small set of typed entities. Instance types are defined by G_CONFTYPE_CLONING; parent types distinguish configuration levels through G_TYPE_INSTANCE, the G_TYPE_OBJECT constant referenced by callers searching for "g_object", and G_TYPE_PROC. Procedure stages are enumerated through G_STAGE_IMPORT, G_STAGE_PRE_COMPILE, G_STAGE_POST_COMPILE, G_STAGE_PRE_EXECUTE, G_STAGE_POST_EXECUTE, and G_STAGE_CLEANUP, while procedure types are limited to G_PROCTYPE_TARGET_PLSQL and G_PROCTYPE_AGENT_JAVA.

Key Procedures and Functions

The documented API surface contains thirty procedures and functions. They fall into several functional groupings:

Tables Accessed

Two persistent tables underpin the package's storage model, both exposed to APPS through synonyms: FND_OAM_DSCFG_OBJECTS, which stores the configuration objects created through the ADD_* APIs, and FND_OAM_DSCFG_PROPERTIES, which stores the properties bound to those objects via ADD_OBJECT_PROPERTY. The package also references DBMS_SQL for dynamic SQL operations, consistent with its role in generating and running scrambling statements against target tables.

Usage Notes

FND_OAM_DSCFG_API_PKG is invoked internally by Oracle Applications Manager data scrambling and cloning infrastructure rather than by end users directly. It is referenced by six other packages in the EBS code base and is typically executed during the configuration phase that precedes a clone, when scrambling rules must be defined for schemas, tables, and columns. Developers extending scrambling behavior should call the ADD_* routines within the active configuration instance established via SET_CURRENT_CONFIG_INSTANCE, after confirming with ARE_CONFIG_CHANGES_ALLOWED and IS_CONFIG_INSTANCE_INITIALIZED that the instance accepts modification. Because the package executes as AUTHID CURRENT_USER and relies on APPS synonyms, custom callers must be granted appropriate privileges on the underlying configuration tables.