Search Results cleanup_data

Overview

The APPS.IGI_SLS_SECURITY_PKG package body is a core component of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 application used by the IGI (i-Expenses / Grants and Security) product family. It provides the server-side security engine for the IGI Security Listing Service (SLS), which controls how organization, responsibility and group-level data access is enforced across secured SLS objects. The package resolves the effective schema (typically APPS or an MRC/MLS secondary schema), maintains the registry of secured tables, builds and refreshes the physical security objects used at runtime, populates group allocation mappings, consolidates security groups, applies security to existing data, and performs cleanup of stale security artifacts. The package is also the entry point for security maintenance and audit routines referenced by the IGI_SLS_SECURE_TABLES registry.

Key Procedures and Functions

• WRITE_TO_LOG — Writes diagnostic messages to the FND_LOG facility, gated by the current runtime log level, so that security operations can be traced during debugging and support.
• GET_MRC_MLS_SCHEMANAMES — Returns the schema name(s) applicable for the Multiple Reporting Currencies (MRC) and Multiple Language Support (MLS) contexts, ensuring security objects are created in the correct schema.
• CHECK_ALLOCATION_EXISTS — Determines whether an SLS allocation already exists for a given scope, preventing duplicate allocation creation.
• CREATE_DROP_SLS_OBJECTS — Creates or drops the physical database objects (views, synonyms or grants) used to enforce SLS security on the registered tables.
• REFRESH_SLS_OBJECTS — Rebuilds existing SLS security objects when definitions or secured table lists change, avoiding a full drop/recreate cycle.
• POPULATE_GROUP_ALLOC — Inserts the group allocation mappings that tie security groups to the objects they protect.
• CLEANUP_DATA — Removes obsolete or orphaned SLS security metadata rows (allocations, groups and audit records) left behind after responsibility or group changes. This is the procedure most closely associated with the searched term cleanup_data and serves as the housekeeping routine for the SLS security repository.
• CONSOLIDATE_GROUPS — Merges duplicate or overlapping security groups into a consolidated definition to simplify maintenance.
• APPLY_SECURITY — Applies the resolved security rules to the secured objects, enacting the group allocation state.
• SECURE_EXISTING_DATA — Retro-applies security to data that predates the SLS configuration, bringing legacy rows under the current security scheme.

Tables Accessed

The package operates primarily against IGI_SLS_SECURE_TABLES and its audit counterpart IGI_SLS_SECURE_TABLES_AUDIT to drive object creation and refresh. Allocation and grouping logic touches IGI_SLS_ALLOCATIONS, IGI_SLS_ALLOCATIONS_AUDIT, IGI_SLS_GROUPS, IGI_SLS_GROUPS_AUDIT, IGI_SLS_SECURITY_GROUP_ALLOC and IGI_SLS_CONSOLIDATE_GROUPS. The exception handling structure is anchored in the IGI runtime log API. The package references FND_ORACLE_USERID, FND_PRODUCT_GROUPS, FND_PRODUCT_INSTALLATIONS, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES and FND_RESPONSIBILITY to resolve the active user, installation and responsibility context, and ALL_OBJECTS to verify whether SLS objects already exist before creating or dropping them.

Usage Notes

IGI_SLS_SECURITY_PKG is typically invoked from IGI SLS security administration forms and from concurrent programs that maintain the SLS security repository after responsibility, group or secured-table changes. It is also called by custom code that needs to apply or refresh SLS security. Because the package performs DDL through CREATE_DROP_SLS_OBJECTS and REFRESH_SLS_OBJECTS, it must run under the APPS schema with appropriate privileges. No other packages reference it (Referenced by 0), confirming it is a top-level maintenance API. The CLEANUP_DATA routine is generally scheduled as part of housekeeping to purge stale allocation, group and audit rows, and should be executed during a maintenance window because it deletes security metadata.