Internal Pricing

1 Introduction

The system administration guide contains key information to setup pricing in Manufacturing Sales Platform (MSP) CPQ Internal Pricing Guide effectively. The guide provides the concepts and detailed definition of the functions, aiming to enable administrator to have sufficient knowledge to setup the function with minimal supervision.

The document will be continually edited and updated based on latest product releases. Taking into the consideration of expensive effort keeping the document updated and effective usage of it, only major and complex features should be covered.

To better illustrate how to setup certain feature, some examples are given. It also contains the steps linked to relevant screens. Each step contains actions which the administrator needs to perform to complete the setup.

This administration guide is based on Sales Platform release version 1902.

Enjoy!

The Product Engineering Team

2 CPQ Internal Pricing Guide Introduction

CPQ Internal Pricing Guide enables administrator to maintain data, configure major pricing steps and pricing scheme and sum up sales item price and quote price.

CPQ has available 3 pricing categories, these are:

Internal Pricing

  • Internal pricing is based on the pricing scheme and pricing steps maintained in CPQ system.

 

External Pricing

  • External pricing is done with the help of pricing simulation in ERP system. All the price related information such as pricing procedures, condition tables, condition types, access sequences is maintained in the ERP system. It involves a BAPI (Business Application Programming Interface) call with parameters maintained in CPQ. BAPI returns the pricing of each of the sales Items and whole quotation together with breakdown of each sales item pricing. (For the moment, we skipped this portion)

 

Basic Pricing based on SPARQL (Deprecated)

  • Based on the user model, the pricing calculation methods are written in SPARQL and is maintained in CPQ system. This is not supported after 1711 release

Determination for pricing categories is handled by the setting in CPQ. To enable internal pricing, setting “Enable Internal Pricing” must be turn on. In this document, we will focus on “Internal Pricing Engine (IPE)”.

3 Internal Pricing Engine

Internal Pricing Engine (IPE) is basically composed of price item type, pricing table (also known as lookup table), pricing scheme, pricing step and price item type category. It provides functionality for currency conversion with maintained exchange rates. Moreover, IPE has an easy retrieval of price data based on validity of price records and the quote pricing date and manipulation of price data for quotation

Pricing scheme, pricing step, data maintained in lookup table and currently executed quote’s information are the input elements to the IPE. The output from IPE are sales item net price (based on each sales item and known as sales item unit price), sales item total price (based on total quantity), document header net value and the breakdown of each of them. Starting from the following section, each of components will be described in detail.

3.1 Price Item Type

Price item type is one of the most basic parts of internal pricing engine. It is maintained as master data. Administrator of CPQ system needs to maintain all the price item types required from the master data management screen. The following figure shows price item type sample.

Figure 1 - Price Item Type Sample
Figure 1 - Price Item Type Sample
NoData PointMandatoryHow it works
1NameYesPrice Item Type Name. Unique name for each of the price item type.
2Price Item Type CategoryYesIt will be explained detailed in another section 2.5.
3Price Item Type SignNoTwo options:  PLUS, and MINUS are available. Default value is PLUS, which will add up to the cost of quote and sales item net price. It is used whether the value of price item type is added or subtracted from sales item amount.
4Price Item RelevanceNoThree options: 0, 1, 2 are available. Determines whether the price item type is applicable to quote (0) or sales item (1) or both (2). Default value is 1, only applicable to sales Item.
5DefaultNoN/A to IPE.
6Is Percent ValueNoDetermines whether the price item type is percentage or amount.
7Is Quantity BasedNoDetermines whether the price item type is based on quantity or lump sum.
8External IdNoN/A to IPE.
9ERP IdNoN/A to IPE.
10Is DeltaNoDetermines whether the price item type is delta price item or not. Detail explanation about delta pricing is described in section  2.7 Delta Pricing.

3.2  Pricing Table

Pricing table (also known as Lookup Table) are the place holders to store data inside CPQ system. It supports the ability to search with well-defined expression or criteria.

Figure 2 - Lookup Table Creation
Figure 2 - Lookup Table Creation
NoData PointMandatoryHow it works
1ERP IDNoERP Id of lookup table.
2NameYesName of lookup table.
3Has ValidityNoDetermines whether lookup table if validity based or not. If YES, it will add extra “validFrom” and “validTo” fields automatically.
4Delta Price TableNoYES, represents this lookup table is delta price table and will add “PRICE_ITEM_TYPE” and “DELTA_PRICE” fields automatically. By default, administrator should not choose this option to avoid unnecessary columns.

The usage of this will be explained in section  2.7 Delta Pricing.

Figure 3 - Sample Lookup Table
Figure 4 - Sample Lookup Field
Figure 4 - Sample Lookup Field
NoData PointMandatoryHow it works
1NameYesLookup field name
2Column IdYesLookup field sequence ID
3Record TypeYesAvailable record types are Currency, Data, Fetched, Price, “Valid From” and “Valid To”, Assert, Percent and Rate. However, the latter three are rarely used.
4Lookup Field SearchableNoYES, represents this lookup field is used as key or part of combined key to search.
5Lookup Field Unique KeyNoYES, represents this lookup field is unique. No duplicate values are allowed for this value.
6Currency FieldNoUse for lookup table synchronization from ERP system. Usage is described in detail 2.2.1.
7ERP IdNoERP ID of lookup field. Use for lookup table synchronization from ERP system.
8Business TypeNoRepresents the business type of which owns attribute. It helps to support lookup record data creation.
9AttributeNoRepresents the attribute name to search. Generally, the attribute that represents the last part of search expression. It helps to support lookup record data creation.
10Search ExpressionNoRepresents expression how the value is built as key to retrieve data from lookup table. Correct expression is important. Lookup field searchable and search expression are pair data points.

3.2.1 Synchronizing Custom Table/View from ERP as Lookup Table

CPQ can integrate with SAP ERP system. The data maintained in SAP ERP custom tables or view can be synchronized into lookup table and can make it use by the IPE. In this case, data is maintained in ERP system, but pricing and calculation is done in CPQ system. The ERP ID of lookup table and lookup field represents the ERP table and ERP table fields respectively in SAP ERP table field.

Usually there is one to one mapping not only for ERP table and lookup table but also for ERP field and lookup field. The mapping is done via ERP ID. The following figure shows how to set up the lookup table to make it synchronize.

Figure 5 - Set up Lookup Table for Synchronization
Figure 5 - Set up Lookup Table for Synchronization

As you see in the above figure, one lookup field is mapped to one ERP field. Linked currency is mandatory for price lookup field in data synchronization.

Figure 6 - Lookup Field Price
Figure 6 - Lookup Field Price
Figure 7 - Synchronize Lookup Table
Figure 7 - Synchronize Lookup Table
Figure 8 - Result of Lookup Table Synchronization
Figure 8 - Result of Lookup Table Synchronization

3.3 Pricing Scheme

Pricing scheme is a predefined arrangement or setup of how the calculation of quote pricing is done in the CPQ system. It is composed of multiple pricing steps. Each pricing step generally yields the part of sales item net price. Summation of all the sales item net price usually gives document header price or quote price.

IPE produces sales item net price, sales item net value and document header net value which is quote price. All the events that can affect the quote price such as adding a new line item, changing sales item quantity, deletion of sales item or changing of price date automatically triggers internal pricing. Besides automatic triggering, users can click the internal pricing button to explicitly make pricing.

At one point of time, only one pricing scheme must be activated. Till 1902r, pricing scheme determination logic is not supported. To make it clear, only inactive price scheme is editable. Deactivation and activation and of price scheme is required as administrator to make changes.

Figure 9 - Pricing Scheme Creation
Figure 9 - Pricing Scheme Creation

3.4 Pricing Step

The following data points are mandatory for pricing step creation.

Figure 10 - Pricing Step Creation
Figure 10 - Pricing Step Creation
NoData PointMandatoryHow it works
1Price Item TypeYesRepresents price item type and its associated category determines how the pricing step will be calculated.
2Pricing Step NameYesThe name of pricing step.
3Sequence IDYesSequence ID of pricing step. No duplicate is allowed.
4Percent OnYesEnables only when the price item type is percent value.
5Arithmetic ExpressionNoEnables only when the price item type is subtotal.
6Search ExpressionNoEnables only when the price item type is fetched.
7Record TypeNoNA, place holder for future scalability

3.5 Reordering Questions

Price item type category of price item type determines how the pricing step will be calculated to get the sales item amount. From pricing scheme point of view, the data points required to maintain for each individual pricing step will be different according to the price item type category.

There are six price item type categories:
1. Lookup table category
2. Fetch category
3. Calculated category
4. Manual category
5. Subtotal category
6. Aggregation category (also known as Aggregation of specific line item of child)
7. Script category

The detail description of each of the categories together with the pricing will be explained in the following from Section Lookup Category to Section Script Category below.

3.5.1 Lookup Category

Use Case

The pricing data (amount with currency and validity) is maintained in a table. This data is retrieved by a unique key or a combination of unique keys such as (product id only or product id together with sales organization). CPQ gives the flexibility to define such a lookup table with fields dynamically, ability to maintain pricing data and usage in IPE.

Example

Maintain Product List Price in a lookup table named “Product List Price”. This list price is retrieved by product ERP ID.

3.5.1.1  Create Pricing Step

Create a pricing step with price item type whose category is lookup table. Any name and sequence id can be given to the pricing step.

Figure 11 - Lookup Pricing Step (1)
Figure 11 - Lookup Pricing Step (1)
Figure 12 - Lookup Pricing Step (2)
Figure 12 - Lookup Pricing Step (2)
NoData PointMandatoryHow it works
1Sequence IDYesDetermines order of pricing step in execution. No duplicate is allowed.
2NameYesName of Pricing Step.
3Price Item TypeYesIn this case, it is Lookup table category.
4Percent OnNoN/A
5Arithmetic ExpressionNoN/A
6Search ExpressionNoN/A
7Groovy ScriptNoApplicable only when price item type category is groovy category.
8Routing RelevantNoDetermines whether pricing step is a place holder for material routing. If it is routing relevant, the purpose of using this pricing step is for ERP routing creation and the output of the price item type will be excluded in sales item amount.
9MandatoryNoDetermines whether pricing step is mandatory or not. If it is mandatory, notification will be shown if pricing step does not have amount.
10DisabledNoDetermines whether pricing step is disabled.
11Applicable Product TypeNoDetermines the product type applicable to the product. If blank, the pricing step is applicable to all product types.

Apart from price item type, the description of rest of price item type category is the same.

Figure 13 - Lookup Pricing Step (3)
3.5.1.2  Add Lookup Table Sequence

Pricing step with lookup up category must have at least one lookup table sequence. If more than one lookup table sequences are existed, pricing scheme will follow the sequence to get price data. The sequence is determined the order that it usually goes from most specific to generic ones.

The following figure shows the example pricing step with two lookup table sequences. Sequence ID  1 is used for lookup table searched with the combination of product ID and account ID. Sequence ID 2 is used for lookup table searched with product ID only.

Figure 14 - Lookup Table Sequence Creation (1)
Figure 15 - Lookup Table Sequence Creation (2)
3.5.1.3 Add Lookup Table and Field

Each lookup table sequence must have exactly one lookup table and one lookup field. Prior creation of lookup table and fields is required in order to select lookup table and its related field from dropdown. Here, it is only mentioned about the lookup table usage and how it will retrieve. It defines only lookup table and lookup table field. Under which condition or criteria or how the lookup record is picked up is defined in lookup table. The following figures shows steps by step creation of lookup table and lookup fields and how-to entry data to lookup table.

Figure 16 - Create Lookup Table
Figure 16 - Create Lookup Table
Figure 17 - Create Lookup Field:Product ID
Figure 17 - Create Lookup Field:Product ID
Figure 18 - Create Lookup Field:List Price
Figure 18 - Create Lookup Field:List Price
Figure 19 - Lookup Table Overview
Figure 19 - Lookup Table Overview
Figure 20 - Detail View of Product ID field
Figure 20 - Detail View of Product ID field
Figure 21 - Detail View of List Price field
Figure 21 - Detail View of List Price field

Once lookup table is created and set up fully, check the schema before adding lookup record addition. Once confirmed, activate lookup table to add new records.

Figure 22 - Lookup Table Activation
Figure 22 - Lookup Table Activation
Figure 23 - Data Entry 1: Lookup Record
Figure 23 - Data Entry 1: Lookup Record
Figure 24 - Data Entry 2:Lookup Record
Figure 24 - Data Entry 2:Lookup Record
Figure 25 - Price Entry: Price Record
Figure 25 - Price Entry: Price Record
3.5.1.4 How It Works

The product price maintained must be picked up according to product id and validity date with respective to quote pricing date. If lookup record currency is different from sales item currency, the exchange rate conversion is applied.

Figure 26 - Sample Quote with Currency EURO
Figure 26 - Sample Quote with Currency EURO

The unit price for Product 803 is maintained as 150 SGD and is valid from Feb 7, 2019 to Dec 31, 9999. Since quote currency is in EUR, exchange rate (0.656173 from SGD to EUR) must be applied to lookup record value.

 

150 SGD = 150 * 0.656173 = 98.42595 EUR per quantity

Since quantity = 2, 98.42595 * 2 = 196.95 EUR for total price

Figure 27 - Quote View for Sale Item
Figure 27 - Quote View for Sale Item
Figure 28 - Price Detail View of Sales Item
Figure 28 - Price Detail View of Sales Item

System administrator can define exchange rate with validity in master data management screen. Below figure shows how the exchange rate for SGD to EUR is defined.

Figure 29 - Maintain Exchange Rate
Figure 29 - Maintain Exchange Rate

3.5.2 Fetched Category

Use Case

Fetched Category is used when price calculation consists of fetching data/ retrieving from quote or configuration of sales item. Necessary data points used for the pricing step are maintained within the quote.

Example

Shipping cost is maintained as configuration of sales item. That shipping cost is added in sales item net price.

Figure 30 - Fetched Use Case
Figure 30 - Fetched Use Case

Sales representative configures sales Item by adding shipping fees in this example, the amount retrieved is part of sales item price.

As of Sales Platform Version 1902, fetched category can only retrieve configuration values. The fetched value + The quote currency will be used fetched price. in the other way, quote currency becomes configuration currency by default. If the system administrator wants to use currency from dynamic attribute (also known as DA currency), calcualted category is the right choice.

3.5.2.1 Create Pricing Step

Create a pricing step with price item type “Additional Price” whose price item type category is FETCHED.  Give the search expression “SalesItem().getDAValue(‘Shipping_Cost’)[0]”. In this case, Shipping_Cost is the dynamic attribute name.

Figure 31 - Fetched Pricing Step
Figure 31 - Fetched Pricing Step
3.5.2.2 How It Works

Let check on a Quote with two sales items. The main difference here is the first sales item does not have fetched price, but the second one does.

Figure 32 - Sample Quote for Fetched
Figure 32 - Sample Quote for Fetched
Figure 33 - Configuration value(s) for Sale Item
Figure 33 - Configuration value(s) for Sale Item
Figure 34 - Fetched Price Showing for Sales Item
Figure 34 - Fetched Price Showing for Sales Item

3.5.3 Calculated Category

Use Case

Calculated category is the combination of FETCHED and LOOKUP. In addition, it has the functionality of calculation on the top of these two price item type categories.

Example

Price is the multiplication of hourly rate and the hours need to build the sales item (maintained as a configuration of sales item.)

Figure 35 - Calculated Use Case
Figure 35 - Calculated Use Case
3.5.3.1 Create Pricing Step
Figure 36 - Calculated Pricing Step
Figure 36 - Calculated Pricing Step

Each of calculated steps has exactly one pricing component. Pricing step component defines how the price will be calculated and which currency will be used for pricing step. Since unit of measure is optional and does not have specific impact on IPE, administrator can leave it as default. However, currency expression does influence the result currency of price item for calculated step. Usually, currency expression is one of the three expressions:

  • Quote().hasCurrency[0] for quote currency
  • SalesItem().hasCurrency[0] for sales item currency
  • SalesItem().getDACurrency(‘DAName’)[0] for dynamic attribute currency whereas DAName is the dynamic attribute name.

Arithmetic expression is the place that we define how the price will be retrieved or calculated. Usage of arithmetic operators such as addition (+), subtraction (-), multiplication (*) and division (/) are supported in it.

Figure 37 - Creation of Pricing Step Component
Figure 37 - Creation of Pricing Step Component

The type of pricing step component are

1. Fetched
2. Lookup
3. Delta, which will be explained in Delta Pricing Component
4. Stepped which will use previous pricing step(s) of the sales item.

Figure 38 - Creation of Lookup Pricing Step Component (1)
Figure 38 - Creation of Lookup Pricing Step Component (1)
Figure 39 - Creation of Lookup Pricing Step Component (2)
Figure 39 - Creation of Lookup Pricing Step Component (2)
Figure 40 - Creation of Fetched Pricing Step Component (1)
Figure 40 - Creation of Fetched Pricing Step Component (1)

The following figure shows the creation of pricing step component with Stepped. The expression is mandatory field in step-based component. It must start with PricingStep followed by dot(.) and followed by pricing step sequence id that the administrator wants to use.

Sample expression, PricingStep.X where X is the sequence id of pricing step:

Figure 41 - Sample Stepped Component
Figure 41 - Sample Stepped Component
3.5.3.2 How It Works

In the below example, set up cost is calculated from the multiplication of Rate (which is from lookup table) and Hrs (which is from sales item configuration). The setup is already converted in Section Create Pricing Step.

Calculation step uses currency from the calculated component expression. However, till in 1902r, it does not consider currency conversion if variables inside pricing component have different currencies. It assumes all the variables has same currency. It only calculates the value with currency from calculated component expression.

Figure 42 - Sample Quote showing Calculated Pricing Step
Figure 42 - Sample Quote showing Calculated Pricing Step
Figure 43 - Fetch Hours from Configuration
Figure 43 - Fetch Hours from Configuration
Figure 44 - Lookup Rate from look table
Figure 44 - Lookup Rate from look table

3.5.4 Manual Category

Use Case

Sales representative gives discount or mark up (either percentage or cash amount) to a sales item with affected pricing date (also known as “Valid From Date” of price item). For example, seasonal discounts (such as Christmas discount) will be affected from target date (December) but before that, the discount is not applied yet. By this way, sales representative will be able to define discount at a predefined date.

Example

Sales representative gives 100 SGD discount to one of the sales items.

Internal Pricing Engine
Internal Pricing Engine
3.5.4.1 Create Pricing Step

Below figure show creation of pricing step. The price item type category is manual in this case.

Figure 45 - Manual Pricing Step
Figure 45 - Manual Pricing Step
3.5.4.2 How It Works
Figure 46 - Sample Quote Before Discount is Given
Figure 46 - Sample Quote Before Discount is Given
Figure 47 - Manual Discount of 100 EURO is giving to Sales Item
Figure 47 - Manual Discount of 100 EURO is giving to Sales Item

After discount is given, the discount amount is subtracted from the sales item net price and net value.

Figure 48 - Sample Quote After Discount Application
Figure 48 - Sample Quote After Discount Application

3.5.5  Subtotal Category

Use Case

Subtotal is the intermediate step to show meaningful pricing information in the user. The output price from subtotal category is neither part of sales item net price nor quote price.

Example

Sales representative wants to see sum of the product price and shipping cost in user interface as total cost.

Figure 49 - Subtotal Use Case
Figure 49 - Subtotal Use Case
3.5.5.1 Create Pricing Step

Below figure show creation of pricing step. The price item type category is subtotal in this case.

Figure 51 - Sample Quote with Subtotal Steps
Figure 51 - Sample Quote with Subtotal Steps
3.5.5.2 How It Works

Assume that shipping cost is retrieved by Pricing Step 2 and set up cost is retrieved by pricing step 3. In this example, arithmetic expression of subtotal step is “PricingStep.2 + PricingStep.3”, the sum of the result of pricing step 2 and pricing step 3 is shown in pricing step 5. However, the sales item net price does not include that subtotal price.

Figure 51 - Sample Quote with Subtotal Steps
Figure 51 - Sample Quote with Subtotal Steps

3.5.6 Aggregation Category

Use Case

Consider there is a sales item hierarchy. Administrator wants to find a specific pricing step of all sub sales items and sum up to get the output of aggregation category. The output price from aggregation category is not part of quote price.

Example

Breaker is composed of multiple components. Each of the components has its own set up cost. Sales representative wants to see sum of all the set-up cost of breaker’s components.

Figure 52 - Aggregation Use Case
Figure 52 - Aggregation Use Case
3.5.6.1 Create Pricing Step
Figure 53 - Aggregation Pricing Step (1)
Figure 53 - Aggregation Pricing Step (1)

Arithmetic expression is mandatory for aggregation category. It decides which pricing step that administrator wants to sum up. The syntax of arithmetic expression is “PricingStep” followed by dot(.), followed by pricing step sequence id. In the following example, pricing step 3 will be used to aggregate.

Figure 54 - Aggregation Pricing Step (2)
Figure 54 - Aggregation Pricing Step (2)
3.5.6.2 How It Works

The following figure show the sales item hierarchy. Each of sub line item has its own set up cost. In order to build parent line item “Assembly”, the total set up cost is the sum of its children’s set up cost.

Figure 55 - Sample Sales Item Hierarchy
Figure 55 - Sample Sales Item Hierarchy
Figure 56 - Individual Cost for Child Sales Item (1)
Figure 56 - Individual Cost for Child Sales Item (1)
Figure 57 - Individual Cost for Child Sales Item (2)
Figure 57 - Individual Cost for Child Sales Item (2)
Figure 58 - Aggregated Cost for Parent Sales Item
Figure 58 - Aggregated Cost for Parent Sales Item

3.5.7 Script Category

Script category is introduced in 1902 release. The purpose of script category is to make custom implementation with the use of groovy language.

3.5.7.1 Script Category
Figure 59 - Script Use Case
Figure 59 - Script Use Case

This will show the groovy script to be used for this price step. If administrator opens the groovy script drop down, it will show all the groovy script maintained in CPQ system which are intended for IPE usage. That means administrator can pre-write and publish the groovy scripts which can be used in the pricing step. The place to maintain this is explained in Figure 59.

Figure 60 - Script Pricing Step (1)
Figure 60 - Script Pricing Step (1)
Figure 61 - Script Pricing Step (2)
Figure 61 - Script Pricing Step (2)

Administrator can maintain all the groovy scripts used for IPE in master data management screen with the type of ”Internal Pricing – Custom Item Calculation”. Only the groovy script used for that type will be shown in pricing Step groovy script selection. Below is the groovy script from master data management screen.

Figure 62 - Maintain Groovy Script in Master Data Management Screen
Figure 62 - Maintain Groovy Script in Master Data Management Screen
3.5.7.2 How It Works

The output from custom implementation is price item base amount. On the top of that, the rest of price item type additional information such as Mandatory, Disabled, Applicable Product Types are still applicable and handled by the IPE.

Figure 63 - Output from Groovy Script Price Item Type
Figure 63 - Output from Groovy Script Price Item Type

3.6 Custom Implementation

From 1902 onwards, two extension points are ready for custom implementation of IPE.

1. Custom Implementation for a pricing step which is shown in detailed for (already covered in Script Category)

2. Custom Implementation for sales item net price, net value and quote price calculation.

Figure 64 - Groovy Script Place Holder for Sales Item Price Calculation (1)
Figure 64 - Groovy Script Place Holder for Sales Item Price Calculation (1)
Figure 65 - Groovy Script Place Holder for Sales Item Price Calculation (2)
Figure 65 - Groovy Script Place Holder for Sales Item Price Calculation (2)

3.7  Editing Answer data

Use Case

Delta pricing is also known as price change. The changes about price over time are saved into one lookup table and can be used as tracking purpose.

Price Item TypeNoStarted From
Offer Price2 SGD1 Jan 2018
Offer Price-1 SGD1 Mar 2018
Offer Price3 SGD1 Jun 2018
Offer Price4 SGD1 Aug 2018

In February, the offer price is 2 SGD. But in April, the offer price becomes 1 SGD (2 -1). In December, the cumulated offer price is 8 SGD.

In order to save delta price in look up table, administrator must indicate the table as delta price table by enabling “delta price” at the time of lookup table creation

Figure 66 - Delta Price Table Creation
Figure 66 - Delta Price Table Creation

The below picture shows the default fields created by the options that administrator selected.

The lookup fields “PRICE_ITEM_TYPE” and “DELTA_PRICE” are added as delta price table selection and “validFrom” and “validTo” are added as has validity optiion.

Figure 67 - Default Fields for Delta Price Table
Figure 67 - Default Fields for Delta Price Table

The price item type needs to indicate itself as “is Delta” if it is used for price change. The following picture shows creation of delta price item.

Figure 68 - Price Item Type Applied to Delta Price Table
Figure 68 - Price Item Type Applied to Delta Price Table

In order to create delta price item, the setting “Enables Delta Price Item Creation” must be on.

Internal Pricing Engine

Once the quote is in accepted state (everything is confirmed and got approval from superiors if existed any), administrator can save delta price in order to be used by next quote.

Figure 69 - Sales Item having Delta Price
Figure 69 - Sales Item having Delta Price
Figure 70 - Delta Price Creation (1)
Figure 70 - Delta Price Creation (1)
Figure 72 - Delta Price Creation (3) - After Delta Price is Created
Figure 72 - Delta Price Creation (3) - After Delta Price is Created

Once delta price is created, it is saved to delta price table. However, it can be checked in two places, delta lookup table and product pricing. The below screen is the individual product page. In Product Pricing tab, administrator can see the different delta prices with validity date.

Figure 73 - Delta Price in Product Pricing
Figure 73 - Delta Price in Product Pricing
Figure 74 - Delta Price in Delta Table
Figure 74 - Delta Price in Delta Table

3.7.1 Delta Pricing in Pricing Scheme

In order to use delta pricing, administrator must use price item type of Calculated Category. The key difference is the component type is “Delta” and must choose lookup table and price item type to calculate the cumulative price.

Example:

In this example, the added fee has two different values with different validity date. 10 EUR from Feb 12 and -7 EUR from Mar 1.

Figure 75 - Delta Price with Two Different Validity
Figure 75 - Delta Price with Two Different Validity

The below picture shows the quote pricing date is 25 Feb. So only one record is applicable for delta price resulting in the cumulative added fee of 10 Euro.

Figure 76 - Delta Price with Different Pricing Date (1)
Figure 76 - Delta Price with Different Pricing Date (1)

The below picture shows the quote pricing date is 11 Apr. Now two records are applicable for delta price resulting in the cumulative added fee of 3 Euro. Hence pricing date has the effect on delta price.

Figure 77 - Delta Price with Different Pricing Date (2)
Figure 77 - Delta Price with Different Pricing Date (2)

4 Audit and Debug

Audit is essential to figure out the situation such as administrator suspects that price is not coming out correctly or price calculation is wrong or incomplete set up of pricing scheme. In order to do that, setting “Enable audit of Internal Price Engine” must be turn on from the administration master data management screen.

Figure 78 - Setting for IPE Audit
Figure 78 - Setting for IPE Audit

Audit file can be found under Content Management -> audit -> [today date]-> [quoteId] ->Internal_Pricing. The output audit file is html format.

Figure 79 - Generated Audit File Location
Figure 79 - Generated Audit File Location
Figure 80 - Sample Audit File (1)
Figure 80 - Sample Audit File (1)
Figure 81 - Sample Audit File (2)
Figure 81 - Sample Audit File (2)