Caching Lookup Results

The calculation logic contains multiple lookups from both raw user data (like Datamarts, Data Sources or Product Extensions tables) and calculation specific configuration in Price Parameters. Some of it is cached by default (e.g. sales and forecast data or configuration from Price Parameters), but some of is not. Especially configuration tables that are split based on "dimensions" which are described in Product Segmentation per Feature.

It depends on the granularity of the product segmentation and the number of products whether caching such a configuration helps the logic execution times.

To address this, you can use this option in Calculation Inputs:

By default it is switched off since it may impact the performance negatively (particularly in cases where the segmentation is big). This should be the first thing to check when looking for optimization.

In price list logics, in the “Config Lookups“ element you can see multiple lookups of the same information with different features.