Pricing Administration Guide > Testing and Validating Pricing Models >

About Testing and Validating Pricing Models

To validate pricing models, you can test them as they will be used in actual runtime scenarios.

To validate that a pricing model functions as expected, you need to test each pricing factor and the sequences of pricing factors that may occur when the model is actually used.

It is best to test incrementally. Test the results of each pricing adjustment before testing the interactions of adjustments. This is especially important if you are applying many pricing factors in the pricing model or compounding multiple pricing factors in a model.

Siebel ePricer has built-in features for testing pricing factors.

• The Quote Pricing Model Validation view and the Order Pricing Model Validation view allow you to create quote and order data and to experiment with sample scenarios.
• The Siebel ePricer log file records the effects of each pricing factor when it is executed.

When you test pricing factors in the pricing model validation views, the pricing model must be locked. A locked model cannot accidentally execute in runtime.

If you test the pricing factors in a simulated runtime environment, the pricing model must be unlocked. An unlocked model can be used in runtime processing.

To test a model in any environment, you must use the Reload function to load the model cache.

It is particularly important to test models when pricing models use complex decision flows, with different pricing adjustments, such as volume discounts, component-based pricing, attribute-based pricing, and pricing factors.