NOTE 1: Each time you change any value on profile values, please click ‘SAVE’ prior to

moving to the next profile value so that configurations are saved. If not, the change in value
is not saved.
NOTE 2: Make sure the user that will replicate the issue is having a person id in Fusion (i.e.
it is an active user, linked to a person number and not an Implementation User). You will
enable the trace file for this user.

A) STEPS to enable PLSQL tracing:

(Some settings may already be configured if done before)
1) Navigation
Go to “Setup and Maintenance”
2) Setup Trace
Search: "Manage Administrator Profile Values"
Navigate to the UI by pressing on the task name itself.
Set the following profile values (instructions listed below)

Profile Name Profile Code Value Level

FND: Maximum size AFLOG_MAX_FILE_SIZE 100 or more

for log file in MB

FND: Log File for PL/SQL AFLOG_PLSQL_FILENAME APPLLOG_DIR/xxxxx.log User Level (e.g. for user
running the process)
FND: Log Level AFLOG_LEVEL FINEST User Level (e.g. for user
running the process)

FND: Module AFLOG_MODULE % User Level (e.g. for user

running the process)

FND: Log Enabled AFLOG_ENABLED Yes User Level (e.g. for user
running the process)
STEP 1 >
Increase the log size to 100MB

**Mandatory Important Step for Benefits**

Please make sure the log file size is more than 100 MB. If the file size is not sufficient, most of the times
the trace gets truncated. It will be of no use if the trace is truncated.

**Save **
STEP 2 >
Set PL/SQL Log File Name

**Save **
Please note -- File name has to be of the format -- APPLLOG_DIR/xxxxx.log (i.e. APPLLOG_DIR/diagnostic.log)

NOTE: This is the file name you will provide to support. If you are running
multiple trace files, you need to change this filename each time to avoid
overriding the previous filename.
STEP 3 >
Set Log level to be Finest for the user.

Note: The AFLOG_LEVEL profile option (FND: Log Level) should be added (if missing) with Site level value
set to Severe.

This is the out of the box seed data and should not be removed.

**Save **
STEP 4 >
Set the module where you want to run the trace.

Please set it as % if not otherwise instructed. This means it will trace all the modules.

**Save **
STEP 5 >
Enable Log for the user
Please note – It is highly recommended that before performing this step, in a separate tab/browser, you log
as the username that is set (i.e. “dummy”) and navigate as close as possible to the place where the issue
is observed. Then proceed in enabling the profile value.
This way, when the trace is enabled, system will capture only the relevant data and facilitate the
troubleshooting of the issue. Also, while the trace is active, it is expected to experience slowness in the UI
for that logged in user.

**Save **

(or SAVE and CLOSE)

B) – Reproduce the issue:
*** Immediately go to the page where you can reproduce the issue (i.e.
where you are seeing the error message).

C) – Disable the Tracing:

*** Once you have reproduced the issue, you need to disable the logging by
changing the value to ‘N’ for the AFLOG_ENABLED in Step 5.

**Save ** (or SAVE and CLOSE)

D) – Provide diagnostic file name to SR:

*** Please provide the file name to support through SR so they can obtain the
logs files from the servers. (filename done in Step 2 above).