This chapter covers the following topics:
The Pricing Engine Request Viewer window captures the pricing call from any calling application, such as Oracle Order Management, and displays the inputs and outputs of the pricing call. This information can help you to diagnose which price list lines were selected or rejected by the pricing engine and to determine why certain prices and adjustments were or were not applied.
Only the latest pricing request appears; however, historical data is not maintained because the Pricing Engine Request Viewer window updates the display information each time that the pricing engine captures a new transaction. Previous pricing requests are saved in the pricing tables.
The Pricing Engine Request Viewer window is available from the main Advanced Pricing menu (Pricing Manager responsibility) or in Oracle Order Management using the following navigation path: Sales Orders > Tools > Pricing Engine Request Viewer.
Process for the Pricing Engine Request Viewer
The following outlines the activities when a pricing call is made:
The calling application makes a call to build qualifiers and builds the contexts through mapping.
The calling application calls the pricing engine with the attributes generated by attribute mapping.
The pricing engine processes the request, and then searches for and evaluates eligible price list and modifier lines.
If the profile option QP Debug is set to Request Viewer On, then the pricing engine inserts records into the permanent pricing debug tables and generates a unique request ID, storing the information from the calling application.
You can then view the pricing request information by querying the request in the Pricing Engine Request Viewer from the Order Management Sales Order Pad or through the Pricing Manager responsibility menu.
QP: Debug: Set the value of this profile option to Request Viewer On when you want the Request Viewer to capture pricing request details into the pricing debug tables and debug log information into the debug log table. The debug log text file is also created. The default value is Request Viewer Off.
The setting is active for the transactions for the user who set this profile option - other users' transactions are not affected.
Note: Setting the profile QP: Debug slows the performance of the Pricing Engine Request Viewer. The concurrent request Purge Pricing Engine Requests purges the pricing engine requests. You should run this program on a regular basis to purge the historical data from the pricing debug tables. Periodically purging the historical data improves the performance of the Pricing Engine Request Viewer window.
QP: Set Request Name: The profile option QP: Set Request Name is used in conjunction with the QP: Debug profile option. Set QP: Set Request Name to Yes if you want the value in the Request Name field prefixed to the OrderID. For more information on setting up profile options, see Oracle Advanced Pricing Implementation Manual, Profile Options.
Related Topics
Viewing Information in the Pricing Engine Request Viewer
The Pricing Engine Request Viewer window displays detailed information about the price list lines and modifier lines that the pricing engine applied or rejected. In the Pricing Engine Request Viewer window, you can view the following information:
Pricing attributes, qualifiers, and product attributes passed to the pricing engine along with the other data generated by the pricing engine.
Modifier lines that the pricing engine applied or rejected for benefit adjustments along with the details of the modifier line. View price request line of the calling application.
Relationships between order lines for promotional modifiers, price breaks, and service lines.
Formula step values generated by the pricing engine used in formula calculation.
Controls passed by the calling application to the pricing engine, such as Event, Rounding, Search and Calculate Flag, and GSA.
View and query fields in the Pricing Debug Log.
You can view the debug log in the Pricing Engine Request Viewer window, and query the record within the debug log to display the lines directly. The results are the 10 previous lines and the remaining lines of the debug file.
You can delete a request by selecting (N) Edit > Delete.
The transaction details appear in one or more of the following regions in the Pricing Engine Request Viewer window.
Pricing Engine Requests region
This region displays information about the pricing requests and information about controls sent by the calling application to help you locate the problem.
For Request Type ONT only, the order number associated with the request appears.
Note: Depending on the version of Oracle Advanced Pricing, the order and line numbers for orders created in prior releases may not appear in the Pricing Engine Request Viewer window. However, you can view order and line numbers created in subsequent releases.
Pricing Engine Request Lines region
This regions shows information about the lines being priced, including line number, unit price, and adjusted unit price. You can view information related to service and serviceable lines in this region.
Note: For lines of type LINE, the Line No. field displays the appropriate line number from the Order Entry page. For lines of type ORDER, the order number associated with that request appears. For requests of type PRICE, the line number for the request lines of type LINE does not appear.
The Request Id + Line Index column maintains the master-detail relationship between the lines and line details. This block is used to change operand value, select/de-select modifiers, change manual modifiers, and change buckets.
Pricing Engine Request Line Details region
This region displays information about processed price list lines and modifiers lines selected or rejected by the pricing engine. The Priced box indicates which lines were finally selected for pricing by the pricing engine. The Applied check box indicates which lines were considered in calculating the selling price.
This region also displays the information for item upgrades, coupon issue, term substitution, freight and special charges, and relationships between price breaks.
Pricing Debug window
Click View Debug Log to view the debug log in the Pricing Engine Request Viewer window. You can then query a record within the debug log to display the lines directly. The results display the ten previous lines and the remaining lines of the debug file.
Attributes window
Click the Attributes button to display all attributes for a selected line or line detail. The region displays information about the pricing attributes that the attribute mapping function passed to the pricing engine. The pricing engine uses these attributes to qualify a line or an order for price and adjustments:
Click Attributes from the Request Lines region to display the attributes passed to the pricing engine.
Click Attributes from the Request Line Details region to display the attributes related to the selected price list lines/modifier line.
Pricing Debug Related Lines window
Click Related Lines from the Pricing Engine Request Viewer window to display the Pricing Debug Related Lines window. The cursor must be in the Engine Request Lines Details region. You can view the relationship between the Buy and Get items for Other Item Discounts and Promotional Goods.
Formula Step Values window
When your cursor is in the Pricing Engine Request Lines Detail region, click Step Values in the Pricing Engine Request Viewer window to display the Formula Step Values window.
Related Topics