This category includes profile options related to security.
Security Category
| Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
|---|---|---|---|---|---|---|
| SLA: Additional Data Access Set | No Default | View Only | Update | Update | Update | Update |
| SLA: Allow Reports Journal Source Override | No | View Only | Update | No Access | Update | Update |
| SLA: Enable Data Access Security in Subledgers | No | View Only | No Access | Update | Update | Update |
| SLA: Enable Subledger Transaction Security in GL | No | View Only | No Access | Update | Update | Update |
The SLA: Additional Data Access Set profile option, in conjunction with the GL: Data Access Set profile option, controls which ledgers and balancing or management segment values you can access when logging onto a responsibility. If SLA: Enable Data Access Security in Subledgers is enabled for the responsibility, you have access only to the ledgers and balancing or management segment values included in the data access sets assigned to the SLA: Additional Data Access Set and GL: Data Access Set profile options.
This profile option applies only to the following reports:
Open Account Balances Listing
Third Party Balances Report
Enable this option to change the Journal Source parameter during report submission. If the option is set to No, then you cannot change the value defaulted during report submission.
This profile option determines whether the General Ledger Access Set security mechanism is applied for a subledger application responsibility when viewing, reporting, or creating subledger journal entries associated with a given ledger. The General Ledger Access Set security mechanism is always applied for responsibilities associated with the General Ledger application.
The profile option enables you to combine data access security with subledger transaction security and therefore control access to subledger journal entries depending on the ledger to which they belong. For example, you can implement a Multi-Org Security Profile that allows you to create Oracle Receivables Invoices for two different operating units each associated with different ledgers but restrict drill-down from the subledger transaction to the associated subledger journal entry based upon the destination ledger contained in the Access Set.
Use this profile option to combine subledger transactions security with data access security for General Ledger responsibilities when drilling down to multi-organization enabled subledger application. Transaction security in the respective subledger application is always applied when drilling down from subledger transactions to subledger journal entries.