Lookup Engine can be used for any strategy that has a static price that needs to be fetched from an existing table, e.g. Promotion Price or Recommended Retail Price.
It utilizes additional filtering based on:
-
Target Date – Applied to "Valid From Field"/"Valid To Field" fields from the input configuration.
-
Additional Filter Values – Passed values are OR'ed together and applied to the "Additional Filter Field" field from the input configuration. By default in the Price Setting package it uses all not-null.
At the end, we get a result for a given SKU, within the given validity dates and matching additional filter.
Input Parameters
|
Input |
Type |
Description |
|---|---|---|
|
SKU |
String |
SKU of the calculated product. |
|
Target Date |
Date |
Date used for the ValidFrom/ValidTo filtering. |
|
Additional Filter Values |
List |
Used to pass values that will be used as additional filters.
|
Additional Engine Configuration
This engine needs an additional simple configuration Price Parameter where all Configuration Options are present as keys.
|
Configuration Option |
Expected value |
Description |
|---|---|---|
|
Source Type |
Allowed values:
|
Defines where the data is kept. For the PP type the engine expects a MATRIX table (Value Type: MATRIX, MATRIX2, MATRIX3, or MATRIX4) with SKU in the “name” column. |
|
Source Table |
ExampleTableName |
Name of the data table. |
|
Source Field |
ExampleSourceField |
Name of the column that contains the price within the table. |
|
Valid From Field |
ExampleFromColumn |
Name of the Date type field. |
|
Valid To Field |
ExampleToColumn |
Name of the Date type field. |
|
Additional Filter Field |
ExampleAdditionalFilterColumn |
Name of the additional filter column. It can be any string that can match some data passed in the Additional Filter Values list. |
Default Strategy Calculation Parameters
SKU,TARGET_DATE,DEPENDENCY_INFORMATION_VALUES