Thursday, August 22, 2019

writeDiagnostics in OAF?

Step:1) You can see the log by using the below code in the Controller

Syntax:
            pageContext.writeDiagnostics(Object,String,int);

Example:
pageContext.writeDiagnostics(this,”Enter into CO:=”+assnum,OAFwkConstants.STATEMENT);

For bc4j objects(AM, View Object Impl ,Entity Object Impl)

use the below code as Syntax:

getOADBTransaction().writeDiagnostics(Object,String,int);

Example: getOADBTransaction().writeDiagnostics(this,”customerid in AM =”+customerid,1);

Step:2)  Set the profile Option Values Go to System Administrator responsibility and set the profile options to enable the log.

Navigation : System Administrator-Profile-System Set FND: Debug Log Enabled to Yes

Save the Record. Set FND: Debug Log Level to Statement

Save the Record. Bounce the Apache. When you login to EBS you can see Logging is enabled.

Step:3) Query FND_LOG_MESSAGES in the database for all the debugging messages.

Select * from FND_LOG_MESSAGES

Now the log messages can be seen in the table. You can also see the log on seen by selecting the Diagnostics link on OAF Page Select Show Log on Screen Option.

No comments:

Post a Comment

AME (Approval Management Engine)

AME (Approval Management Engine) : AME Stands for Oracle Approval Management Engine. AME is a self service web application that enables...