User PV Form? Risk Description / Comments Recommended Setting

(1)

User Profile Name

Risk Rating Category

User PV

Form? Risk Description / Comments Recommended Setting

Subject

to CM? Who Approves?

Personalize Self-Service Defn High ITGCs No

If this profile option is set to Yes, the user can perform "Admin Personalization" for OA Framework-based pages.

No at Site level; Yes at User level when approved through the change management process to migrate a personalization. Yes

Hide Diagnostics menu entry High ITGCs No

These profiles control the Help->Diagnostics->Custom Code-> Personalize choice on the pull-down menu of Oracle Forms-based forms. The default value of FND_HIDE_DIAGNOSTICS (Hide Diagnostics menu entry) is Yes, the Diagnostics menu entry is hidden. If it is set to No, the Diagnostics menu entry is visible to the user. If DIAGNOSTICS (Utilities:Diagnostics) is set to Yes, then users can automatically use these features.

Yes at Site level; Yes at any level in Production - should not be allowed at any level in Production even if approved by

management Yes

Utilities:Diagnostics High ITGCs No

If Utilities:Diagnostics is set to No, then users must enter the password for the AP schema to use the Diagnostics features. If it is set to Yes, then the user is able to change data directly at the database level for the data to which they have access. This could corrupt the data and invalidate your support agreement with Oracle. Having access to this is like the equivalent of having the 'APPS' password as it provides DML access to database. Having access to this functionality also allows a user to turn off Custom Code (such as personalizations) that may be used to

No at Site level; No at any level in Production - should not be allowed at any level in Production even if approved by

management Yes DBAs

GL Ledger ID N/A ITGCs No This is derived by the system, not set directly, when the GL Set of Books Name is As needed Yes

GL Ledger Name High ITGCs No

Typically set at the Responsibility level for GL related responsibilities to identify

the Ledger or Book to which the responsibility relates. As needed Yes

MO: Default Operating Unit Medium ITGCs Yes

Determines the default operating unit when a user accesses a form that is MOAC enabled. This is used in conjunction with the MO: Security Profile profile option where MOAC is enabled

As needed. Sometimes this is set at the Site level for one Global Security Profile then overridden at the Responsibility level for other responsibilities not using that Global Security Profile Yes

MO: Operating Unit High ITGCs No

Determines to which operating unit a responsibility can access data (update or inquiry)

As needed. Sometimes this is set at the Site level for one Operating Unit then overridden at the Responsibility level for other responsibilities not using that Operating Unit Yes

MO: Security Profile High ITGCs No

Determines to which global security profile (MOAC) a responsibility can access data (update or inquiry)

Typically set at the responsibility level. Sometimes this is set at the Site level for one Global Security Profile then overridden at the Responsibility level for other responsibilities not using that

Global Security Profile Yes

HR:User Type High HR / PAY No

Limits field access on windows shared between Oracle Human Resources and Oracle Payroll. If you do not use Oracle Payroll, it must be set to HR User for all responsibilities. If you do use Oracle Payroll, you can give each Responsibility one of the following user types, depending on the work role of the holders of the

responsibility: HR User, HR with Payroll User, Payroll User As needed per policy Yes

Signon Password Case High ITGCs No

Critical password configuration - determines whether or not the password is case sensitive

Should be set at the Site level and not overridden at any other level. Setting should be consistent with your corporate policy. Yes

Signon Password Failure Limit High ITGCs No

Critical password configuration - determines the number of attempts a user can try to enter their password before the account gets locked

Should be set at the Site level and not overridden at any other level. Setting should be consistent with your corporate policy. Should be set in all instances because otherwise this just invites a hacker to keep trying without the account being locked Yes

Signon Password Hard to Guess High ITGCs No

Critical password configuration - determines if the hard to guess criteria is enabled. Oracle defines a password as hard-to-guess if it follows these rules: o The password contains at least one letter and at least one number o The password does not contain repeating characters. o The password does not contain the username.

Should be set at the Site level and not overridden at any other level. Setting should be consistent with your corporate policy. To enable the highest level of security set this to YES Yes

Signon Password Length High ITGCs No Critical password configuration - determines minimum length of the password

Should be set at the Site level and not overridden at any other level. Setting should be consistent with your corporate policy

and be at least five characters Yes

Signon Password No Reuse High ITGCs No

Critical password configuration - determine the number of days before a password can be reused

Signon Password Custom High ITGCs No

Critical password configuration - is used if you want to define your own password scheme (validated by custom Java code) in a custom Java class. This would be used if you have a more advanced and complex password value requirement that is not supported by the standard profile options

Sign-On:Audit Level High ITGCs No

This determines the level of Sign-On auditing. Levels are User, Responsibility, and Form. If this is enabled, the system tracks basic sign-on information for each session.

Should be set to "Form" to capture maximum amount of audit data. We recommend you work with your DBAs and auditors to determine the purge criteria. The DBAs will want to purge more often than your auditors or Corporate Governance group would.

A balance needs to be reached. Yes

Local Login Mask High ITGCs Yes Enables Self-Service Password Reset functionality

Sign-On:Notification High ITGCs Yes

Critical password configuration - determines whether or not users are notified when there have been failed login attempts for their user account

FND: Developer Mode High ITGCs Yes Enables logging

No at the Site level, set at the User or Responsibility on an as

needed, but temporary basis. Yes

FND: Debug Log Enabled High ITGCs No

Generally only set to Yes only for debugging as this impact the performance. See more at - How to Collect an FND Diagnostics Trace (aka FND:Debug) [ID 372209.1]

No at all levels other than when debugging an issue in Production. Ideally debugging would be done in a clone of

Production rather than Production. Yes

FND: Debug Log Level High ITGCs No

Determines how much information is collected when the FND: Debug Log Enabled is set to "YES". Options are:

LEVEL_UNEXPECTED : Internal Level Id is 6 LEVEL_ERROR : Internal Level Id is 5 LEVEL_EXCEPTION : Internal Level Id is 4 LEVEL_EVENT : Internal Level Id is 3 LEVEL_PROCEDURE : Internal Level Id is 2

LEVEL_STATEMENT : Internal Level Id is 1 Depends on your policy Yes

EGO: User Organization Context High ITGCs No

This option stores the organization selected by a user. When the user logs in to the system, the system retrieves the organization from this option and uses it for the session. So this is set dynamically as the user changes organizations and, therefore, should not be set statically.

Probably not wise to set this manually rather allow the system

(2)

PV

Subject

GLDI: Journal Source High Finl Close No

Determines the default source in ADI / Web ADI. If this is wrong or is changed to a source that doesn't require journal approval, it would allow a user to enter a journal entry that is not subject to the journal approval workflow. This may result in a control violation depending on how your organization's journal entry and approval controls are defined.

Typically this is set to Spreadsheet at the Site level and should

not be overridden at any other level. Yes

GLDI: Force Journal to Balance Medium Finl Close No Determines whether JE's uploaded from ADI must balance Yes Yes GL process lead

GL: Journal Review Required High Finl Close Yes

Determines if Allocation journals that are a generated from the Mass Allocation process (formulas) are subject to the journal approval workflow process

Typically this is set to YES at the Site level, but it depends on how the journal entry and approval controls are defined. This should not be overridden at any other level (Application,

Responsibility) Yes

Journals: Allow Preparer Approval High Finl Close No

Determines if the preparer of a journal entry can approve their own journal entry. The risk is determined by the journal entry and approval controls. If all journal entries should be subject to a secondary approval, then not setting this properly would allow a user to enter and approve their own journal and result in a violation of your internal controls

Typically this is set to NO at the Site level, but it depends on how the journal entry and approval controls are defined. This should not be overridden at any other level (Application, Responsibility) Yes

Journals: Find Approver Method High Finl Close No

This determines how an approval will be sought when the journal approval workflow is required. Options are: Go Up Management Chain, Go Direct, and One Stop Then Go Direct. It needs to be set according to how you policy expects the approval to be routed. The risk is that the configuration would not support the policy.

No specific recommendation. Make sure your policy and this

configuration are consistent / they match. Yes

ICX:Session Timeout Medium ITGCs No

This profile option determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled. Note that disabled does not mean terminated or killed. The user is provided the opportunity to re-authenticate and re-enable their timed-out session. If the re-authentication is successful, the disabled session is re-enabled and no work is lost. Otherwise, the

session is terminated without saving pending work. Depends on your policy Yes

GL Account Analysis Report: Enable Segment Value Security on

Beginning/Ending Balances High Finl Close No

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. Yes Yes

FSG: Enforce Segment Value Security High Finl Close No

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 might run.

No: Defined security rules are not used for FSG reporting purposes. Yes at the Site level Yes

FND: Personalization Region Link

Enabled High ITGCs Yes Used to enable Oracle Apps Personalization link on JSP pages.

Personalizations should go through the change management process and access only granted when there is an approved change request. Therefore, we'd only expect this to be granted on a temporary basis rather than a user having access to it

permanently in Production. Yes

WF: GUEST Access to Notification High ITGCs No

Enables approval of workflow approvals via email - does not require the user to authenticate with their credentials in order to make the approval.

From Oracle Users Guide: This profile option helps control whether users must log in before they can access the Notification Details Web page from a notification. To enable guest access, which does not require an individual login, you must both set this profile option to Enabled and create a grant assigning the "Workflow Guest

User permission set" to the GUEST user. Depends on your policy Yes

JTF_INACTIVE_SESSION_TIMEOUT High ITGCs Yes

This profile option affects CRM-based products only, and serves the same purpose as the ICX:Session Timeout profile. This profile option exists for legacy reasons,

(3)

User Profile Name Rating Category Form? Risk Description / Comments Recommended Setting to CM? Who Approves?

WF: Notification Reassign Mode High ITGCs Yes

This profile option controls how users can reassign notifications. See: Setting the WF: Notification Reassign Mode Profile Option.

Delegate - Provides users access to delegate a notification to another user while still retaining ownership of the notification.

Transfer - Provides users access to transfer complete ownership of a notification to another user.

Reassign - Provides users access to both the Delegate and Transfer reassign modes. This setting is the default value for this profile option.

Depends on your policy. Generally most organizations set this to Transfer so that the person to whom the notification is transferred needs to have proper authority to respond to the

workflow notification. Yes

WF: Vacation Rules - Allow All High ITGCs No

Set the profile option to Enabled if you want the "All" option to appear in the list of item types for vacation rules, or to Disabled if you do not want the "All" option to appear. If you choose Disabled, then users must always specify the item type to which a vacation rule applies. The WF: Vacation Rules - Allow All profile option

must be set at site level. The default value is Enabled. Depends on your policy Yes

Journals: Override Reversal Method High Finl Close No Yes

Journals: Allow Posting During Journal Entry (post button on Journals

Entry form) (Rel 11.0 and earlier) High Finl Close No Yes

GLDI: Analysis Wizard Privileges

(allow use of Analysis Wizard) High Finl Close No Yes

GL/MRC: Post Reporting Journals

Automatically High Finl Close No (if using MRC) Yes

ADI: Use Function Security High Finl Close No Yes

PO: Allow Auto-generate Sourcing

Rules High

Procure to

Pay No Yes

PO: Allow Autocreation of Oracle

Sourcing Documents High

Procure to

Pay No Yes

PO: Allow Buyer Override in

Autocreate Find High

Procure to

Pay Yes Yes

PO: Allow Retroactive Pricing of POs High

Procure to

Pay No Yes

PO: Amount Billed Threshold

Percentage High

Procure to

Pay No Yes

PO: Automatic Document Sourcing High

Procure to

Pay No Yes

PO: Change Supplier Site High

Procure to

Pay No Yes

PO: Price Tolerance (%) for Catalog

Updates High

Procure to

Pay Yes Yes

PO: Release During ReqImport High

Procure to

Pay Yes Yes

Tax: Allow Manual Tax Lines High

Procure to

Pay No Yes

Tax: Allow Override of Customer

Exemptions High

Procure to

Pay No Yes

Tax: Allow Override of Tax Code High

Procure to

Pay No Yes

AR: Update Due Date High

Order to

Cash No Yes

AR: Allow Update Of Existing Sales

Credits High

Order to

Cash Yes Yes

AR: Cash - Allow Actions High

Order to

Cash No Yes

AR: Receipt Batch Source High

Order to

Cash Yes Yes

AR: Use Invoice Accounting For Credit

Memos High

Order to

Cash No Yes

FND: Diagnostics Medium ITGCs Yes

Enables/Disables Logging (used to collect debug information) - should only be enabled when debug process is necessary for troubleshooting. This could cause a significant amount of data to be collected unnecessarily if left enabled.

No unless needed for debugging a certain process then should only be enabled for a short period of time. Yes

AuditTrail:Activate High ITGCs No

Enables the use of the System Administrator audit trail functionality. Disabling this could disable the triggers being used to capture audit history as expected.

If not using native audit trail, this should be No, otherwise it

needs to be Yes Yes

HR:Cross Business Group High HR / PAY No

Controls whether users of some HRMS windows can see certain information for

more than one business group. Yes

HR:Cross BG Duplicate Person Check Medium HR / PAY No

Controls the duplicate person check functionality across multiple business groups in Oracle HRMS and Oracle SSHR. Set to Yes to enable the duplicate person check

functionality across business groups Yes

ICX: Limit time Medium ITGCs No

This profile option defines the maximum connection time for a connection – regardless of user activity. If 'ICX:Session Timeout' is set to NULL, then the session

will last only as long as 'ICX: Limit Time', regardless of user activity. Yes

ICX: Limit connect Medium ITGCs No

This profile option defines the maximum number of connection requests a user can make in a single session. Note that other EBS internal checks will generate connection requests during a user session, so it is not just user activity that can

increment the count. Yes

FND: Enable Cancel Query High ITGCs No

This allows a user to cancel a query submitted. Enabling this could cause

performance issues. Discuss with DBAs - generally set to No Yes

POR: Days Needed By Medium

Procure to

Pay Yes

Indicates the default number of days until the requester needs the order. This value is used to calculate the need by date. The risk would be a need by date that

(4)

PV

Subject

PO: Default Need-By Time Medium

Procure to

Pay Yes

Indicates that the time is defaulted to need-by dates in purchase order. This value is used to calculate the time on the need by date. The risk would be a need by

date that too long and the item not being received on time. Yes

Concurrent:Report Access Level Medium ITGCs No

This profile determines access privileges to report output files and log files generated by a concurrent program. When it is set to YES which is typically at the Responsibility level, then others with the same Responsibility can see the output and log files of other users using the same Responsibility. I believe this is only

relevant prior to R12. As per policy Yes

Initialization SQL Statement - Custom High ITGCs No

Using the profile option Initialization SQL Statement - Custom, you can add site-specific initialization code, such as optimizer settings. This profile value must be a valid SQL statement, or a PL/SQL block for more than one statement, that is to be executed once at the startup of every database session.

This could be used for a variety of purposes causing issues and any use of it should be peer-reviewed and be subject to the

change management process. Yes

Initialization SQL Statement - Oracle High ITGCs No

Per Oracle in its "Oracle E-Business Suite System Administrator's Guide - Configuration". This profile option is used by Oracle E-Business Suite. This profile option and its value settings are delivered as seed data, and must not be

modified. Never make any change to the default value per Oracle. Yes

Create Seeded Personalizations High ITGCs Yes Used to enable Oracle Apps Personalization link on JSP pages.

FND: Personalization Seeding Mode High ITGCs Yes Used to enable Oracle Apps Personalization link on JSP pages.

HR: Enable User Personalization High ITGCs No Used to enable Oracle Apps Personalization link on JSP pages.

POR: Require Blind Receiving High

Procure to

Pay No

If this is set, and this setting matches the PO setting defaulting in the Receiving Controls form, the quantities are hidden when entering a receipt. If this is set incorrectly it could cause a deviation from control design if blind receiving is

expected. As per policy Yes

ICX:Session Timeout High ITGCs No

This profile option determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled. Note that disabled does not mean terminated or killed. The user is provided the opportunity to re-authenticate and re-enable their timed-out session. If the re-authentication is successful, the disabled session is re-enabled and no work is lost. Otherwise, the session is terminated without saving pending work. This functionality is available via Patch 2012308 (included in 11.5.7, FND.E).

Per Solution Beacon recommendations -- Note: Setting the profile value to greater than 30 minutes can drain the JVM resources and cause ‘out of memory’ errors.

As per policy Yes

Responsibility Trust Level High ITGCs No

The main significance of Responsibility Trust Level is to make a responsibility accessible from an external web tier when this profile option is set at responsibility level equal to “External”. Only those responsibilities that have this profile option against them will be accessible from External Middle tiers. The risk is that responsibilities that should not be externally facing are set to be.

These profile options should be set according to policy how your technical architecture should be configured. This is typically set up at the Responsibility level only for the externally facing Responsibility(ies). This should NOT be set at the Site level. Yes

Node Trust Level High ITGCs No

If this profile option is set to EXTERNAL for any server, the server is external facing - that is it can be accessed via a url outside the firewall. The risk is that servers that should not be externally facing are set to EXTERNAL making a public url available on the world wide web.

These profile options should be set according to policy how your technical architecture should be configured. Yes

POS: External Responsibility Flag High

Procure to

Pay No

The main significance of this profile option is to make a responsibility accessible from an external web tier. This is specific to the iSupplier module when this profile option is set at responsibility level set to "Yes". Only those responsibilities that have this profile option against them will be accessible from External Middle tiers. The risk is that responsibilities that should not be externally facing are set to be.

These profile options should be set according to policy how your technical architecture should be configured. This is typically set up at the Responsibility level only for the externally facing Responsibility(ies). This should NOT be set at the Site level. Yes

DateTrack:Date Security High HR / PAY No

Controls the way users can change their effective date: All (users can change to any date), Past (users can change to dates in the past only), Present(users cannot change their effective date), Future (users can change to dates in the future only).

The risk is this is set contrary to what your organization's policy would require. Set according to your organization's policy Yes

DateTrack:Reminder Medium HR / PAY Yes

Determines whether the Decision window appears when a date tracked window opens: Always (the window always appears), Never (the window never appears), Not Today (the window appears only if the effective date is not the system date). The risk is this is set contrary to what your organization's policy

would require. Set according to your organization's policy Yes

HR:Query Only Mode High HR / PAY No

Restricts access to view-only for all HR and Payroll forms on a menu. The risk is the is NOT set or is removed from the User or Responsibility that is intended to be query only - giving one or more users the ability to maintain HR data that they should only be able to view.

Set according to your organization's policy for a given user or responsibility. This should NOT be set at the Application or Site

(5)

User Profile Name Rating Category Form? Risk Description / Comments Recommended Setting to CM? Who Approves?

HR: Security Profile High ITGCs No

This profile option is used to restrict access to the organizations, positions, and payrolls defined in the security profile. This option is seeded at Site level with the view-all security profile created for the Startup Business Group. Typically this is set at the responsibility level for each custom responsibility that needs access to a subset of organizations, positions, and payrolls to override the Site level setting where security is needed to be more granular.

If you use Standard HRMS security you must set up the HR: Security Profile option for each responsibility.

If you use Security Groups Enabled security you must not set up the HR: Security Profile option. This is set up automatically when you assign security profiles using the Assign Security Profile window. You must only change the HR: Security Profile option by assigning a different security profile to a responsibility using the Assign Security Profile window.

The risk is setting wrong security profile to a responsibility or inappropriately setting it at the Site level that could allow one or more users to have access to

data to which they shouldn't. Set according to your organization's policy Yes

HR:Business Group High ITGCs No

This profile option determines the business group linked to a responsibility. This option is used online to control access to records that are not related to organization, position, or payroll. The Setup Business Group is defaulted at Site level. It is view only.

If you use Standard HRMS security this option is automatically set up when you enter the HR: Security Profile profile option, except in cases where you are using a global security profile (that is, a security profile that does not specify a business group). In this case, you must specifically set up this option for each responsibility. If you use Security Groups Enabled security, this option is not user-configurable. The business group is determined when you create a security profile assignment using the Assign Security Profile window.

The risk is setting wrong business group to a responsibility or inappropriately setting it at the Site level that could allow one or more users to have access to

data to which they shouldn't. Set according to your organization's policy Yes

GL: Debug Mode ITGCs Yes

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.

No at all levels other than when debugging an issue in Production. Ideally debugging would be done in a clone of

Production rather than Production. Yes

JTF_PROFILE_DEFAULT_RESPONSIBILI

TY Low ITGCs ?

Specifies the default responsibility for the Site Administration UI. Set to 21819 for the iStore Administrator responsibility. Set at iStore application level only. May be higher risk if you are using iStore and this is set manually to the wrong responsibility. Often this is set dynamically by the system 'behind the scenes.'

JTF_PROFILE_DEFAULT_APPLICATION Low ITGCs ?

Specifies the default application ID. May be higher risk if you are using iStore and this is set manually to the wrong responsibility. Often this is set dynamically by the system 'behind the scenes.'

IBE: Preferred Shipping Method Low ? ?

ICX: Language Low ITGCs ? Determines the default session language.

ICX: Territory Low ITGCs ?

Printer:Type Low ITGCs ?

Printer Low ITGCs ?

ICX: Date format mask Low ITGCs ?

Determines the date format mask to use. The American English default is DD-MON-RRRR, for example, 12-NOV-2002.

GL Journals: Last Find Window State Low ITGCs ?

JTF_PROFILE_DEFAULT_CURRENCY Low ITGCs ?

Viewer: Text Low ITGCs ?

Sets the display viewer for text report output. Valid values are Browser and Report Viewer.

Viewer: Application for HTML Low ITGCs ?

These profile options determine the applications a user will use to view reports in the given output formats. For example, you could set Viewer: Application for Text to 'application/word' to view a Text report in Microsoft Word.

Viewer: Application for XML Low ITGCs ?

Viewer: Application for Text Low ITGCs ?

If your system administrator has registered other applications for viewing text output, select the application from the list of values. The profile option Viewer: Text must be set to Browser to use this profile option.

Viewer: Application for PCL ITGCs ?

Viewer: Application for PDF Low ITGCs ?

Those profile options that have negligible risk in Production and may not be need to be subject to the Change

Management process:

(6)

PV

Subject

Viewer: Application for Postscript Low ITGCs ?

Export MIME type Low ITGCs ? Determines how files are exported - such as text/tab-separated-values

Applications Start page Low ITGCs ?

ICX: Preferred Currency Low ITGCs ?

This profile determines in which currency a user will see the currency number in the UI. For example, the source currency number might be stored in database such as 10.00 as US Dollar (USD), but the displayed currency number is based on the currency set in this profile option such as 1,200 as Japanese Yen (JPY). ICX: Date language ITGCs ? Determines the date language to use. This impacts the default date format mask.

ICX: Numeric characters Low ITGCs ?

Enter the preferred decimal and group separators you want to display for numbers. For example, if you specify .. as the value for this profile option, you indicate that the decimal separator is a period and the group separator is a comma. When set to blank, the decimal and group separators are obtained from the nls_numeric_parameters setting in the database.

Default Country Low ITGCs ?

This is the default source for the Country field for all address zones and is used by the Flexible Address Formats feature, the Flexible Bank Structures feature and the Tax Registration Number and Taxpayer ID validation routines. The profile can be set to any valid country listed in the Maintain Countries and Territories form and can be set to a different value for each user.

Currency:Thousands Separator Low ITGCs ?

You can separate your currency amounts in thousands by placing a thousands separator. For example, one million appears as 1,000,000.

Currency:Positive Format Low ITGCs ?

You can use different formats to identify positive currency values. The default condition is no special identifier.

Currency:Negative Format Low ITGCs ?

You can use different formats to identify negative currency. The default identifier is a hyphen ( - ) preceding the currency amount, as in "-xxx". Other options: Angle brackets < > < xxx >

Trailing hyphen xxx -Parentheses ( ) ( xxx ) Square Brackets [ ] [ xxx ]

Currency:Mixed Precision Low ITGCs ?

Use Mixed Currency Precision to specify how many spaces are available to the right of the decimal point when displaying numbers representing different currencies. Normally, currency numbers are right-justified.

Viewer:Default Font Size Low ITGCs ?

Using this new profile option, you can set the default font size used when you display report output in the Report Viewer. The valid values for this option are 6, 8, 10, 12, and 14.