Search Results get_mrc_mls_schemanames

Overview

IGI_SLS_SECURITY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API type. The acronym "SLS" references the Secure Library System functionality delivered by the Oracle Financials for EMEA product family, historically derived from the IGI (Global Accounting Engine / Financials Intelligence) module set. The package administers row-level and group-level security on the SLS data model, controlling which responsibilities and users may access specific SLS allocation and group records.

The package operates with AUTHID CURRENT_USER, meaning privilege resolution honours the invoking schema rather than the defining APPS schema. This design allows the package to execute DDL and DML operations across multiple schemas, notably a multi-lingual (MLS) schema and a multi-reporting-currency (MRC) schema, whose names are resolved dynamically at runtime.

Its responsibilities include creating and dropping SLS security objects, refreshing those objects, populating group allocations, consolidating groups, applying security rules, and securing pre-existing data — the operation surfaced by the search term "secure_existing_data".

Key Procedures and Functions

• WRITE_TO_LOG — Diagnostic utility that records messages to a log destination at a caller-specified severity level.
• GET_MRC_MLS_SCHEMANAMES — Resolves and returns the MRC and MLS schema names used by the remaining procedures, returning status through errbuf and retcode.
• CHECK_ALLOCATION_EXISTS — Boolean function that tests whether an allocation exists for a given secured table, accepting a table name drawn from IGI_SLS_SECURE_TABLES.
• CREATE_DROP_SLS_OBJECTS — Creates or drops the database objects supporting SLS security, using the MLS and MRC schema names as inputs.
• REFRESH_SLS_OBJECTS — Rebuilds or synchronises the SLS security objects against the current MLS and MRC schemas.
• POPULATE_GROUP_ALLOC — Populates the group allocation table that maps security groups to allocations.
• CLEANUP_DATA — Removes orphaned, invalid, or obsolete security assignment records.
• CONSOLIDATE_GROUPS — Merges or reconciles duplicate and overlapping group definitions.
• APPLY_SECURITY — Applies the security rules, accepting a mode parameter that governs the enforcement behaviour.
• SECURE_EXISTING_DATA — Retro-fits security onto data that predates the security configuration, accepting a security group parameter that determines which group the existing records are assigned to.

Tables Accessed

The package reads configuration and security definitions from IGI_SLS_SECURE_TABLES, IGI_SLS_ALLOCATIONS, IGI_SLS_GROUPS, IGI_SLS_CONSOLIDATE_GROUPS, and IGI_SLS_SECURITY_GROUP_ALLOC, and writes audit records to IGI_SLS_ALLOCATIONS_AUDIT, IGI_SLS_GROUPS_AUDIT, and IGI_SLS_SECURE_TABLES_AUDIT. It consults FND_ORACLE_USERID, FND_PRODUCT_GROUPS, FND_PRODUCT_INSTALLATIONS, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES, and FND_RESPONSIBILITY to resolve schema ownership, installation status, and profile-driven behaviour. ALL_OBJECTS is queried to confirm the existence of the security objects it manages.

Usage Notes

IGI_SLS_SECURITY_PKG is not referenced by any other documented package, indicating it is invoked directly by Oracle EBS application forms, concurrent programs, or customer extensions rather than through a wider internal call chain. The errbuf and retcode parameters conform to the standard concurrent program signature, so the procedures are suited to registration as concurrent executables. SECURE_EXISTING_DATA is typically executed as a one-time or on-demand remediation step after security groups have been defined, ensuring that records created before the security model was activated are assigned to an appropriate group.