During implementation, set a value for each Subledger Accounting profile option to specify how Subledger Accounting controls access to and processes data.
See: Setting User Profile Options, Oracle Applications System Administrator's Guide - Maintenance
Profile options are grouped into one or more profile option categories enabling you to view only the profile options that pertain to your application or function.
Subledger Accounting Categories
Subledger Accounting Profile Options
This section describes the profile options by category.
The tables in this section provide profile option information as follows:
The Default column displays the default profile option value in italics or No Default if none exists.
The User Access column indicates whether you can view or update the profile option.
The System Administration: User, Responsibility, Application, and Site columns indicate at which levels the system administrator can update these profile options.
The key for these tables is:
Update: You can update the profile option.
View Only: You can view the profile option but cannot change it.
No Access: You cannot view or change the profile option value.
This category includes profile options related to the Accounting Methods Builder (AMB).
| Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
|---|---|---|---|---|---|---|
| SLA: Accounting Methods Builder Context | Default | View Only | Update | Update | Update | Update |
This profile option controls the value for an internal context code associated with each application accounting definition and each of its assigned components, such as journal line types and account derivation rules.
Most AMB components are striped by a context. Assign a different value for the SLA: Accounting Methods Builder Context profile option to work on your own copy of components and perform changes.
Define additional AMB Context profile values as a Subledger Accounting lookup, XLA_AMB_CONTEXT_TYPE.
This category includes profile options that enable debugging and diagnostic features.
| Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
|---|---|---|---|---|---|---|
| SLA: Display Timestamp on Trace | No | View Only | Update | Update | Update | Update |
| SLA: Enable Diagnostics | No | View Only | Update | Update | Update | Update |
| SLA: Enable PL/SQL Profiler | No | View Only | Update | Update | Update | Update |
| SLA: Enable Trace | No | View Only | Update | Update | Update | Update |
| SLA: Enable SQL Trace | No | View Only | Update | Update | Update | Update |
| SLA: Enable SRS Log/Output | Yes | View Only | Update | Update | Update | Update |
| SLA: Flush Trace File | No | View Only | Update | Update | Update | Update |
| SLA: Oracle Forms Trace Mode | File | View Only | Update | Update | Update | Update |
| SLA: SRS Trace Mode | Tracer | View Only | Update | Update | Update | Update |
| SLA: Trace File Override Directory | No Default | View Only | Update | Update | Update | Update |
| SLA: Trace File Override Filename | No Default | View Only | Update | Update | Update | Update |
| SLA: Trace Level | 100 | View Only | Update | Update | Update | Update |
| SLA: Trace Timeout | 600 | View Only | Update | Update | Update | Update |
This profile option displays timestamps on the trace.
This profile option controls whether diagnostic information is gathered by the Create Accounting program.
If the FND: Debug Log Enabled profile option is enabled, then the diagnostic framework information is also available in the Oracle Applications system logs page.
This profile option enables the PL/SQL profiler.
This profile option enables the Subledger Accounting trace mode.
This profile option enables the SQL trace. The possible values are Yes or No.
This profile option controls whether concurrent programs will generate a log or output file.
This profile option controls whether the trace information is sent to the trace file immediately.
This profile option indicates where the debug information provided by the forms is printed. The possible values are AF Log and File.
This profile option is set by Subledger Accounting concurrent programs. It indicates where the debug information provided by the concurrent programs is printed. The possible values are AF File and Logfile.
This profile option designates the directory for the trace file.
This profile option designates the trace file name.
This profile option controls the level of detail for the trace.
This profile option controls the time a program should wait for acknowledgement from the trace engine.
This category includes profile options set up to run the application.
| Profile Option | Default | User Access | System Administration: User | System Administration: Responsibility | System Administration: Application | System Administration: Site |
|---|---|---|---|---|---|---|
| SLA: Disable Journal Import | No | No Access | View Only | View Only | View Only | Update |
| SLA: Initial Date for Historical Upgrade | No Access | View Only | View Only | View Only | Update |
This profile option controls whether subledger journal entries are imported to General Ledger.
See: Create Accounting Program
This profile option initiates the Historical Upgrade on the specified date.
This category includes profile options related to security.
| 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.