Post date: Sep 16, 2011 4:6:7 AM
In this Document
A) Instructions in generating the Debug Log :
B) Instructions on running the script : ebtxtract.sql
C) What to look for in a Tax Debug Log
D) Upload the resulting file to support for review.
Oracle E-Business Tax - Version: 12.0 to 12.1.2 - Release: 12.0 to 12.1
Information in this document applies to any platform.
EBTax ,ebtxtract.sql
We are actively trying to build up participation in our EBTax community. We'd love your input, ideas, collaboration and solutions to be part of the experience. Check us out at on the E-Business Tax communities page
Generate a FND debug log for the tax calculation in R12.
Use the following steps to generate the FND debug log.
1) Set the following Profiles at the user level :
FND: Debug Log Enabled : Yes
FND: Debug Log Level : Statement
FND: Debug Log Module : %
2) Get the Starting Point for the log_sequence
SELECT MAX(log_sequence) log_start_point
FROM fnd_log_messages;
3) Run the Program / enter the Transaction etc to reproduce the issue .
4) Get the End Point for the log_sequence
SELECT MAX(log_sequence) log_end_point
FROM fnd_log_messages;
5) Get the debug log .
Use the script ebtxtract.sql to get the debug log using the Log_start_point
and Log_End_Point
If you are submitting a concurrent request use the following to get the Log_start_point and Log_End_Point . You need to give the request id as a parameter.
SELECT MIN(log_sequence) log_start_point,
MAX(log_sequence) log_end_point
FROM fnd_log_messages LOG,
fnd_log_transaction_context con
WHERE con.transaction_id = &request_id
AND con.transaction_type = 'REQUEST'
AND con.transaction_context_id = LOG.transaction_context_id
AND LOG.MODULE LIKE 'ZX%'
ORDER BY LOG.log_sequence;
Please note that you will need to use sql plus to be able to get the output in the desired format.
If you are using SQL Developer , invoke the SQL Plus utility from that tool and then run the script.
This is not tested on TOAD or other such Data Base access utilities.
Download the file ebtxtract.sql
Give the following parameters :
Start_log_sequence , Stop_log_sequence
This script will assume that the extract script is run on the same date on which the debug log was generated.If you are running this script to get the debug log generated earlier than the system date please alert support of this situation .
Tax debug logs can be very long and difficult to review. There are a few tricks to finding meaningful information in the logs that we will attempt to highlight below:
a) Search for Database errors
Search for the string "ORA-" If there was a database error this will return the portion of the debug log containing that error. Copy and past the line containing the ORA error into the search window on My Oracle Support and you can effectively filter the search results to documents that contain that error.
b) Search for Return Status messages
In addition to database errors the ebtax developers coded into the debugging utility several return status values that indicate code that failed. Search for the following two strings in your debug log file and again use the corresponding line from the log file to search for solutions on My Oracle Support
1) Return Status = E
2) Return Status = U
When conducting the keyword search, wrapping some or all of the string in double quotes (ex: "Return Status = E" ) will cause that portion of the search to be done as an exact string search. This will ensure that the parsing engine does not break the string up and return unrelated results.
NOTE:417238.1 - How to obtain and read a debug logfile for R12 E-Business Tax (EBTAX)
Attachments
File to generate the extract output (11.59 KB)
Related
Products
Oracle E-Business Suite > Financial Management > Financials Common Modules > Oracle E-Business Tax
Keywords
FND_LOG_TRANSACTION_CONTEXT; FND_LOG_MESSAGES; DEBUGGING; R12; STATEMENTS; E-BUSINESS TAX; TAX CALCULATION
Article Rating
Comments
Provide feedback for this article. Please use 'Contact Us' for other feedback.
Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
Cancel