AuditTrail&Concurrent

AuditTrail:Activate

You can turn AuditTrail on or off (Yes or No). The default setting is No (Off).

When you enter or update data in your forms, you change the database tables underlying the forms you see and use.

AuditTrail tracks which rows in a database table(s) were updated at what time and which user was logged in using the form(s).

• Several updates can be tracked, establishing a trail of audit data that documents the database table changes.

• AuditTrail is a feature enabled on a form-by-form basis by a developer using Oracle's Application Object Library.

• All the forms that support AuditTrail are referred to as an audit set.

• Not all forms may be enabled to support AuditTrail.

• To enable or disable AuditTrail for a particular form, you need access to Oracle Application Object Library's Application Developer responsibility.

Users cannot see nor change this profile option.This profile option is visible and updatable at the site and application levels. 

Level	Visible	Allow Update
Site	Yes	Yes
Application	Yes	Yes
Responsibility	No	No
User	No	No

The internal name for this profile option is AUDITTRAIL:ACTIVATE. 

Concurrent:Active Request Limit

You can limit the number of requests that may be run simultaneously by each user. or for every user at a site. If you do not specify a limit, no limit is imposed. Users cannot see or update this profile option.

This profile option is visible and updatable at all four levels.

NOTE: Above fig as follows.

The internal name for this profile option is CONC_REQUEST_LIMIT.

Concurrent:Attach URL

Setting this option to "Yes" causes a URL to be attached to request completion notifications. When a user submits a request, and specifies people to be notified in the Defining Completion Options region, everyone specified is sent a notification when the request completes. If this profile option is set to Yes, a URL is appended to the notification that enables them to view the request results on-line.

Only the System Administrator can update this profile option.

Users can see but not update this profile option.

This profile options is visible at all levels but can only updated at the Site level.

NOTE: Above fig as follows.

The internal name for this profile option is CONC_ATTACH_URL.

Concurrent:Collect Request Statistics

Set this profile option to "Yes" to have statistics for your runtime concurrent processes collected.

To review the statistics you must run the Purge Concurrent Request and/or Manager Data program to process the raw data and have it write the computed statistics to the FND_CONC_STAT_SUMMARY table. You can then retrieve your data from this table using SQL*PLUS or on a report by report basis using the Diagnostics window from the Requests window.

Users cannot see nor change this profile option.

This profile option is visible at all levels bu can only be updated at the Site level.

NOTE: Above fig as follows.

The internal name for this profile option is CONC_REQUEST_STAT.

Concurrent:Debug Flags

Your Oracle support representative may access this profile option to debug Transaction Managers.

Users cannot see nor change this profile option.This profile option is visible and updatable at all four levels.

NOTE: Above fig as follows.

The internal name for this profile option is CONC_DEBUG.

Concurrent:Hold Requests

You can automatically place your concurrent requests on hold when you submit them.

The default is "No". The concurrent managers run your requests according to the priority and start time specified for each. Changing this value does not affect requests you have already submitted.

"Yes" means your concurrent requests and reports are automatically placed on hold. To take requests off hold, you:

• Navigate to the Requests window to select a request

• Select the Request Control alternative region

• Uncheck the Hold check box

Users can see and update this profile option.This profile option is visible and updatable at all four levels.

NOTE: Above fig as follows.

The internal name for this profile option is CONC_HOLD. 

Concurrent:Multiple Time Zones

"Yes" sets the default value to 'Sysdate-1' for the 'Schedules Start Date' used by request submissions. Sysdate-1 ensures that you request is scheduled immediately regardless of which time zone your client session is running in. You should use this profile option when the client's session is running in a different time zone than the concurrent manager's session.

Users cannot see nor change this profile option.

This profile option is visible at all four levels and updatable at the Site level.

Level	Visible	Allow Update
Site	Yes	Yes
Application	Yes	No
Responsibility	Yes	No
User	Yes	No

The internal name for this profile option is CONC_MULTI_TZ.