How Oracle EBS standard error messages are tracked (DEBUG)

Http://www.cnblogs.com/songdavid/articles/2067534.html

When calling the EBS standard API, it may be possible to return some incomprehensible errors, such as when I recently developed rcv_transaction_interface, the data card is not in the interface table, but the error returned is confusing.

For example, the following two errors are confusing:

*******************

Error:derive_vendor_rcv_line_qty-098:1

CAUSE:A SQL error has occurred in Derive_vendor_rcv_line_qty. The SQL error is user-defined Exception.

Action:take note of both this error number and the actions are were trying to perform. Contact your system administrator for further assistance.

********************

RVTSH-189: Error returned by subroutine Rvtshiline ()

Cause: An internal error occurred while the subroutine Rvtshiline () returned.

Action: Please record this error number and the activity you are trying to do. Contact your system administrator for help

Concurrent Program RVCTP returned error

CAUSE:RVCTP encountered an internal error. parameters:rvctp,immediate,4686, 

Action:note Both this error number and the actions you were trying to perfo RM. Contact your system admi
Rvtbm-008:subroutine Rvtbm_immediate_mngr () returned error

Cause:subroutine Rvtbm_immediate_mngr () returned an internal error. 

Action:note This error number and the actions you are try ing to perform. Contact your syste
Rvtbm-120:subroutine rvtptcontrol () returned error

Cause:subroutine Rvtptcontrol () Returned an internal error. ,

Action:note This error number and the actions you were trying to perform. Contact your system administrator 
Concurrent Manager encountered a error while attempting to start your immediat E Concurrent program RVCTP. Routine &routine received a return code of failure.

Contact your support representative.

****************************************

Then we can use the EBS standard debug method to easily trace the cause of the error:

******************

First, we need to set some profiles under admin responsibility:

----------------------------------------------
A. Rcv:debug Mode=yes
B. Fnd:debug Log Enabled=yes
C. fnd:debug Log level=statement
D. Fnd:debug Log module=po%
----------------------------------------------
A. TP:INV Transaction processing Mode=on-line
B. Inv:debug Trace=yes
C. inv:debug level=11
D. inv:debug file (including the complete path) =<valid directory path----------------------------------------------

A. Om:debug level = 5
B. Om:debug Log directory = <valid directory path>

You can then use the following SQL to view the debug information:

Select To_char (timestamp, ' dd-mon-yy HH24:MI:SS '),
Message_text,
Module
Log_sequence
From Fnd_log_messages
WHERE trunc (timestamp) = Trunc (sysdate)
and process_id = (SELECT os_process_id
From Fnd_concurrent_requests
WHERE request_id = &p_request_id)
and module not like ' fnd% '
ORDER by Log_sequence;

*********************************************

For example, error: The debug information for error:derive_vendor_rcv_line_qty-098 is as follows:

match Option:rprofile val UE allow_rate_override_for_user_rate_type:n	po.plsql.RCV_ Roi_transaction. rcv_roi_transaction.4731
no of Di Stributions:1:: Rate and Rate_date in PO distributions7.468200216771979::16-jan-08	Po.plsql.RCV_ROI_TRANSACTION. rcv_roi_transaction.4757
Exception in Derive_vendor_rcv_line_qty	Po.plsql.RCV_ROI_TRANSACTION. rcv_roi_transaction.5011

As a result, we can see that in package:rcv_roi_transaction, there is an error between lines 4757-5011, which causes exception errors: error:derive_vendor_rcv_line_qty-098, Then this error is easily solved.

How Oracle EBS standard error messages are tracked (DEBUG)