Troubleshoot pricing
- 12 Nov 2024
- 1 Minute to read
- Print
- DarkLight
Troubleshoot pricing
- Updated on 12 Nov 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Troubleshoot external pricing
If using a standard Java implementation for external pricing, the following table shows which logger to use for troubleshooting.
| Instance | Logger Name |
|---|---|
| COD_SALESORDER_SIMULATE | ERPPricingCommand |
| BAPI_SALESORDER_SIMULATE and SSC environment | SSCERPPricingCommand |
| BAPI_SALESORDER_SIMULATE and non-SSC environment | IMCERPPricingCommand |
If you are using a Groovy implementation, use GroovyLogger to print logging.
Troubleshoot internal pricing
Enable and use the Zilliant CPQ pricing audit feature if you suspect:
- Prices are not aggregating correctly
- Price calculations are incorrect
- Pricing schemes are incomplete
Enable internal pricing audit
- From the application left navigation area, select Administration.
- From Master Data Management, select Setting Boolean.
- Select Enable Audit of Internal Price Engine.
- Set the Setting Value Boolean switch to YES.
When a user executes internal pricing, the system generates an audit log file in .html format.
Review an audit file
- From the application left navigation area, select Administration.
- Select Content Management from the top navigation bar.
In the audit log, review the pricing information, including exchange rate, pricing scheme, pricing steps, lookup table, and sales items.
Sales items are printed in the order of their execution. If a calculation indicates Not Executed, check the Exceptions column.
Was this article helpful?
