Special Cases Lookups

Owned by Ondřej Tesař
Sept 30, 2024
1 min read

Actual Price

Technically, the Actual Price PX lookup is standardized. However, from the configuration point of view, the flow of data reading is non-standard when using PL and PG sources.

PL and PG do not use batching. PG is not even a lookup as such, since it reads data from the previous run of the same price grid.

Preference: Actual Price Lookup (PriceSettingConfig)

Transaction

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

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

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

Preference: Transaction Lookup (PriceSettingConfig)

Forecast

  • 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.

Preference: Forecast Lookup (PriceSettingConfig)

Competition Data and Strategy Conditions

While using Configurable Lookups, Competition Data and Strategy Conditions configurations are hardcoded in Groovy logic. These can be changed, but doing so will invalidate some of the wizards.