Search Results gl_access_sets

The GL_ACCESS_SETS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for defining and managing data access control within the General Ledger (GL) module. It serves as the foundation for implementing the Data Access Set (DAS) security model, which governs user access to ledger, balancing segment, and management segment values. This table is part of Oracle's robust security framework, ensuring compliance with segregation of duties (SoD) and regulatory requirements.

Purpose and Functionality

The primary purpose of the GL_ACCESS_SETS table is to store metadata about access sets, which determine the scope of financial data a user can view or modify. Each access set defines:

• Ledger Access: Specifies which ledgers a user can access.
• Balancing Segment Access: Controls access to balancing segment values (e.g., cost centers, departments).
• Management Segment Access: Restricts access to management segment values (if configured).

Access sets are assigned to responsibilities via the GL_ACCESS_SET_ASSIGNMENTS table, linking security definitions to user roles.

Key Columns in GL_ACCESS_SETS

The table includes several important columns that define access set properties:

• ACCESS_SET_ID: Primary key, uniquely identifying each access set.
• NAME: User-defined name of the access set (e.g., "US_Ledgers_Read_Only").
• SECURITY_SEGMENT_CODE: Indicates whether security applies to balancing ('B'), management ('M'), or both ('A') segments.
• CHART_OF_ACCOUNTS_ID: References the chart of accounts structure.
• PERIOD_SET_NAME: Associates the access set with a calendar.
• DEFAULT_LEDGER_ID: Specifies the default ledger for the access set.
• STATUS: Active ('A') or inactive ('I') status flag.

Integration with Other Modules

The GL_ACCESS_SETS table integrates with multiple Oracle EBS components:

• Subledger Accounting (SLA): Ensures SLA rules respect GL access restrictions.
• Financial Reporting: Limits report data based on assigned access sets.
• Multi-Org Access Control (MOAC): Works in tandem with MOAC to enforce data security across operating units.

Implementation Considerations

When configuring access sets in Oracle EBS 12.1.1 or 12.2.2:

• Hierarchy: Access sets follow a hierarchical model where more restrictive definitions override broader ones.
• Performance: Complex access set definitions with numerous ledger/segment restrictions may impact query performance.
• Audit: The table's data is critical for SOX and financial audits, as it documents who can access what data.

Technical Details

The table resides in the APPS schema and is part of the General Ledger product family. In EBS 12.2.2, it may leverage Oracle's Online Patching (ADOP) framework for maintenance. Typical size ranges from a few dozen to several hundred rows, depending on organizational complexity.

Best Practices

• Maintain a naming convention that reflects access set purpose (e.g., "Region_EU_Write").
• Regularly review inactive access sets to purge obsolete entries.
• Document access set assignments in a controlled manner for audit trails.

The GL_ACCESS_SETS table remains a cornerstone of Oracle EBS financial security, enabling granular control over financial data visibility while supporting complex, multi-entity organizational structures.