«

»

Feb 28 2011

JD Edwards ER Debugger – Conditional Breakpoint

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)

Event Rules Debugger has been an integral part of a JD Edwards Developer’s life. Checking the code, the parameters, inspecting values etc, makes the life easy.

For those who want to learn and understand Event Rules (ER) Debugger visit this Link from Oracle

The JD Edwards debugger helps not just in debugging the code at run time, but at times, it gives us a good visual of the code,and the parameters which itself sometimes solves the issue. 

This is what the Help file of ER Debugger says : “The Event Rules Debugger provides the essential debugging tools (breakpoints, step commands, and variable inspection), you need to debug a OneWorld interactive or batch application. You can use the Event Rules Debugger to debug named event rules and table event rules. When the Event Rules Debugger builds debug information for an application, it includes named event rule and table event rule information for that application

ER debugger had many limitations, like

  • Suppose you have about 10000+ records in a UBE, and you have an issue with records starting from nth one.
  • Need to break only for a specific record.
  • Break on the line of code when a condition satisfies (like the var is not equal to value).
  • Break on multiples of a hit count, e.g. break on 10th, 20th, 30th, ….

Now from E1 tools – 8.97 onwards you have got a new functionality called Conditional Debug, for ER Debugger. Presenting Conditional Debugging

Conditional Debug Breakpoint
Conditional Debug Breakpoint

Notice the ? symbol on the Breakpoint set. That is a conditional breakpoint. This is how you set it.

Right click on the breakpoint, and select its Properties and you will get the following window

Breakpoint with Expression Condition

Breakpoint with Expression Condition

Here you can set the Condition for your break point on when to Break. Only issue here is that you have to specify the complete Name of the variable (Case sensitive too) with the condition.

Expression Condition Dialog

Expression Condition Dialog

Set Hit CountNow let us look at the HIT counter functionality of the Conditional Breakpoint.
The hit counter can be used on the following occasions.

  • Break Always on all records
  • Break if the Hit Count is equal to a value
  • Break if hit count is greater than or equal to
  • Break if the hit count is a multiple of a value
Hit Count Condition Dialog

Hit Count Condition Dialog

An additional functionality that the Breakpoint Properties give us is Enable/Disable a Breakpoint, instead of deleting it.

Disabled Breakpoint

Disabled BreakpointEnable/Disable Breakpoint

This is where you Enable/Disable

Enable/Disable Breakpoint

Enable/Disable Breakpoint

Published under the license.

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)
JD Edwards ER Debugger - Conditional Breakpoint, 5.0 out of 5 based on 2 ratings
(Visited 800 times, 1 visits today)

About the author

Ashish Khandelwal

4 comments

Skip to comment form

  1. Sachin Pande

    Hi ,
    It’s very good ..it help to solve time while debug .

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  2. Abhishek Chhajer

    awesome!!!

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  3. Deepak mishra

    It saves so much of time and the irritation usually which we tends to gets sometime in XE version……very useful utility….

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  4. Nivi

    Very Helpful…It would be good,if we get the same functionality in debugging C business functions also…

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

Leave a Reply