Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Here you can find a list of mandatory and optional data for Accelerator Packages. It helps you identify what data you need from the customer to set up and configure the packages.

Accelerate Price Setting Package

For this package you could start with requirements for Core (Product Data) and at least mandatory data for one pricing strategy.

Type

Data

Fields

Mandatory for Use Case

Master Data

Products

  • SKU

  • Field(s) to be used as Lookup Key

Core

Technically SKU could be SKU, but this would probably make no sense - you could completely “skip” the lookup key concept by defining SKU as the only Lookup Key Dimension and configure everything with the “*” value

Product Cost

Mandatory:

  • SKU

  • Cost

  • Pricing Level Identifier (e.g. Country)

Optional

  • Validity Period

  • Currency

Cost+ Pricing Strategy

Margin Calculation / Margin Checks

Advanced Cost Definition

Per Advanced Cost type:

  • The same as Product Cost

  • Optionally, we can use SUM, AVG when we want to use multiple cost entries and combine them into one

Advanced Cost Module

Discount Structure

Discount Groups and Discount Values

Pricing on List Price → Net Price level

Exchange Rates

Currency and Conversion Rates

Dependent pricing in different currencies

Competition Data

Mandatory:

  • SKU

  • Competition Price

Optional:

  • Competitor Name

  • Validity Dates

  • Currency

  • Relevant Competition Definition

All Competition Based Pricing Strategies

Pricelist Data

  • SKU

  • Pricing Level (Country, Global, Channel, …)

Initial Prices

All checks and KPI regarding price increase

Pricing Strategy: Price Increase

Stock Data

  • SKU

  • Pricing Level Identifier (e.g. Country)

  • Stock

Optional:

  • Validity Dates

KPI Days of Cover (DoC)

DoC related Pricing Strategies

Product References

  • SKU

  • reference SKU

Pricing Strategies: Anchor Pricing, Attribute Based Pricing

BoM (Kit List)

  • SKU

  • Sub-Component SKU

  • Quantity

Pricing Strategy: Kit Pricing

Business Data

Plus for Product

  • Lookup Key

  • Plus %

Cost+ based Pricing Pricing Strategy

Price Increase

  • Lookup Key

  • Price Increase

Price Increase Strategy

Pricing relevant Attributes

  • Attributes in P/PX

  • Value Impacts of Pricing Attributes

Attribute Based Pricing Strategy

Pricing Level Adjustment

  • Pricing Level

  • Adjustment %

Dependent Pricing of Independent (e.g. Global Reference Pricelist → Country Pricelist)

Sales Forecast

  • SKU

  • Sales Volume

  • Forecast Date

  • Pricing Level Identifier (e.g. Country)

Optional:

  • Currency

Lookup Based Forecast (optionally, we can use Lookup Based or Transaction Based Forecast)

Transaction Data

Sales Data (Transactions)

  • SKU

  • Sales Volume

  • Sales Turnover (Sold Price)

  • Transaction Date

  • Pricing Level Identifier (e.g. Country)

Optional:

  • Currency (you need filled CCY DM when using CCY)

All KPI regarding “Sales History”

  • Historical Sales/Turnover

  • Forecast based on historical data

Accelerate CPQ Package

Type

Name

Fields

Mandatory

Master Data

Product

Core data

Customer

Core data

Product Extension

ProductCost

Mandatory:

  • SKU

  • Cost: defaults to attribute1

Optional:

  • Currency

  • Additional dimensions fields

Core data

Price List

Core data

Product Extension

  • PriceByCustomer 

  • PriceByCountry 

  • PriceByRegion 

  • PriceBySegment 

Mandatory:

  • SKU

  • Attribute1: customer mapping

  • Attribute2: cost

Optional:

  • Currency

Mandatory if the price of the product is not in the price list

Model Record

PriceOptimizer model

Mandatory:

  • Target price

  • Floor price

  • Stretch price

Optional:

  • Currency

Optional

Product Extension

PriceGuidance

Mandatory:

  • Target price

  • Floor price

  • Stretch price

Optional:

  • Currency

Optional

Product Extension

PriceCompetitors

Mandatory:

  • SKU

  • Competitor

  • Price

Optional:

  • Currency

Optional

Customer Extension

CustomerCashDiscount

Mandatory:

  • Customer ID

  • Discount

Optional

Price Parameter

StandardDiscount

Mandatory:

  • Customer ID

  • Dimensional keys

  • Discount

  • Value Type

Optional:

  • Currency

Optional

ExceptionDiscount

Mandatory:

  • Customer (key1)

  • Product (key2)

  • Discount (attribute1)

Optional:

  • Currency

Optional

Transaction Data

Sales data

Mandatory:

  • SKU

  • Customer ID

  • Quantity

  • Invoice price

  • Net price

  • Margin

  • Pricing data

Optional:

  • Unit price

  • Invoice ID

Optional

Accelerate Sales Insights Package

Type

Data

Fields

Use Case

Transaction Data

Sales Data (Transactions)

  • Unique Id (String)

  • Product Id (String)

  • Customer Id (String) - mandatory if customer master is deployed

  • Pricing Date (Date)

  • Invoice Price (Money/Number)

  • Gross Margin (Money/Number)

  • Quantity (Quantity/Number)

Optional:

  • Currency (you need filled Ccy Datamart when using currency)

  • UoM

  • Additional waterfall fields

You can add additional fields for your waterfall definition. Basically you can add every field that follows your pricing journey starting from the List Price and ending at the pocket price.

You can have different price points as well as adjustments. Note that in the example below the price points are in bold and have adjustments in between.

Typically you have items like:

  • List Price

  • Local Adjustments

  • Local Listprice

  • On-Invoice Discounts

  • Invoice Price

  • Off-Invoice Discounts

  • Net Price

  • Transaction Cost

  • Cost

  • Gross Margin

Other optional data (mandatory for specific dashboards):

  • Period Over Period:

    • List price

    • Net price

  • Regional Revenue and Margin:

    • Continent

    • Country

    • City / Region

Master Data

Product

  • Product Id

  • Product Name

  • Up to 30 custom attributes

The Product / Customer Masterdata is used for two scenarios:

Filtering and Dimensions.

Filtering allows you to define the Products/Customers you want to include in your analysis.

Typically you can include following fields for this reason.

Product:

  • Product hierarchy

  • Product Group

  • Brand

  • Product performance markers

    • Product Class

    • Competitive / Captive

    • Product Lifecycle

    • Basic / Premium Products

Customer:

  • Regional Data / Org Data

    • Country

    • Region

    • Sales Office

    • Sales Org

  • Customer performance markers

    • Loyalty

    • Size / Classification

The second use case is to define the Product/Customer aggregation to have a view on your portfolios from different angles.

You can find this aggregation in chart types like Pie Charts (definition of the “pieces” or Scatter Charts (band by).

Customer

  • Customer Id

  • Customer Name

  • Up to 30 custom attributes

Accelerate PO Package

(warning) Please note: Accelerate PO Package has very similar data requirements as Sales Insights Package. Just pay attention to the slightly different purpose of the Product/Customer attributes in the two packages. It is encouraged to deploy Accelerate Sales Insights Package first and include all Product/Customer fields that you will need for the segmentation right away.

You can use this Excel Template to get an idea what the data could look like:

Type

Data

Fields

Use Case

Transaction Data

Sales Data (Transactions)

  • Unique Id (String)

  • Product Id (String)

  • Customer Id (String) – mandatory if customer master is deployed

  • Pricing Date (Date)

  • Invoice Price (Money/Number)

  • Gross Margin (Money/Number)

  • Gross Margin Rate (needs to be added as a calculated field in Datamart after deployment. It is “Gross Margin / Invoice Price”)

  • Quantity (Quantity/Number)

Optional:

  • Currency (you need filled Ccy Datamart when using currency)

  • UoM

Transaction data is essential for price optimization process.

(warning) Product/Customer master data should be provided in a separate data structure if it is to be used in segmentation and deal guidance.

Master Data

Product

  • Product Id

  • Product Name

  • Up to 30 custom attributes

Product and Customer master data is used to drive the segmentation process.

Good examples for Product Dimensions are:

Product:

  • Product hierarchy

  • Brand

  • Product performance markers

    • Competitive / Captive

    • Product Lifecycle

    • Basic / Premium Products

Customer:

  • Regional Data / Org Data

    • Country

    • Region

    • Sales Office

    • Sales Org

  • Customer performance markers

    • Loyalty

    • Size / Classification

These Dimensions are used in the Optimization model to drive the segmentation of the model. Each segment will be optimized separately.

Try to add as many product attributes as possible to make sure the Machine Learning Algorithms can evaluate the most optimized segmentation tree.

Customer

  • Customer Id

  • Customer Name

  • Up to 30 custom attributes

Accelerate Customer Insights Package

Type

Data

Fields

Use Case

Master Data

Customer

Custom attributes (optional)

  • Active /Inactive Customers indentification

    • e.g. if CM.Attribute15 = “10” then the particular customer is considered active

  • Customer segmentation (any other data source can be used as well).
    For example, the segment can be defined by:

    • Country + Region

    • Customer Type + Customer Group

    • ….

Product

All the dimensions in the relevant Product Data Source (optional)

Customer Products Portfolio: Pricing and Selling Opportunities by Product Attribute:

  • Product Attribute defined by a user input, the filter items are loaded from the Data Source definition.

  • Used in Pricing Opportunities and Selling Opportunities portlets as a dimension (aggregation level).

Transaction Data

Sales Data (Transactions)

  • Unique ID

  • Customer ID

  • Customer Name

  • Product Id

  • Product Name

  • Pricing Date

  • Invoice Price

  • (Gross) Margin

  • Quantity

Core.

Accelerate Rebate Management Package

Type

Data

Fields

Use Case

Master Data

Product

  • Product Id

  • Optional: Up to 30 custom attributes

Customer

  • Customer Id

  • Optional: Up to 30 custom attributes

Transaction Data

Sales Data (Transactions)

  • Product Id (String)

  • Customer Id (String)

  • Baseline Value (In most cases, it will be a Revenue/Invoice Price) (Money)

  • Quantity (Quantity)

  • Pricing Date (Date)

  • Rebate (this field is used to allocate a rebate value into the transaction Datamart) (Money)

Accelerate Rebate Dashboard Package

Type

Data

Fields

Use Case

Master Data

Product

  • Product Id

  • Optional: Up to 30 custom attributes

Customer

  • Customer Id

  • Optional: Up to 30 custom attributes

Transaction Data

Sales Data (Transactions)

  • Product Id (String)

  • Customer Id (String)

  • Baseline Value (In most cases, it will be a Revenue/Invoice Price) (Money)

  • Quantity (Quantity)

  • Pricing Date (Date)

  • Rebate (this field is used to allocate a rebate value into the transaction Datamart) (Money)

  • Margin (Money)

Rebate Records (Rebates module)

  • Current Baseline Value

  • Current Quantity

  • Current Rebate

  • Forecast Baseline Value

  • Forecast Quantity

  • Rebate Forecast

  • Accrual Forecast Baseline Value

  • Accrual Forecast Quantity

  • Accrual Forecast

Rebate Agreement output name (Rebates module)

  • Payment Period

  • Target For

  • Rebate Formulas

  • Customer Group

  • Product Group

PricefxPlasma

Type

Data

Fields

Use Case

Transaction Data

Sales Data (Transactions)

  • Currency

  • Customer ID

  • Document ID

  • Document Line ID

  • Global List Price

  • Gross Margin

  • Invoice Price

  • Local List Price

  • Net Price

  • Pricing Date

  • Product ID

  • Product Or Service

  • Quantity

  • Realized Price

  • Selling From

  • Selling To

  • UOM

  • Unique ID

Optional:

  • Competitive Discounts

  • Consignment Cost

  • Corrections

  • Customer Loyalty Program

  • Customer Negotiated Discounts

  • Customer Pickup Allowance

  • Customer Charge Customization

  • Customer Charge Installation

  • Customization Charges

  • Customization Costs

  • Early Payment Discounts

  • End Customer OffInvoice Discounts

  • End Customer OnInvoice Discounts

  • Entity

  • Expedited Shipping

  • Foreign Exchange Adjustment

  • Free Giveaways

  • Freight

  • Freight Charges

  • Installation Charges

  • Installation Costs

  • Instant Rebates

  • Inventory Maintenance

  • Labor

  • Local Adjustment

  • Marketing Development Promotions

  • OffInvoice Promotions

  • Other COGS

  • Other OffInvoice Discounts

  • Other OnInvoice Promotions

  • OtherTransaction Costs

  • Production

  • Quick Cash Payment Discounts

  • Raw Materials

  • Rebates

  • Receivables Carrying

  • Rush Orders

  • Sales Channel Discounts

  • Sales Rep

  • Seasonal Discounts

  • Slotting Allowance

  • Stocking Allowance

  • Support Cost

Transactions data is essential for Plasma Transactions core functionality.

Quotes

Quotes Data

  • Approval Processing

  • Approval Date

  • Denial Date

  • InGuideline

  • Boundary Price

  • Deal Date Time

  • Cost

  • Creation Date Time

  • Currency

  • Customer ID

  • Deny Step

  • Effective Date

  • Expiry Date

  • Invoice Price

  • Last Change By

  • Last Change Date Time

  • List Price

  • Margin

  • Mark As Lost Date Time

  • Needs Approval

  • Number O fApproval Steps

  • Product ID

  • Product Or Service

  • Quantity

  • QuoteId

  • Quote ID Without Revision

  • Quote Line ID

  • Revision

  • Revoke Date Time

  • Sales Person

  • Status

  • Submit Date Time

  • UOM

  • Workflow Status

  • Username

Optional:

  • Selling From

  • Selling To

  • Unique ID

Quotes data is essential for Plasma Quotes core functionality.

Selling To, SellingFrom and Unique ID are necessary in case Plasma Quotes Enrichment is applied.

Accelerate Sales Compensation

Type

Data

Fields

Use Case

Master Data

Product

  • Product Id

  • Optional: Up to 30 custom attributes

There are various ProductGroup inputs throughout the solution that require this data, e.g. during Plan creation or Adjustments.

Customer

  • Customer Id

  • Optional: Up to 30 custom attributes

There are various CustomerGroup inputs throughout the solution that require this data, e.g. during Plan creation or Adjustments.

Seller

  • Seller Id

  • Seller Name

  • Reports To

  • Pricefx User Account Id

Optional:

  • First Name

  • Surname

  • Active

  • Termination Date

  • Hire Date

  • Region

  • Market

  • Status

Seller data is essential for Sales Compensations core functionality.

Transaction Data

Sales Data (Transactions)

  • Baseline Value (in most cases, it will be Revenue/Invoice Price) (Money)

  • Invoice Price (Money)

  • Quantity (Quantity)

  • Margin (Money)

  • Seller Id (String)

  • Product Id (String)

  • Product Name (String)

  • Customer Id (String)

  • Pricing Date (Date)

  • Currency (String)

Transactions data is essential for Sales Compensations core functionality.

  • No labels