Form Level Debug (FRD Debug Small Tips)

This tips is used to add your debug msg into form and Nomsg popup while testing the issue

Introduce a parameter into your debug form,eg. PT_DEBUG

Add your debug message into form/pld like:

copy('Go into to_account_fh,event='||event,'PARAMETER.PT_DEBUG');

copy('Go into IF','PARAMETER.PT_DEBUG');

Then in FRD log, it will like

Executing NAME_IN Built-in:
In Argument 0 - Type: String   Value: SYSTEM.RECORD_STATUS
Out Argument 0 - Type: String   Value: INSERT

Executing COPY Built-in:
In Argument 0 - Type: String   Value: Go into to_account_fh,event=INIT
In Argument 1 - Type: String   Value: PARAMETER.PT_DEBUG

Executing COPY Built-in:
In Argument 0 - Type: String   Value: Go into IF
In Argument 1 - Type: String   Value: PARAMETER.PT_DEBUG

Executing NAME_IN Built-in:
In Argument 0 - Type: String   Value: TOMAI_MAIN_LINES_BLK.INVENTORY_ITEM
Out Argument 0 - Type: String   Value: AS54888

Benefit(Relative to fnd_message.debug)
There is no debug message popup, you can add many debug bug messages into form/pld

Other Reference: Note 438652.1 - R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications

===EOF===

转载请注明出处:http://blog.csdn.net/pan_tian/article/details/7431771