Skip Headers

Oracle Subledger Accounting Implementation Guide
Release 12.1
Part Number E13628-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Oracle Subledger Accounting Profile Options and Profile Option Categories

Profile Options and Profile Option Categories Overview

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

Profile Option Category and Profile Option Descriptions

This section describes the profile options by category.

The tables in this section provide profile option information as follows:

The key for these tables is:

Accounting Methods Builder Category

This category includes profile options related to the Accounting Methods Builder (AMB).

Accounting Methods Builder Category
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

SLA: Accounting Methods Builder Context

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.

Debug Category

This category includes profile options that enable debugging and diagnostic features.

Debug Category
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

SLA: Display Timestamp on Trace

This profile option displays timestamps on the trace.

SLA: Enable Diagnostics

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.

SLA: Enable PL/SQL Profiler

This profile option enables the PL/SQL profiler.

SLA: Enable Trace

This profile option enables the Subledger Accounting trace mode.

SLA: Enable SQL Trace

This profile option enables the SQL trace. The possible values are Yes or No.

SLA: Enable SRS Log/Output

This profile option controls whether concurrent programs will generate a log or output file.

SLA: Flush Trace File

This profile option controls whether the trace information is sent to the trace file immediately.

SLA: Oracle Forms Trace Mode

This profile option indicates where the debug information provided by the forms is printed. The possible values are AF Log and File.

SLA: SRS Trace Mode

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.

SLA: Trace File Override Directory

This profile option designates the directory for the trace file.

SLA: Trace File Override Filename

This profile option designates the trace file name.

SLA: Trace Level

This profile option controls the level of detail for the trace.

SLA: Trace Timeout

This profile option controls the time a program should wait for acknowledgement from the trace engine.

Deployment Category

This category includes profile options set up to run the application.

Deployment Category
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

SLA: Disable Journal Import

This profile option controls whether subledger journal entries are imported to General Ledger.

See: Create Accounting Program

SLA: Initial Date for Historical Upgrade

This profile option initiates the Historical Upgrade on the specified date.

Security Category

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

SLA: Additional Data Access Set

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.

SLA: Allow Reports Journal Source Override

This profile option applies only to the following reports:

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.

SLA: Enable Data Access Security in Subledgers

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.

SLA: Enable Subledger Transaction Security in GL

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.