This chapter covers the following topics:
For general information about the Model Debugger, see The Model Debugger.
For general information about unit testing, see Introduction to Unit Testing .
For information about using the Model Debugger, see:
To launch the Model Debugger from Configurator Developer:
Open a Model for editing, and then navigate to the Structure, Rules, or UI area of the Workbench.
Click Test Model.
Choose whether to Create a new configuration or Restore a saved configuration, and then click Next.
If you chose to restore a saved configuration, select a saved configuration from the list, and then click Next.
You can sort the data in each column by clicking the column header.
Verify that Model Debugger is selected, and then optionally enter any Session Parameters.
For details, see Session Parameters.
Click Finish. The Model Debugger displays the selected Model and applies the session parameters that you specified.
For details on using the Model Debugger, see Using the Model Debugger.
You can launch the Model Debugger directly from the Oracle E-Business Suite Home page, without starting Configurator Developer. The only limitation when launching the Model Debugger this way is that you can restore a saved configuration, but you cannot create a new configuration.
To launch the Model Debugger from the Oracle Applications E-Business Suite Home page:
Select the Oracle Configurator Developer responsibility, and then select Test Configuration.
Enter a Configuration Header ID and Revision Number, and then click Next.
If you want to display pricing and ATP information in the Model Debugger, click Preferences, and then enter the callback interface packages and procedures to use in the Custom Initialization Parameters field. For details, see Displaying Pricing Information and ATP Dates when Unit Testing.
To load the saved configuration using the latest, published version of the Model:
Select Use Currently Published Model Version.
The Model may have been modified since the configuration was saved. Select this option to test the saved configuration against the most up-to-date version of the Model structure and rules.
Specify the publication you want to test by specifying a date, Application Code, Publication Mode, or Usage.
Click Next.
To test the version of the Model against which the configuration was saved, choose Use Model Version Saved in Configuration, and then click Next.
Select this option to load the Model in the same state it was in when the configuration was saved. In other words, the Model structure and rules that are loaded are the same as when the configuration was saved, regardless of whether the published version has changed.
Optionally enter any Session Parameters.
For details, see Session Parameters.
Click Finish.
For details on using the Model Debugger, see Using the Model Debugger.
Important: The Model Debugger provides some additional functionality when using the Fusion Configurator Engine (FCE). The FCE is an alternative to the configuration engine described in this document. For all information about the Model Debugger and the FCE, see the Oracle Configurator Fusion Configurator Engine Guide.
Following are some suggestions for unit testing a configuration model using the Model Debugger.
Click Show Legend to see the icons that the Model Debugger uses to indicate each option’s logic state and any options that are unsatisfied. Expand parts of the Model structure to view their children, or click Expand All to view the Model’s entire structure. Click Collapse All to view only the first level of the Model structure.
Click the icon in the Add to Watch List column to monitor the status of specific items while unit testing. All items added to the Watch List appear in a separate table at the top of the page, along with their selection state and current value. Each item in the Watch List still appears in the Model structure. You can add items to the Watch List or remove them at any time while using the Model Debugger. To remove a node from the Watch List, click the icon in the Remove column.
Select and enter values for various items to add them to the configuration. Also add component instances and configure them. Notice how these actions affect the configuration and items in your Watch List.
To run a Configurator Extension, click the icon in the Run Extension column. If multiple Configurator Extensions exist for the selected node, choose the one to run from the page that appears, and then click Apply.
The number and distribution of Configurator Extension icons is affected by the choice of Model Node and Event Binding Scope in the Configurator Extension Rules defined for the Model. For example, if the Event Scope was chosen as Global, then Configurator Extension icons appear for every node of the Model. If the Event Scope was chosen as Base Node, then Configurator Extension icon appears only on that node of the Model.
Only Configurator Extensions bound to the onCommand event can be explicitly run in the Model Debugger. When you run one, the Model Debugger prints a message displaying the command string that was handled and the names of the Configurator Extension Rules that handled it. If multiple commands are bound to the same node, then the Model Debugger presents a list of them so that you can select the one that you want to run.
Navigate to the Summary tab to view a summary of all selected items. If pricing is enabled, this page also displays item pricing and Available to Promise (ATP) information.
For details about pricing and ATP in the Model Debugger, see Displaying Pricing Information and ATP Dates when Unit Testing.
Navigate to the Status tab to view items based on their current status in the configuration.
For example, go to the Unsatisfied Items section to see a list of all items that contain required selections, or go to User Requests to view only items that you selected during the debugging session (in other words, not items selected by the propagation of a rule). When testing a saved configuration, the User Requests section also shows items selected when the debugging session started.
For details about using the View list, see Views.
Click Save to save the configuration periodically. This performs an intermediate save, but does not give you the option to exit the Model Debugger.
Click Revert to Saved to rollback the changes and return the configuration to the way it was before the last time you saved it.
To exit the Model Debugger without saving the configuration, click Cancel.
To save the configuration and exit the Model Debugger:
Click Finish.
Enter a Configuration Name.
To create a new configuration with a unique Configuration Header ID, select New Configuration from the Save As list. (You can save a new configuration only if you launched the Model Debugger from Configurator Developer.)
To increment the Revision Number and save the configuration with the same Configuration Header ID, select New Revision.
Click Apply.
If the configuration is invalid or incomplete, the Model Debugger displays a status message. Click Yes to continue.
Make a note of the Configuration Header ID and Revision Number for future reference.
If you launched the Model Debugger from Configurator Developer, click Return to Configurator Developer.
If you launched the Model Debugger from the E-Business Suite Home page, click Home to return to the E-Business Suite Home page, or Logout to exit Oracle Applications.
To generate a User Interface, see Creating a New User Interface.
Related Topics
Launching a Runtime User Interface from Configurator Developer
Launching a Runtime User Interface from the E-Business Suite Home Page
To unit test a Model in a generated User Interface:
Open the Model for editing, then navigate to the Structure, Rules, or UI area of the Workbench.
Click Test Model.
Choose either Create a new configuration, or Restore a saved configuration, then click Next.
If you chose to restore a saved configuration, select it from the list, and then click Next.
If you chose to create a new configuration, go to the next step.
Select Model UI, and then select a UI from the list.
Specify Session Parameters, and then click Finish. Session parameters are described in Session Parameters.
Unit test the Model structure, rules, and review the UI to ensure that it performs as expected. For more information see Configuring an Item in a Runtime Oracle Configurator.
To launch a saved configuration from the Oracle Applications E-Business Suite Home page, you must know the configuration’s header ID and Revision number.
When you open a saved configuration from the E-Business Suite Home page, you can view only the UI that was saved with the configuration; in other words, you do not have the option to select one of the Model’s UIs.
To unit test a saved configuration from the E-Business Suite Home page:
Click Test Configuration.
Enter the saved configuration’s Header ID and Revision Number.
To test the published version of the Model, choose Use Currently Published Model Version.
To test the version of the Model against which the configuration was saved, choose Use Model Version Saved in Configuration, and then click Next.
If you chose to test the currently published Model version, enter applicability parameters to specify the publication you want to test.
Specify Session Parameters, and then click Finish.
Session parameters are described in Session Parameters.
For details about unit testing a configuration in a User Interface, see Configuring an Item in a Runtime Oracle Configurator.