According to the helpful Oracle Support DocId:791049.1 ::R12 SLA/FAH: How to Improve Performance in Subledger Accounting & Financials Accounting Hub
in the 4th FAQ which explain how to capturing trace and/or tkprof.
1. Enable tracing using the profile option – ‘Initialization SQL Statement – Custom’
Set this at the user level with the following string:
BEGIN FND_CTL.FND_SESS_CTL(”,”, ”, ‘TRUE’,”,’ALTER SESSION SET TRACEFILE_IDENTIFIER=’||””||’XXXTEST’||””||’ EVENTS =’||””||’ 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 ‘||””); END;
2. Login using the user for which you set the profile option.
3. Reproduce the issue.
4. Reset the profile option to its prior value.
5. Locate the generated trace, using the query:
select name, value from v$parameter where name like ‘user_dump_dest’;
6. Convert the trace file into tkprof format using the command:
tkprof <filename.trc> <output_filename_SORT.txt> explain=apps/<password> sort='(prsela,exeela,fchela)’
in the 5Th FAQ witch explain basic points to check before logging a performance bug. and one of these basic step is to stop the Debug logging”if it;s not nessessary, Or you can make it on USER level not SITE level”
Do you have any of the following profiles set to Yes at the User Level?
If so, then please disable them (i.e., set them to No) and re-run Create Accounting:
When running Create Accounting, the profile values should be set as follows:
FND: Debug Log Enabled = No
SLA: Enable Diagnostics = No
AR: Enable Debug Message Output = No — If it is for Receivables.