Forecast Lookup (PriceSettingConfig)

This configuration represents a single row of the PriceSettingConfig Price Parameter.

There are also other ways of reading Forecast; Lookup is only one of them.

Column

Value

Description

Column

Value

Description

Key

Forecast

Defines how to calculate the forecast.

Condition

  • Q1

  • Q2

  • Q3

  • Q4

If the current date matches this configuration row, the row is used. This is checked by the logic.

Type

Lookup

The logic will perform a lookup for the forecast from an external source.

Source

  • Datamart

  • Datasource

  • PX

Source type where the forecasts are stored.

Source Table

{name of the table with forecasts}



Source Field

{name of the column with the turnover}



Source Field 2

{name of the column with the quantity}



Source Field 3

{name of the column with SKU}

Only PX has a default SKU, so we require SKUs for all tables for consistency.

Source Field 4

{name of the column with the invoice date}

The forecast will always be fetched using only data with the "next year" filter applied on this column.

The column must be of the Date type.

Source Field 5

{name of the column with currency of turnover}

Turnover currency

Source Field 6

{name of the column with minimum value of aggregated data}

Only for pre-aggregated PX Source

Source Field 7

{name of the column with maximum value of aggregated data}

Only for pre-aggregated PX Source

Source Field 8

{name of the column with average value of aggregated data}

Only for pre-aggregated PX Source

Why This Lookup Is Not Standardized

  • Hierarchy works differently for Transaction data (it goes down for all sub-levels of dependency, instead of working as fallback).

  • A lot of data will be returned for a given time period, there is a "date overlap" issue.

  • Lookup manager supports api.stream calls, while transaction data might be stored in Datamart or Data Source.