Oracle Applications: GL Profile Options.

Budgetary Control Group

Assign budgetary control groups when you enable budgetary control for your ledger. Budgetary control groups include a set of options which are used to enforce budgetary control based on combinations of journal entry source and category. You can also define budgetary control options for the detail and summary accounts for which you want to enforce budgetary control.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility or user level.

Daily Rates Window: Enforce Inverse Relationship During Entry

Use this profile option to specify whether to enforce the automatic calculation of inverse exchange rates in the Daily Rates window. When the profile option is set to Yes and you enter a daily rate to convert currency A to currency B, General Ledger automatically calculates the inverse rate (currency B to A) and enters it in the adjacent column. If either rate is changed General Ledger automatically recalculates the other.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application or responsibility level.

Enter Journals: Validate Reference Date

This profile option controls whether the reference date is validated using Italian Libro Giornale rules. If this profile option is set to Yes, the value entered in the Reference Date field will be validated to ensure the date falls into an open or future enterable period.

The following values are available:

Yes: Reference date is validated.

No: Reference date is not validated.

The default value for this profile option is No.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility level, or user level.

FSG: Accounting Flexfield

Choose the General Ledger application reporting flexfield. For your General Ledger application, select the natural account as your reporting flexfield.

The default value for this profile option is account.

You cannot view this profile option at the user level. Your System Administrator must set this profile option at the site or application level.

FSG: Allow Portrait Print Style

Control the print orientation of your Financial Statement Generator reports that are less than or equal to 80 characters wide. You can print these reports in either portrait style (80 character wide) or landscape style (132 character wide). The following values are available to you:

Yes: Your General Ledger application prints reports that are less than or equal to 80 characters wide in portrait (80 character wide).

No: Your General Ledger application prints reports that are less than or equal to 80 characters wide in landscape (132 character wide).

If this profile option is not enabled, or your reports are more than 80 characters wide, your General Ledger application produces landscape style (132 character wide) or landwide style (180 character wide) reports, depending on the report character width.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

FSG: Enable Search Optimization

Enable this profile option to enhance the performance of FSG reports that include a large number of parent values, where each parent value contains a large number of child values. This profile option optimizes the search process for detail child values associated with each parent account value to allow the FSG reports to run faster.

The following values are available to you:

Yes: The FSG Performance Enhancement is applied.

No: The FSG Performance Enhancement is not applied.

You can set this profile option at the Site, Application, Responsibility, and User levels.

FSG: Enforce Segment Value Security

Control whether your defined security rules will apply to reports produced using FSG. The following values are available to you:

Yes: If security rules are defined that prevent you from accessing specific account segment values, then you cannot produce financial information for those same segment values when you run FSG reports. For example, if you are excluded from using any accounts for cost centers 100 and 200, then any balances for those same accounts will not appear on any FSG reports you run.

Note: If the profile option is set to Yes and the segment is independent, the security rule applies. If the profile option is set to Yes and the segment is dependent, the security rule does not apply.

No: Defined security rules are not used for FSG reporting purposes.

You cannot view this profile option. Your System Administrator can set this profile option at the site, application, responsibility, or user level.

FSG: Expand Parent Value

Control the expansion of parent values when requesting summary balances. The following values are available to you:

Yes: FSG uses the rollup group to determine whether to expand a parent value into its child ranges. If the parent value belongs to a rollup group, FSG does not expand the parent value into its child ranges. If the parent value does not belong to a rollup group, FSG expands the parent value into its child ranges.

No: FSG uses the summary flag associated with the flexfield assignment to determine whether to expand a parent value into its child ranges. If the summary flag is set to Yes, FSG does not expand the parent value into its child ranges. If the summary flag is set to No, FSG expands the parent value into its child ranges.

The default value for this profile option is No.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

FSG: Message Detail

Specify the level of detail in your error message log file when you request your Financial Statement Generator reports. Your General Ledger application divides error messages into the following three catalogs:

Catalog I: contains all detail memory figures, detail timings, and SQL statements which are useful for program debugging.

Catalog II: contains all file and function names, and all messages which give process information. This is useful for finding out where a process failed.

Catalog III: contains only error messages and other important messages, and therefore gives the least amount of information for program debugging.

You specify the level of detail for your error message log file by setting this profile option to one of the following values:

None: No messages.

Minimal: Catalog III messages.

Normal: Catalog II and III messages.

Full: Catalog I, II, and III messages.

The default value for this profile option is Minimal.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

GL Account Analysis Report: Enable Segment Value Security on Beginning/Ending Balances

This profile option applies segment value security rules to the beginning and ending balances of the following Account Analysis reports:

Account Analysis - (132 Char)

Account Analysis (180 Char)

Account Analysis - Foreign Currency (132 Char)

Account Analysis - Foreign Currency (180 Char)

The following values are available:

No: Segment Value Security rules will only apply to the period activity, not the beginning and ending balances of the reports listed above. Thus, the above reports will display the beginning and ending balances for any secured segment values, but hide the period activity from view.

YES: Segment Value Security rules will be applied to both the period activity and the beginning and ending balances of the reports listed above.

The default value for this profile option is No.

The System Administrator must enable the user view of this profile option and set this profile option at the site, application, or responsibility level.

GL AHM: Allow User to Modify Hierarchy

Specify whether users can use the Account Hierarchy Manager to modify and save account hierarchies.

Yes: Users can modify and save account hierarchies.

No: Users cannot modify and save account hierarchies. Users will have read-only access to view account hierarchies.

The default value for this profile option is No.

You can view this profile option at the site, application, responsibility, and user levels. This profile option can be set at the site, application, responsibility, and user levels.

GL AutoAllocation: Continue to Next Step if No Journal Created

Specify whether a Step-Down AutoAllocation process stops or continues to the next step if a journal batch is not generated by the previous step in the AutoAllocation set.

For example, assume a journal batch is not created because a step in a Step-Down AutoAllocation Set processes an account with no activity. In this case, the Step-Down AutoAllocation process stops when the profile option is set to No, or continues to the next step when set to Yes.

The following options are available:

Yes: The Step-Down AutoAllocation process will continue to the next step.

No: The Step-Down AutoAllocation process will not continue to the next step.

The default value for this profile option is No.

This profile option can be set at the site, application, responsibility, and user levels.

GL Consolidation: Cross Instance Workflow Notification Contact

When a cross instance data transfer is complete, this profile option allows you to activate a workflow process that sends an e-mail containing transfer results to a designated user on the target instance.

In the System Profile Values window in the source instance, query this profile option then enter a user name in the Responsibility, Application, or Site fields.

Ensure the user you defined has an e-mail address entered in the Users window on the target instance.

The default value for this profile option has no user defined.

You can set this profile option at the responsibility, application, or site level.

GL Consolidation: Preserve Journal Batching

Background: This profile option complements the Global Accounting Dual Posting solution by allowing you to preserve journal details transferred from the source ledger to the target ledger during consolidation.

This profile option can also work in conjunction with the profile options GL Consolidation: Exclude Journal Category During Transfer and GL Consolidation: Preserve Journal Effective Date.

Set this profile option to Yes to:

Retain originating journal and batch groupings from the source ledger to the target ledger.

Preserve up to 50 characters of the original batch name plus batch ID in the source ledger to the target ledger.

Preserve up to 25 characters of the original journal name and journal ID from the source ledger to the target ledger.

Retain the batch and journal header descriptions from the source ledger to the target ledger.

Preserve the category name of the journal in the source ledger to the journal in the target ledger.

Preserve the Reference Date entered in the Journals window.

The default value for this profile option is No.

The System Administrator must set this profile option at the Site or Responsibility level. If you set the profile option at the responsibility level to preserve the journal batches and header details, that responsibility must be the same responsibility from which you initiate the consolidation transfer.

GL Consolidation: Preserve Journal Effective Date

This profile option instructs General Ledger how to handle the effective date of the consolidation journal generated under the Transaction method of consolidation.

The following options are available:

Yes: The effective date of the individual journal being consolidated will be preserved in the generated consolidation journal. This profile option setting has to be used in conjunction with the profile option GL Consolidation: Preserve Journal Batching. This second profile must also be set to Yes to preserve the consolidation journal effective date.

No: The effective date of the generated consolidation journal is based on the target consolidation period for the parent ledger.

The default value for this profile option is No.

GL Consolidation: Separate Rows for Debit and Credit Account Balances in Consolidation Journal

This profile option controls whether a consolidation or elimination journal is created with the debit and credit account balances in separate journal lines, or with the debit and credit account balances in a single journal line.

Consolidation program and Elimination program will generate journals with separate lines for debit and credit account balances if the profile option is set to Yes. When the profile option has no value, or if the value is set to No, then the journals that are generated by the respective programs may contain lines that have both debit and credit balances.

The default value for this profile option is No.

Your System Administrator must set this profile option at the site or responsibility level.

GL Daily Rates: Cross Rates Override

The GL Daily Rates: Cross Rates Override profile option governs the behavior of generated cross rates according to the table below.

GL Daily Rates: Cross Rates Override profile option

Value	Insert/Update	Delete
User Entered Rate Overrides	A user-entered rate can override a system generated rate, if one already exists.	System generated cross rates can be deleted by the user.
System Generated Rate Overrides	System generated rate can override a user entered rate, if one already exists.	User defined rates that fall within the cross rate definition set may be deleted by the cross rate generation program. System generated rates cannot be deleted by the user.
No Overrides	The first defined rate, whether it be user entered or system generated, remains.	System generated cross rates are never deleted but overwritten by the same method used to create the cross rates. User can delete user created rates.

The default value for this profile option is User Entered Rate Overrides.

The system administrator must set this profile option at the site, application, responsibility, or user levels.

GL Journal Import: Separate Journals by Accounting Date

Specify how Journal Import will group journal lines by accounting date. The following values are available to you:

Yes: Journal Import will always place journal lines with different accounting dates into separate journals.

No: Journals Import will group all journal lines with different accounting dates that fall into the same period into the same journal, unless average balancing processing is enabled for the ledger.

The default value for this profile option is No.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility, or user level.

GL Ledger ID

This profile option displays the current Ledger ID of the ledger that is assigned to the GL Ledger Name profile option when you are in the System Administrator responsibility.

You cannot change the value of this profile option. Instead, you set the profile option GL Ledger Name and the system automatically determines and displays the value for GL Ledger ID.

GL Ledger Name

If using Oracle Subledgers whose menus contain General Ledger windows that require data access set information, you must assign the appropriate ledger to this profile option for each subledger application or responsibility. This profile option controls the ledger that each subledger will use for transaction processing.

The ledger assigned to the GL Ledger Name profile option will automatically be assigned to the GL: Data Access Set profile option. You can change the default assignment made to the GL: Data Access Set profile option if you want to access more ledgers in General Ledger. However, any changes made to the GL Ledger Name profile option will automatically be applied to the GL: Data Access Set profile option.

You cannot view this profile option at the user level. Your System Administrator can set this profile option at the site, application or responsibility level.

GL Revaluation: Days to Roll Forward Daily Rates

If a revaluation rate is not defined for a specified revaluation rate date, the revaluation program will search prior days to find a rate, up to the value set for this profile option. The revaluation process completes with a warning and the rate used is listed on the Revaluation Execution report. This setting affects all currencies.

The default value for this profile option is 0. If, for example, you want the revaluation program to search up to 5 days prior to find a revaluation rate, set this profile option to 5. There is no maximum value.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

GL Revaluation: Tracking by Cost Center

This profile option determines whether the Revaluation process balances unrealized gain/loss using the balancing segment only, or using both the balancing and cost center segments.

If you set this profile option to Yes, you must assign the cost center segment qualifier to an accounting segment.

The default value for this profile option is No.

You can view this profile option at the User level. Your System Administrator can set this profile option at the site, application, or responsibility level.

GL Revaluation: Use Primary Currency from Source Ledger to Create Entries in Reporting Currency

Specify the method of revaluation for the reporting currency. The following values are available to you:

Yes: The Revaluation program will use the source ledger currency balances to create revaluation entries for the reporting currency.

No: The Revaluation program will use the source ledger's entered currency balances to create the revaluation entries for the reporting currency.

The default value for this profile option is No.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

GL Summarization: Accounts Processed at a Time per Delete Worker

This profile option allows you to specify the number of accounts that should be processed by each worker process when you delete summary templates. For more information on setting the number of delete workers, see GL Summarization: Number of Delete Workers Required.

Example: you define 3 delete workers and specify 5,000 to have 5,000 accounts processed per delete worker. You then delete a summary template involving 20,000 accounts. Each worker will process 5,000 accounts in parallel. The first worker to complete processing will process the last group of 5,000 accounts.

The default value for this profile option is 5,000.

The System Administrator must enable the user view of this profile option and set this profile option at the site, application, or responsibility level.

GL Summarization: Number of Delete Workers Required

This profile option improves system performance when deleting summary templates. Rather than process records sequentially, this profile option enables General Ledger to process summary templates in parallel. Specify the number of parallel processes you want by specifying a value from 1 to 30.

The default value for this profile option is 3.

The System Administrator must enable the user view of this profile option and set this profile option at the site, application, or responsibility level.

GL Summarization: Rows Deleted Per Commit

This profile option allows you to control how many rows are deleted in a balance table per worker when you delete a summary template. This setting impacts your ability to rollback the affected data should the delete process fail.

Example: You specify 3 workers to delete a summary template involving 60,000 rows. You specify each worker to process 5,000 accounts at a time and 2,500 rows deleted per commit. Should your delete process fail, these rows are not deleted.

The System Administrator must enable the user view of this profile option and set this profile option at the site, application, or responsibility level.

GL Translation: Revenue/Expense Translation Rule

This profile option lets you specify the translation method you want to use when translating revenue and expense accounts. The default setting is PTD. For more information, see: Translating Balances.

PTD: The Period-to-Date translation method is used.

YTD: The Year-to-Date translation method is used.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

GL: Archive Journal Import Data

Specify whether you want Journal Import to save your journal import data from the GL INTERFACE table to the GL INTERFACE HISTORY table at the end of each Journal Import run.

The following values are available to you:

Yes:Journal Import will save your journal import data to the GL INTERFACE HISTORY table.

No:Journal Import will not save your journal import data to the GL INTERFACE HISTORY table at the end of each successful journal import run.

Note:If you choose Yes, Journal Import will run slower.

The default value for this profile option is No.

You can view this profile option at the User level. Your System Administrator must set this profile option at the Site, Application, Responsibility, or User level.

GL: AutoAllocation Rollback Allowed

Specify whether to allow the rollback of an AutoAllocation set. You can only use rollback for GL batches. You cannot use rollback for AutoAllocation sets that contain Projects batches. The following values are available:

Yes: You can rollback AutoAllocation batches.

No: You cannot rollback AutoAllocation batches.

The default value for this profile option is Yes.

You can view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility, or user level.

GL: Data Access Set

Assign a data access set to a General Ledger responsibility. Data access sets control the ledgers, ledger sets and balancing segment values or management segment values that can be accessed by a responsibility for general ledger processing.

If you are using Oracle Subledgers, the data access set should include the ledger that is assigned to the GL Ledger Name profile option that controls ledgers used by subledger applications.

You can view this profile option at the User level. Your System Administrator can set this profile option at the Site, Application, or Responsibility level.

GL: Debug Mode

Allow features in General Ledger to run in Debug Mode where additional messages are detailed in the log file. Debug Mode operates for many General Ledger features, such as Journal Import, Posting, Translation, Revaluation, Consolidation, Recurring Journals, and Mass Allocation. The following values are available:

Yes: General Ledger will run in Debug Mode.

No: General Ledger will not run in Debug Mode.

The default value for this profile option is No.

You can view and set this profile option at the Site, Application, Responsibility, or User level.

GL: Income Statement Accounts Revaluation Rule

Use this profile option to select either period-to-date (PTD) or year-to-date (YTD) income statement account balances for revaluation. The following values are available:

PTD: Only PTD balances will be revalued for income statement accounts.

YTD: Only YTD balances will be revalued for income statement accounts.

The default value for this profile option is YTD.

You can only review this profile option at the user level. Your System Administrator can set this profile option at the site, application, or responsibility level.

GL: Journal Review Required

Specify whether a Generated Journal Batch within an AutoAllocation set needs to be reviewed (via Oracle Workflow) before posting. The following values are available:

Yes: A generated journal batch within an AutoAllocation set must be reviewed before posting.

No: A generated journal batch within an AutoAllocation set does not require review before posting.

The default value for this profile option is No.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility, or user level.

GL: Launch AutoReverse After Open Period

This profile option instructs General Ledger to launch the AutoReversal Program when a period is opened. AutoReversal will generate and post (if selected) all journals assigned a specific category. If you set this profile option to no, you can launch AutoReversal from the Submit Requests window. The following values are available:

Yes:General Ledger launches AutoReversal when a period is open.

No:General Ledger does not launch AutoReversal when a period is opened.

The default value for this profile option is Yes.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

GL: Number of Accounts in Memory

This profile option allows you to set the concurrent program controls to improve the performance of the MassAllocation and MassBudget programs. The more accounts MassAllocations/MassBudgets can hold in memory, the faster the programs will run.

To use this profile option, you should do the following:

Run the Optimizer program to create indexes on segments of your account
Determine the total amount of main memory that you want to allocate to the programs using the following formula: Size of program (Journal Import or MassAllocation/MassBudgeting) + Memory used for journal lines held in memory (Journal Import or MassAllocation/MassBudgeting) + Memory used for accounts held in memory (MassAllocation/MassBudgeting only)

If you do not enter a value for this profile option, the MassAllocation and MassBudget programs will process 2500 accounts at once. You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

GL: Number of Formulas to Validate for each MassAllocation Batch

This profile option only pertains to ledgers with average balance processing enabled. Use this profile option to specify the number of MassAllocation formulas that will be pre-validated in the Generate MassAllocation Journals form before the Run MassAllocations program is generated. The number you set for this profile option controls the number of formulas that will be randomly selected and checked for average balance processing violations, such as the calculation effective date and average balance usage parameters.

Example: You define a MassAllocation batch that includes six formulas and you specify five for this profile option. When you generate the MassAllocation batch, five of the six formulas are validated in the Generate form. If violations are found, an error message will appear and the generation program will not proceed with processing until the violations have been resolved. If they pass validation, then General Ledger will proceed to generate all of your MassAllocation journals and check for additional invalidations.

The default value for this profile option is 5. Your System Administrator can set this profile option at the site, application, or responsibility level.

GL: Number of Formulas to Validate for each Recurring Journal Batch

This profile option only pertains to ledgers with average balance processing enabled. Use this profile option to specify the number of Recurring Journal formulas that will be pre-validated in the Generate Recurring Journals form before the Recurring Journal Entry program is generated. The number you set for this profile option controls the number of formulas that will be randomly selected and checked for average balance processing violations, such as the calculation effective date and average balance usage parameters.

Example: You define a Recurring Journal batch that includes six formulas and you specify five for this profile option. When you generate the Recurring Journal batch, five of the six formulas are validated in the Generate form. If violations are found, an error message will appear and the Recurring Journal Entry program will not be generated until the violations have been resolved. If they pass validation, then General Ledger will proceed to generate your recurring journals and check for additional invalidations.

The default value for this profile option is 5. Your System Administrator can set this profile option at the site, application, or responsibility level.

GL: Number of Purge Workers

This profile option allows multiple purge processes to run in parallel to speed processing when you have large volumes of journals to purge. If one parallel purge process fails due to an error, the other processes will continue. You only repeat the purge operation for those processes that failed.

The default value for this profile option is 1.

Set this profile option equal to the number of processes you want to be able to run at the same time.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility, or user level.

GL: Number of Records to Process at Once

This profile option allows you to set the concurrent program controls to improve the performance of Journal Import, MassAllocations and MassBudgets. For example, you can speed Journal Import by increasing the number of records (journal lines) it holds in memory. By increasing concurrent program control values, you increase the amount of memory the Journal Import or MassAllocation/MassBudgeting programs can use, thereby increasing their throughput.

To use this profile option, you should do the following:

Run the Optimizer program to create indexes on segments of your account.
Determine the total amount of main memory that you want to allocate to the programs using the following formula: Size of program (Journal Import or MassAllocation/MassBudgeting) + Memory used for journal lines held in memory (Journal Import or MassAllocation/MassBudgeting) + Memory used for accounts held in memory (MassAllocation/MassBudgeting only).

If you do not enter a value for this profile option, the Journal Import, MassAllocation and MassBudget programs will process 1000 records at once. You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

GL: Owners Equity Translation Rule

Specify the rule General Ledger follows to translate owners' equity accounts when you have not entered specific historical rates or amounts. The following values are available:

PTD: The Period-to-Date rule is used to translate owners' equity accounts. For each period for which you translate owners' equity accounts, the historical rate is set to the period-average rate.

YTD: The Year-to-Date rule is used to translate owners' equity accounts. For each period for which you translate owners' equity accounts, the historical rate is set to the period-end rate.

The default value for this profile option is PTD.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

Journals: Allow Multiple Exchange Rates

Specify whether you want to allow multiple conversion rates within a journal entry. The following values are available to you:

Yes: You can override the converted amount when you enter journals.

No: You cannot override the converted amount when you enter journals.

The default value for this profile option is No.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

Journals: Allow Non-Business Day Transactions

Specify whether you want to allow posting on non-business days. Business and non-business days are defined on the Transaction Calendar. The following values are available to you:

Yes: You can post transactions on non-business days.

No: You cannot post transactions on non-business days.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility, or user level.

Journals: Allow Preparer Approval

Specify whether preparers can approve their own journal batches. The following values are available to you:

Yes: Preparers are allowed to approve journal batches that fall within their authorization limit.

No: Preparers cannot approve their own journal batches.

The default value for this profile option is No.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility or user level.

Journals: Default Category

Specify the default journal entry category. When you enter manual journal entries, the category will default to the category you specify here.

You can set this profile option at the user level. Your System Administrator can set this profile option at the site, application, responsibility or user level.

Journals: Display Inverse Rate

Specify how you enter and display conversion rates in the Enter Journals window. The following values are available to you:

Yes: You can enter and display conversion rates in the ledger currency-to-foreign currency format, that is, the rate by which you multiply a ledger currency amount to determine the foreign amount.

No: You can enter and display conversion rates in the foreign currency-to-ledger currency format, that is, the rate by which you multiply a foreign amount to determine the ledger currency amount.

The default value for this profile option is No.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

Journals: Enable Prior Period Notification

Specify whether General Ledger should notify you when you are entering a journal for a prior period. The following values are available to you:

Yes: General Ledger will display a message when you are entering a journal for a prior period. You have to confirm that this is what you want to do.

No: General Ledger will not notify you when you enter a prior period journal.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility, or user level.

Journals: Find Approver Method

Specify the default approval method for the Journal Approval process. The following values are available to you:

Go Up Management Chain: The journal batch moves up the approval hierarchy until it has been approved by an approver whose authorization limit is sufficient to allow approval. The journal batch must be approved by all intermediate approvers as well.

Go Direct: The journal batch is sent directly to the first approver in the approval hierarchy who has an authorization limit high enough to allow approval. The preparer's direct manager receives a courtesy notice.

One Stop Then Go Direct: The journal batch is first sent to the preparer's manager for approval. If further approvals are required, the journal batch is sent directly to the first approver in the approval hierarchy who has an authorization limit high enough to allow approval.

The default value for this profile option is Go Up Management Chain.

You cannot view this profile option at the user level. Your System Administrator must set this profile option at the site, application, or responsibility level.

Journals: Mix Statistical and Monetary

Choose whether to enable users to enter statistical amounts along with monetary amounts in the Enter Journals window. The following values are available to you:

Yes: You can enter statistical amounts along with monetary amounts when you enter journals. The window appears only for those accounts for which you define a statistical unit of measure.

No: You are not able to enter statistical amounts along with monetary amounts in the Enter Journals window.

The default value for this profile option is No.

You can set this profile option at the user level. Or, your System Administrator can set this profile option at the site, application, responsibility or user level.

Journals: Override Reversal Method

Specify whether users can override the default reversal method when they reverse a journal. The default reversal method is specified when you define journal categories. The following values are available to you:

Yes: Users can change the default reversal method when they are reversing journals.

No: Users cannot change the default reversal method when they are reversing journals.

You can only view this profile option at the user level. Your System Administrator must set this profile option at the site, application, responsibility, or user level.

Use Performance Module

Specify whether General Ledger concurrent programs will make use of the statistical data collected by the General Ledger Optimizer program to enhance the performance of some concurrent programs. The concurrent programs affected include Posting, Summarization, MassAllocations, Consolidation, Year End Carry Forward, Budget Range Assignments and Historical Rates Assignment.

The default value for this profile option is Yes, and we strongly advise you NOT change it unless specifically told by Oracle Customer Support.