Oracle® Retail Merchandising System Custom Flex Attribute Solution Implementation Guide Release 15.0 E65438-01 |
|
Previous |
Next |
The CFAS framework also includes a built-in tool designed to help you with the debugging of the code. DBG.MSG (used by the CFAS user interface and libraries) and DBG_SQL.MSG (used by the database stored procedures) are procedures used to display and capture debug messages to a log table.
This tool provides the following features:
Configurable via the database table (DEBUG_CFG).
Debug messages are only displayed/logged to a table for a specific user defined condition.
Target specific program units in the user interface (such as P_FORM_STARTUP, WHEN-VALIDATE-ITEM, and so on) or database stored procedures.
When working with multiple stored procedures or program units, you can switch the object for which you want to see or log messages.
To set the debugging mode for CFAS:
In the relevant procedure, enter the SCHEMA name or user name, OBJECT to debug, and optionally set whether the messages are displayed online (when debugging the UI/library) or saved to a log table (DEBUG_LOG). Set at least one option to Y.
If the program unit does not have debug messages, strategically insert the debug messages using the DBG.MSG for the user interface and DBG_SQL.MSG for the stored procedures. For DBG.MSG, use as the usual imessage(). Pass in the name of the program unit to debug and the debug message.
Compile the code and run the test.