Breadcrumbs

Optimization - Price Waterfall 1.1.0

This document summarizes major improvements and fixes introduced in the Price Waterfall Optimization Package release version.

Version

1.1.0

Release Date

Feb 16, 2023

Table of contents:

New Features and Improvements

Description

ID

You can set a boundary for Price List change.

PFUN-15024

Visual comparison of the satisfaction of the criteria between the current and optimized scenarios is available now.

PFUN-15588

It is possible now to filter the original data before the aggregation – by using an advanced filter in the Definition step.

PFUN-16310

Query tab has been renamed to Evaluation tab. In addition, its results display now as a table (instead of a dashboard).

PFUN-16756

There is a possibility to set a boundary for list price change for specific Price List to be able to properly steer the change of list price and adjust the price waterfall.

PFUN-16820

Drop-down lists with selectable values are available for inputs in the Evaluation tab.

PFUN-17028

Quantity is now computed directly with elasticity on the unit price defined by the revenue measure.

PFUN-17100

Optimization Price Waterfall Accelerator uses a faster and more flexible way to batch query the elasticities of every pair of product - customer (implemented in NG Accelerator).

PFUN-17161

The following elements have been renamed to reflect the current name of this accelerator:

  • Model class: from POAI to Price_Waterfall

  • Logics prefix: from POAI to PW_<step number>

  • Gitlab repository: from poai-accelerator to Optimization - Price Waterfall

  • package-definition files

  • pom.xml references

  • text in the readme file

PFUN-17988

In the Impact step, bubble charts have been removed as they were slow to load and were of limited use. 

PFUN-18712

Fixed Issues

Description

ID

Deltas for UnitInvoicePrice value finder thresholds are too large.

PFUN-16891

PO AI accelerator: User is unable to change mapping from the default setting if there is no segmentation model corresponding to the product group and customer group.

PFUN-16934

It is possible to choose any model for as an elasticity model. After the fix, only models fulfilling these conditions are available for selecting.

  • No condition on the MC name.

  • The model must contain a table called Segments.

  • The table Segments must contain a field called ElasticityParameters.

PFUN-16935

Product and Customer filters are not applied correctly when used together.

PFUN-18180

"Wrangled Data" has been renamed to "Aggregated". 

PFUN-18186