How to troubleshoot a pricing issue? – In Mind Cloud

How do we know which logger to use for External Pricing?

If the standard implementation (JAVA implementation) is used for external pricing, the following table shows which logger is to be used in order to troubleshoot.

When	Logger Name
COD_SALESORDER_SIMULATE	ERPPricingCommand
BAPI_SALESORDER_SIMULATE and SSC environment	SSCERPPricingCommand
BAPI_SALESORDER_SIMULATE and non-SSC environment	IMCERPPricingCommand

If a groovy implementation is used, the logger GroovyLogger can be used to print logging.

How do we know how to troubleshoot Internal Pricing?

In order to troubleshoot internal pricing, users can turn on the setting “Enable Audit of Internal Price Engine”. When user executes internal pricing, audit log as HTML file will be generated on “Content Management → audit → {today date} → {quoteID} → Internal_Pricing” folder. In the audit log, all the information used for calculating pricing such as exchange rate, pricing scheme, pricing steps, lookup table used, and sales item information.

The screenshots below show the sample of the Internal Price Engine log.

Internal Pricing - Master Data

The following screenshot shows the pricing scheme executed, quote ID, priced date, and quote currency.

The following screenshot shows the exchange rate maintained in the system.

Internal Pricing - Price Data Preparation

The following screenshots mentions two (2) lookup tables that are used in the pricing scheme. Users can easily find the lookup table names in the lookup table column. Moreover, all the pricing steps that are included in the pricing scheme are listed below as well.

The following table shows the data record in the lookup table.

Other Pricing related logs

The following screenshot shows each of the sales item pricing. Sales items are printed in the execution order. Usually, it is displayed in a bottom-up approach.

The following screenshot is showing the table for whole pricing processing. If the calculation is shown as “Not Executed”, check the exceptions column. The reason for this is, is due to the product type filter or because of an exception.