Data Access Sets

Data access sets control which ledgers can be accessed by different responsibilities. Data access sets can also limit a user from accessing certain balancing segment values or management segment values or grant read - only or read and write access to data in a ledger. The ledgers and ledger sets assigned to a data access set must share the same chart of accounts, calendar, and period type.

You can define three types of data access sets:

You must specify one of the three types for each data access set. Once defined, you cannot alter the type. You can only add or delete ledgers/ledger sets and segment values specified in the data access set.

Oracle General Ledger automatically creates a data access set when the following occurs:

The system-generated data access set for a ledger uses the same name as the ledger. This data access set uses the Full Ledger access set type that provides full read and write access to the ledgers.

The system-generated data access set for ledger sets uses the same name as the ledger set. This data access set uses the Full Ledger access set type that provides full read and write access to all of the ledgers assigned to the ledger set.

If the level of access provided by the system - generated data access set is sufficient for your needs, you do not need to manually create a data access set; just use the one created by the system.

You only need to create your own data access sets when you want to further limit read and write access to ledgers, ledger sets, or specific balancing segment values or management segment values for a ledger or ledger set.

Full Ledger Access

Full ledger access is required to perform certain operations, such as opening and closing periods, creating summary accounts, creating budgets, and performing Mass Maintenance. Full ledger access means having full read and write access to the ledger and all of its balancing segment values or management segment values.

To obtain full ledger access, your data access set must be one of the following types:

To prevent potential errors in processing, such as not being able to open or close a ledger's periods, make sure at least one responsibility has a data access set assigned with full ledger access.

Note: Data Access Sets work with Segment Value Security Rules and Cross - Validation Rules. If you have defined Segment Value Security Rules that prevent certain responsibilities from accessing certain segment values, those rules are combined with data access set security.

For example, if you defined Segment Value Security rules to exclude Balancing Segment Value 01 and then defined data access set security that provides read-only access to values 01 - 03, the user assigned this responsibility would not be able to read segment value 01 due to the Segment Value Security rule.

Defining Your Cross - Validation Rules and Defining Segment Values.

Reporting Currencies

If you use reporting currencies, Oracle General Ledger automatically creates both of the following:

The system-generated data access set for a reporting currency uses the same name as the reporting currency. This data access set uses the Full Ledger access set type that provides full read and write access to the reporting currency.

If a ledger set is defined that includes reporting currencies (journal or subledger level), the system-generated data access set for the ledger set uses the Full Ledger access set type that provides full read and write access to all of the reporting currencies assigned to the ledger set.