STOCK_DB_CONFIG

Name	PossibleValues	Description
Configuration for batch-abc
central-store-separately	0	Calculate central warehouses separately.
add-abs-value-redistribution-to-parent	0	Add absolute value of all children PLID redistribution to parent PLID redistribution.
add-abs-value-production-to-parent	1	Add absolute value of PLID of all products to PLID component.
overwrite-best-redistribution-abc-to-parent	1	Rewrite best ABC value from child PLID redistribution to parent PLID.
overwrite-parent-redistribution-abc-to-child	0	Overwrite ABC value from parent redistribution to all child PLIDs.
overwrite-best-virtual-abc-to-parent	1	Overwrite the best ABC value from virtual PLIDs to parent PLID from central warehouse.
overwrite-best-production-abc-to-component	1	Overwrite the best ABC value from product PLID to component / raw material PLID.
default-pcat-method-id	10	Id of a default method for ABC analysis (pcat method) throughout the system.
default-pcat-method-id-gui	10	Id of a default method for ABC analysis (pcat method) throughout the system. Used to keep the setting configured via GUI. During the computation, it will replace the default-pcat-method-id parameter.
add-abs-value-predecessor-to-successor	1	Add the absolute value of the predecessor to the absolute value of the successor.
pcat-accepts-ofc	1	ABC methods accept OFC.
pcat-accepts-sellout	1	ABC methods also include sale products.
borders-enabled	1	Whether ABC administration should allow to setup boundaries for ABC values.

Name	PossibleValues	Description
Configuration for batch-basestock
part-size-for-sporadic	1000	How many sporadic PLIDs are processed in one computation thread.
part-size-for-nonsporadic	3000	How many non-sporadic PLIDs are processed in one computation thread.
zero-basestock-when-ofc	1	If the product is marked as order_only_ofc, it automatically resets the basestock.
compute-without-promo	0	1 = history and forecast will be taken when calculating basestock without the effect of the promotion.
history-lenght-for-sporadic	12	How many months ago do we look into sales due to the calculation of smart basestock.
narrowing-enable	1	Vypnutí/Zapnutí vyhlazení basestocku. Možné hodnoty: 0/1.
last-month-fix-method	update	How to solve the fact that it is the first day of the month, we calculate with incrementals and in basestock_data we have counted last month that we do not want there. full = not incremental recalculation but full; reinsert = last month is erased anddelays have passed and the last month for all SKUs has beenshould be.
smart-ignore-dont-order	0	U sporadických položek vyřadí prodeje neobjednávaných plidů v relaci
smart-ignore-sellout	0	U sporadických položek vyřadí prodeje výprodejových plidů v relaci

Name	PossibleValues	Description
Configuration for batch-batch
inventory-compare-compute-days	0,1,2,3,4,5,6	Which days the batch-inventory-compare will be calculated. A comma-separated list of days of the week. 0 = Monday, 6 = Sunday.
inventory-compute-days	0,1,2,3,4,5,6	Which days the batch-inventory will be calculated fully.
sales-compute-days	0,1,2,3,4,5,6	Which days the batch-sales will be calculated fully.
basestock-compute-days	0,1,2,3,4,5,6	Which days the basestock will be calculated fully, not incrementally. 0 = Monday, can be separated by a comma more than one day.
smi-compute-days	0,1,2,3,4,5,6	Which days the batch-smi will be calculated. On other days the values from the last full recalculation will be used. 0 = Monday. The delimiter is a comma. If the SMI tables are empty, the recalculation will be realized in full mode regardless of this setting.
ordering-compare-compute-days	0,1,2,3,4,5,6	Which days the batch-ordering-compare will be calculated. Comma-separated list of days of the week. 0 = Monday, 6 = Sunday.
category-management-compute-days	0,1,2,3,4,5,6,7	Which days the batch-trend will NOT be calculated. A comma-separated list of days of the week. 0 = Monday, 6 = Sunday, 7 = all days will be calculated.
outliers-compute-days	0,1,2,3,4,5,6	Which days batch-outliers will be calculated in full mode. On other days, the outlier values will be retained as it was in the previous full recalculation. 0 = Monday. The delimiter is a comma. If there is no values in the Move table, the recalculation will be full regardless of this setting.
sale-set-compute-days	0,1,2,3,4,5,6	Which days the batch-sale-set will be calculared. On other days, the data from the previous full recalculation is choosen. 0 = Monday. The delimiter is a comma.
abc-compute-days	0,1,2,3,4,5,6	Which days the batch-abc will be calculated. Comma-separated list of days. 0 = Monday, 6 = Sunday.
trend-compute-days	0,1,2,3,4,5,6	Which days the batch-trend will be calculated. A comma-separated list of days of the week. 0 = Monday, 6 = Sunday.
db-cleanup-days	5	Which days should the database be cleanup (comma-separated list). 0 = Monday, 6 = Sunday. Additionally, it must be enabled in db_cleanup_configuration. Performs cleanUpForecastTables, cleanUpPriceHistoryTables, cleanUpSmiHistoryTables, cleanUpMoveTable, cleanUpPromoT.
import-repair-price-days	0,1,2,3,4,5,6	Which days the missing movement prices in the move table and the PLID prices in product_locator will be calculated. Comma-separated list of days of the week. 0 = Monday, 6 = Sunday.
forecast-and-safetystock-compute-days	0>0,1>0,2>0,3>0,4>0,5>0,6>0	Format: day> type, day> type, ... - day: 0 = Sunday, 1 = Monday, ... 6 = Saturday - type: -1 = incremental Forecast + incremental Safetystock (the fastest type, but does not capture minor changes) - type: 0 = full Forecast + full Safetystock (the longest and the most accurate) - type: >0 = number of best methods for full/non-incremental Forecast + full Safetystock (long) - example: 0>1: on Sunday, only calculate one method, full Safetystock - example: 1>-1: on Monday, run incremental Forecast and incremental Safetystock Note: Fast Adapt forecast and Promo Increment are calculated regardless from this setting

Name	PossibleValues	Description
Configuration for batch-dayshare
type	4	Allowed values {1,2,3,4}. Indicates how to calculate daily shares. 1 - Selects between SKUs (product_locator) own indexes and indexes from data aggregated via top_down binding. 2 - All SKUs get equal shares. 3 - All SKUs get indexes computed from data aggregated over category specified in dayshare_configuration.explicit-kategory. 4 - All above mentioned will be calculated and best values selected.
sale-days	1,2,3,4,5,6,7	Allowed values <1.7> separated by commas. Specifies the days of the week (1 = Monday, 7 = Sunday) for which the daily product_locator indices will be filled evenly at dayshare_configuration.type = 2 and / or when even indexes are assigned for better compatibility.
part-size	2000	Allowed values (0, ∞), usually 200 or 2000. Specifies in how big parts the work for .NET threads will be divided. A good guide when choosing this number is the size of the top_down groups / categories configured in the dayshare_configuration.explicit-category to avoid too big or too small chunks that may result in slowing the system down.
compute-days	0,1,2,3,4,5,6	Allowed values <0, 6> separated by a comma. Specifies the days of the week (0 = Monday, 6 = Sunday) for which the batch will not be incrementally optimized. During incremental optimization, the new product_locators will be assigned values according to the selected dayshare. The allowed.
explicit-category	AUTO	Allowed values is a comma-separated list of categories in the format cX_id, or the value AUTO. Combinations of the specified levels will be used to determine the affiliation of the product_locator to the categories, if the AUTO value is entered, all available will be used.
min-months	4	Allowed values (0, ∞). Specifies the minimum length of data in whole months with non-zero sales at which the series will be considered valid for the calculation of monthly indices.
min-weeks	8	Allowed values (0, ∞). Specifies the minimum length of data in whole weeks with non-zero sales at which the series will be considered valid for the calculation of weekly indices.
min-improvement	0.025	Allowed values <0, 1). Specifies the minimum rate of improvement of indexes for product_locator when moving to a higher level (even> category> top_down> product_locator.
min-sale-percentage	0.7	Allowed values <0, 1> Specifies the minimum ratio of sales and non-sales days in the last month (30 days) since the last non-zero movement, at which the product_locator / top_down / category starts to calculate its own index, up to this ratio the indexes will be assigned evenly.
max-days-without-sale	30	Allowed Values (0, ∞) Specifies the maximum day length of the product_locator / top_down / category without sales in which the own indexes will be calculated, after this time indexes will be assigned evenly.
history-limit	2	Allowed Values <1, ∞). Specifies in years the maximum length of the product_locator / top_down / category history (according to the dayshare_configuration.type setting). For example, if set to 2 and PwDate is 20.4.2015, the history 1.4.2013 - 1.4.2015 will be used.
christmas-analysis-enabled	0	Allowed values {0,1}. The variable enables Christmas analysis. If set to 0, Christmas analysis will not start.
easter-analysis-enabled	0	Allowed values {0,1}. The variable enables Easter analysis. If set to 0, Easter analysis will not start.
day-smoothing-enabled	1	Range of values {0, 1}. If set to 1, it allows the smoothing of the resulting daily indexes 25/50/25%.
day-index-zeroing-threshold	0	Range of values <0, ∞). Specifies an index value below which the index will be reset before smoothing.
day-smoothing-protection	5	Allowed values: <1, 7>, separated by commas. Specifies the days of the week (1 = Monday, 7 = Sunday) for which the value cannot be reduced by smoothing.
max-third-difference-constraint	0.2	Allowed values <0, ∞). If set to 0, disables constraint for third of the month values, constraints maximal difference between thirds of the month to the specified value otherwise.

Name	PossibleValues	Description
Configuration for batch-db_cleanup
db-cleanup-enabled	0	Indicates whether db-cleanup is enabled.
relevant-forecast-history-months-count	6	Indicates how many months of the forecast history from the current month should be retained in the db. Value = 0 means that it should be stored indefinitely.
relevant-move-history-months-count	36	Indicates how long (in months) should the move/transaction history be retained in the db. Value = 0 means that only the records of the current month are retained.
relevant-price-history-months-count	6	Indicates how many months of price history tables from the current month should remain in the db. Value = 0 means that all price_history_* tables except from the current month are deleted.
relevant-smi-history-months-count	6	Indicates how many months of SMI tables (slow moving inventory) can remain in db after the current month. Value = 0 means to delete all smi_month_ * and smi_default_data_ * tables except from the current month.
archive	0	1 = before deleting old data, this old data is archived to the archive database, which is defined in pwm as db_name_archive.
relevant-promo-history-months-count	36	Indicates how many months of history promotions from the current month should remain in the db.
cleanup-and-archive-period-for-move	full-month	Move cleanup period: full-month = if we want to keep eg 1 month of data, the whole last month will be saved plus what we have in the current month; full-year = if we want to keep eg 36 months of data, the whole last 3 years plus the current year are kept.
relevant-promotool-history-months-count	60	It indicates how many months the promotion from Promotool has to remain in db from the current month. Value = 0 means that all actions (and their data) except the current month will be deleted. Follows pt_header.delivery_date_to, ie. if the action extends to the period we want to keep, whole action is retained.
cleanup-and-archive-period-for-promotool	full-year	The period of promotion deletion from Promotool: full-month = if we want to keep eg 1 month of data, the whole last month will be saved plus what we have in the current month; full-year = if we want to keep, for example, 36 months of data, the entire last 3 years are retained plus the current year.
cleanup-and-archive-date-column-for-intelligent-orders	full-year	"History cleanup period for exports to SODI: full-month = if you want to keep, for example, 1 month of data, the entire previous month will be retained along with the current month's data; full-year = if you want to keep, for example, 36 months of data, the last 3 full years will be retained along with the current year."
cleanup-and-archive-period-for-promo	full-year	Cleanup period for promotions from promo_action: full-month = if you want to keep, for example, 1 month of data, the entire previous month will be retained along with the current and future months; full-year = if you want to keep, for example, 36 months of data, the last 3 full years will be retained along with the current and future years.
cleanup-and-archive-date-column-for-promo	promo_date_from	The date column from the promo_action table used for backup operations.
clean-forecasting-method-parameters-plid	0	Allow deletion of data from the forecasting_method_parameters_plid table for PLIDs that no longer exist. Enable by setting value = 1. Warning: enabling this may increase recalculation time.
relevant-intelligent-orders-history-months-count	24	Specifies how many months of export history to SODI, counting from the current month, should remain in the database
cleanup-and-archive-date-column-for-sodi	full-year	Cleanup period for export history to SODI: full-month = if you want to keep, for example, 1 month of data, the entire previous month will be retained along with the current month's data; full-year = if you want to keep, for example, 36 months of data, the last 3 full years will be retained along with the current year.
relevant-sodi-history-months-count	24	Specifies how many months of export history to SODI, starting from the current month, should remain in the database.

Name	PossibleValues	Description
Configuration for batch-fast_adapt
enabled	1	Range of values {0, 1}. Value 1 enables the calculation of the Forecast Fast adapt.
promo-days-tolerance	8	Range of values <0, ∞). How many maximum number of promotion days can be in the history in order to fast adapt evaluation (evaluation on PLID level).
zero-group-trim	1	Value range: {0, 1}. If set to 1, it allows trimming (grouping) of days with sales = 0 at the beginning of the observed period (days-to-history).
regression-grouping	7	Range of values <1, ∞). Number of days on which the data and regressions will be grouped in the fast adapt.
history-days	56	Range of values <1, ∞). Number of days of sale that will enter the fast adapt (rounded up to regression-grouping multiples).
forecast-days	28	Range of values <1, ∞). Number of days on which the regression forecast will be compared with the original forecast (rounded up to regression-grouping multiples).
change-ratio-up	0.5	Range of values <1, ∞). Percentage of the regression forecast that we will take as a new forecast when applying the fast adapt up.
change-ratio-down	0.5	Range of values <1, ∞). Percentage of the regression forecast that we will take as a new forecast when applying the fast adapter down.
down-evaluate-limit	80	Allowed values <0, ∞). Specifies in percent the minimum ratio between the PW forecast and the regression forecast, if PW predicts higher forecast, the fast-adapt will respond by lowering the forecast.
up-evaluate-limit	120	Allowed values <0, ∞). Specifies in percent the maximum ratio between the PW forecast and the regression forecast, if PW predicts lower forecast, the fast-adapt will respond by increasing the forecast.
lower-safetystock-enabled	0	Range of values {0,1}. Enable safetystock reduction according to change from fast-adapt.
zero-group-tolerance	3	Allowed values (0, ∞). If in the monitored period (days_to_history) there is a larger number of day groups (grouping) with sales = 0 than this setting, fast-adapt will be disabled.
increase-safetystock-enabled	0	Range of values {0,1}. Enable increase of safety stock according to the change from fast-adapt.
aggregation-type	0	Range of values {0, 1, 2}. Type of fast-adapt forecast aggregation. 0 = Not aggregated, each PLID is calculated individually. 1 = Aggregates according to the top_down_relation_accumulated table. 2 = Aggregates according to table fast_adapt_relation.
aggregation-lowering-type	2	Range of values {0, 1, 2}. Type of forecast decreasing when fast-adapt-aggregation-type> 0. 0 = All for root. 1 = Evenly. 2 = Proportionally according to the current forecast.
aggregation-increase-type	0	Range of values {0, 1, 2}. Forecast increasing type when fast-adapt-aggregation-type> 0. 0 = All for root. 1 = Evenly. 2 = Proportional to the current forecast.
ignore-cleaned-up-plids	1	Allowed values {0, 1}. If set to 1, the fast-adapt will ignore the months in which it was set by the user to clear the forecast.
days-with-supply-limit	20	Range of values <0, 100>. In percentages, the maximum number of days which can be in the stockout in order to fast-adapt evaluation (on PLID level).
change-ratio-super-FA	1	Range of values <0, ∞). Percentage from the regression forecast that we will take as a new forecast when applying the fast-adapt for new PLIDs.
moving-average-enabled	1	Range of values {0, 1}. If set to 1, sales smoothing is enabled in fast-adapt using moving average.
adaptive-slope-enabled	0	Field of values {0, 1}. If set to 1, enable the evaluation of the trend change within the fast adapter from ascending to descending and will prefer a shorter part of the data (descending).
normalization-zero-level	1e-6	Value range: <0, ∞). Specifies the threshold of the index used for normalization based on daily distribution (day-share, season-indices, Easter, and Christmas), below which the input sales will be set to zero instead of being divided.
minimum-smoothing-enabled	1	Range of values {0, 1}. If set to 1, add half the difference between the lowest sale and the second lowest sale to the lowest sale.
normalization-index-minimum	0.33	Range of values (0, ∞). Specifies the minimum value of index for normalization according to the daily distribution (classically day-share or christmas / easter). For example, a value of 0.33 means that the sale will be increased by a maximum of three times.
output-index-maximum	43587	Range of values (0, ∞). Specifies the maximum amount of the index for adjusting the output regression according to the daily distribution (classically day-share, or christmax / easter) and the seasonal index. For example, a value of 2.5 means that the regression will be increased by a maximum of 2.5x.
zero-group-first-sale-limit	0	Value range: <0, ∞). If set to a value > 0, it specifies the number of days from PwDate after the first sale (product_locator_first) during which the zero-group-tolerance rule will be applied. If this period is exceeded, the rule will be ignored and Fast Adap will be calculated even if the group exceeds the limit.

Name	PossibleValues	Description
Configuration for batch-forecast
max-history-length	NULL	Maximum length of history in months. It can be NULL. The parameter is used in batch-history-for-forecast. !ATTENTION! additional restrictions for the length of history used in .net BatchForecast can be set in forecast_composite_configuration. More restrictive setting will be used!
batch-history-for-forecast-part-size	2000	Number of PLIDs in one thread in OLD calculation of batch-history-forecast. DO NOT use in the future.
middleout-explicit-category	c4_id	Middleout categories - c_id category lists separated by semicolons. Example: c3_id; c3_id, c4_id; c3_id, c4_id, c5_id
middleout-enabled	1	Range of values {0, 1}. Enable middleout forecast.
batch-forecast-part-size	200	Number of items (top-down trees) per thread in .NET forecast.
top-down-distribution-type	1	Range of values {0, 1, 2, 3}.The method of distribution of the accumulated top-down forecast on the PLIDs. 0 = FloorRoundAtChildren (rounding downwards), 1 = SmartRoundAtChildren (smart rounding, default), 2 = RoundAtChildren (ordinary rounding) 3 = DoNotRoundAtChildren (without rounding), 4 = ZeroAtChildren (set to zero)
irrelevant-history-cutoff-enabled	1	Range of values {0, 1}. Enabling irrelevant history cut-off.
seasonality-shifting-enabled	1	Range of values {0, 1}. Enable Moving seasonality in .NET forecast - used to capture the earlier onset of seasonality.
topdown-enabled	1	Range of values {0, 1}. Enable top-down.
memorize-forecast-continuous-enabled	1	Range of values {0, 1}. Enable memorization of forecast_continuous_errors_accumulated table in .NET forecast.
stockout-increase-forecast-in-history	1	Range of values {0,1}. If set to 1, lost sales are uploaded as a forecast input (stockout analysis must be allowed).
sellout-forecast-cutoff	1	Allowed values {0, 1}. If set to 1, the forecast of sales items will be reduced at the level of available stock.
topdown-history-length-for-ratio	12	Length of the history from which the ratio is calculated for TD purposes. Eg for retail it is good to calculate the ratio from the shorter history..
batch-day-variability-part-size	2000	Number of calculation units (product-locators) in one thread in .NET calculation of daily variability. (Usually hundreds or thousands.)
freeze-day	0	Range of values <1, 31>. The day of the month in which the forecast is freezed.
show-in-detail-screen	0	Allowed values {0, 1}. If set to 1, the graph of the best forecast will be displayed on the detail tab.
accept-ofc	0	Range of values {0, 1}. If set to 1, OFC will be added to the history for forecasting.
middleout-history-length-for-ratio	12	Length of history in months, from which the distribution between members of middleout groups will be calculated. (Usually between 3 and 24.)
middleout-ratio-smooth-coefficient	5	Allowed values <0, 1>. The value of the sales multiple of the last and next month of history, if exceeded, will be smoothed in the calculation of the decay ratio (only from below) more at https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Ratio-computation
middleout-ratio-slope-difference-coefficient	0.05	Limit value of the regression slope difference between full and half history, if it is exceeded, only a half of the available history will be used to calculate the middleout.
middleout-ratio-part-size	5000	Number of middle-out groups which will be calculated in one .NET thread. (Usually thousands or tens of thousands.)
top-down-ratio-smooth-coefficient	5	Allowed values <0, 1>. The value of the sales multiple of the last and next month of history, if exceeded, will be smoothed in the calculation of the decay ratio (only from below) more at https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Ratio-computation
top-down-ratio-slope-difference-coefficient	0.05	Limit value of the regression slope difference between full and half history, if it is exceeded, only a half of the available history will be used to the calculation of the middleout..
top-down-ratio-part-size	5000	Number of the top-down trees that will be calculated in one .NET thread.
middleout-default-type	5	Range of values {1, 2, 3, 4, 5, 6}. Default middleout behavior for all root top-down groups not listed in the table middleout_product_locator_settings. Range of values from the dial middleout_type, more at https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Nov%C3%BD_middleout
batch-forecast-day-week-part-size	2000	Number of PLID per computation thread for calculation of the day / week forecast in batch-forecast.php.
forecast-day-length	0	Number of days for calculation of daily forecast.
forecast-week-length	0	Number of days for calculation of the weekly forecast.
top-down-distribution-type-for-zero	0	Range of values {0,1}. Specifies how to distribute proportional sales for zeroed top-down elements. 0 = distribution between non-zero, 1 = all for top-down root.
middleout-new-product-history	PLID	Range of values: value PLID or number of months in history. The number of months in history that the product must go through in order to not to be considered as new product. Def. the PLID value takes information from the table product_locator.sellout_new_product_type_id.
number-of-months-to-view	18	Range of value (0, ∞). How many full forecast months should be displayed.
number-of-months-to-forecast	24	Range of value (0, ∞) For how many whole months sales are to be forecasted.
simple-forecasting-method-history-limit	0	After
top-down-ratio-seasonal-index-effect	1	Allowed values <0, 1>. Used to determine the weight of the seasonal index from the season_indices table to balance sales when calculating the ratio in the group. A value of 1 means the full effect of seasonal indices, 0 disables their loading. In the interval (0, 1) the effect is reduced relatively (0.2 means reducing by 20 %).
middleout-ratio-seasonal-index-effect	1	Allowed values <0, 1> are. Used to determine the weight of the seasonal index from the season_indices table to balance sales when calculating the ratio in the group. A value of 1 means the full effect of seasonal indices, 0 disables their loading.
zero-non-seasonal-forecast	0	Range of values {0, 1}. If set to 1, forecast for highly off-season months is deleted.
zero-non-seasonal-forecast-for-new-products	0	Range of values {0, 1}. If set to 1, for new products in strongly seasonal categories is used the seasonal index of the category and is reset the off-season forecast.
middleout-method-count	5	Range of values <0, ∞>. If set to> 0, setting limits the number of stored middleout methods for one middleout_description_id (combination of selected categories) to the X best.
rpc-forecast-methods-enabled	0	Value range: {0, 1}. Enables RPC forecasting methods.
gen-opt-initial-convergence-window	5	Value range: <1, ∞). Window in number of attempts used to evaluate optimization interruption.
gen-opt-initial-convergence-percent	0.5	Value range: (0, ∞). Minimum improvement in % over the initial convergence window required to continue the genetic optimization
gen-opt-tuning-enabled	1	Value range: {0, 1}. If set to 1, it enables subsequent genetic optimization of stored forecasting method parameters during each following forecast.
gen-opt-tuning-min	10	Value range: <1, ∞). Minimum number of genetic optimization iterations for an already optimized forecasting method.
gen-opt-tuning-max	10	Value range: <1, ∞). Maximum number of genetic optimization iterations for an already optimized forecasting method.
gen-opt-tuning-convergence-enabled	0	Value range: {0, 1}. If set to 1, it allows interruption of the optimization after tuning-min iterations if the fitness function value has not improved by at least tuning-convergence-percent within the tuning-convergence-window.
gen-opt-tuning-convergence-window	5	Value range: <1, ∞). Window in number of attempts used to evaluate whether optimization should be interrupted
gen-opt-tuning-convergence-percent	0.5	Value range: (0, ∞). Minimum improvement in % over the tuning-convergence-window required to continue genetic optimization.
gen-opt-initial-min	50	Value range: <1, ∞). Minimum number of genetic optimization iterations for a new forecasting method.
gen-opt-initial-max	50	Value range: <1, ∞). Maximum number of genetic optimization iterations for a new forecasting method.
gen-opt-initial-convergence-enabled	0	Value range: {0, 1}. If set to 1, it allows interruption of the optimization after initial-min iterations if the fitness function value has not improved by at least initial-convergence-percent within the initial-convergence-window.
batch-forecast-day-part-size	2000	Number of PLIDs per thread for calculating daily/weekly forecasts in batch-forecast.php.
top-down-default-zero	1	Default top-down setting for zero (0 - not set, 1 - set by zero).
top-down-ratio-computation-type	ADAPTIVE	Value range: {ADAPTIVE, SIMPLE}. ADAPTIVE evaluates all configurations regarding smoothing and history trimming, while SIMPLE uses the entire available configured history without smoothing.
middleout-ratio-computation-type	ADAPTIVE	Value range: {ADAPTIVE, SIMPLE}. ADAPTIVE evaluates all configurations related to smoothing and history trimming, while SIMPLE uses the entire configured available history without smoothing.
gen-opt-enabled	1	Value range: {0, 1}. If set to 1, it enables genetic optimization of forecasting method parameters.
accept-sale-internal	1	Value range {0, 1}. If set to 1, it adds sale_internal to the sales in the forecast.

Name	PossibleValues	Description
Configuration for batch-import
use-universal-import	1	Import data using universal-batch-import.
use-datareader-gui	1	Settings from Datareader GUI configuration are used to import data from the customer to the RAW database.
use-raw-to-udm-gui	0	Settings from Raw-To-Udm GUI configuration are used to convert data from RAW database to UDM (database import).

Name	PossibleValues	Description
Configuration for batch-order_acceptation
report-ordering	1	Range of values {0, 1}. If set to 1, comparison report of proposed and actual orders is enabled.
report-redistribution	1	Range of values {0, 1}. If set to 1, comparison report of proposed and actual redistributions is enabled.
ordering-tolerance-days	3	When pairing orders / suggestions / movements do not have to be dated exactly to the day. This parameter determines the tolerance of + -X days.
redistribution-tolerance-days	3	When pairing redistributions / suggestions / movements do not have to be dated exactly to the day. This parameter determines the tolerance of + -X days.
order-use-client-id	1	Range of values {0, 1, 2}. 0 = when pairing, it will not depend on who the goods were actually ordered from, 1 = preferably pair designs / orders / movements with the same supplier, then with a different supplier, 2 = pair only designs / orders / movements with the same supplier.

Name	PossibleValues	Description
Configuration for batch-order
stockout-lost-amount-rate	1	If the stock is below zero level, then if the setting is 1 => everything must be ordered (the whole amount below zero level). If x (x> = 0) => I will order x * what I am below zero level.
order-accept-ofc-delivery-date	0	Range of values {0, 1}. It the setting is set to 1, orders and other calculations accept the expected delivery date of the order (otherwise the order date will be used).
working-days-group-order	1	Range of values {0, 1, 2}. Setting of the working week for ordering - 1 => Mon-Fri, 2 => Mon-Sat, 0 => Mon-Sun. Applies only to a product with fixed period.
working-days-group-delivery	1	Range of values {0, 1, 2}. Setting the working week for ordering - 1 => Mon-Fri, 2 => Mon-Sat, 0 => Mon-Sun. Applies only to a fixed period product.
new-product-ordering	0	New products ordering (if they have disp = 0, fm = 0 and there is no proposal for them). 0 - obj is created for quantity 0, 1 - for quantity MOQ (pp.minimal_quantity), 2 - for quantity SET (package, pp.minimal_quantity_set). If the warehouse_product.new_product_order_amount is set, new_product_ordering_supply is preferred and this setting is ignored.
compute-order-amount-lasts-days	0	Range of values {0, 1}. If the setting is set to value 1, then AMOUNT_LASTS_DAYS calculation is enabled in order_suggested. It means the number of days for which the quantity proposed in the order is spent.
enable-leadtime-first-shift-redistribution	0	In abstract-order-method in loadProviders shifts leadtime_first, 0 = off, 1 = on, 2 = according to the accept_for_lt_first_shift flag in future_move (1 = accept, 0 = ignore)
enable-leadtime-first-shift-provider	1	see enable-leadtime-first-shift-redistribution
enable-leadtime-first-shift-production	0	see settings enable-leadtime-first-shift-redistribution + property ltFirstDisableClientCondForFM
special-preorder-moq-zero-only	0	Range of values {0, 1}. When to apply the MOQ to the promotion pre-purchase. 0 = always, 1 = only if we do not suggest anything.
special-preorder-use-expiration	1	Range of values {0, 1}. Should we consider the expiration date in case of pre-purchasing? 0 = no, 1 = yes.
max-stockout-index	720	Range of values {0, 1}. How long in advance will we deal with stockouts? The value is the number of days from today when the last stockout we are resolving can occur. 0 = off. Affects the number of proposed orders.
order-limit-include-special-preorders	1	Range of values {0, 1}. If the setting is set to value 0, then when adding orders at the order limits, promotions will not be added to the orders for today, ie order_suggested.special_preorder = 1.
back-redistribution-rounding-when-no-needed-supply	0	Range of values {0, 1}. If redistribution rounding is allowed (done in Access Rights) and at the same time a complete stock redistribution is proposed, if set to 0 here, quantity will not be rounded.
intelligent-rounding-amount-max-days-to-round-set	15	Maximum days of supply after delivery of the quantity rounded per package. If the maximum number is exceeded, quantity will not be rounded on given package (rounded on another or not rounded at all). See use-intelligent-orders-rounding access-right.
order-sporadic-accept-fastest-provider	0	Range of values {0, 1}. If it is set tovalue 1, then the sporadic products are always ordered from the fastest supplier. It could be combinated with setting promo_safetystock.ignore-sporadic-redistribution.
lower-safetystock-for-first-period-ratio	0.9	How much percent should the safetystock be reduced in the first period.
order-explanation-history-days-to-keep	0	How many days ago should order-explanation data be available. 0 = nothing is saved. The maximum limit is given by the setting in batch-order-history.
order-explanation-history-outlook	30	How many days from the date structure should be stored in db.
shorten-period-if-less-than-percent	0	Range of values <0, 1>. If it is > 0, then it determines up to what percentage between 2 ordering days we prefer to order earlier. Details: https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Objedn%C3%A1vky
respect-provider-leadtime-for-delivery	0	Allowed values {0, 1}. If it is set to value 1, then when calculating delivery days the set leadtime of the supplier will be respected - eg 0> 1 with a leadtime of 7 days will mean delivery until Tuesday of the next week, not on the second day.
leadtime-compute-settings	0,2	Allowed values {0, 1, 2, 3}. Setting how to calculate leadtime. Values are separated by commas. 0 = via product_locator_id and supplier, 1 = via user settings in the leadtime_group_relation table, 2 = via product_id and supplier, 3 = via supplier.
min-purchase-count-for-leadtime	1	Setting of the minimum number of purchases.
intelligent-rounding-amount-max-days-to-round-moq	30	Allowed values {0, 1}. Maximum stock endurance after delivery of the rounded quantity to moq in days. If the maximum endurance is exceeded, it is not rounded to the moq (it is rounded off the package or not rounded at all). See right use-intelligent-orders-roundingmoq.
intelligent-rounding-force-round-to-moq	0	Allowed values {0, 1}. 1 = Force rounding on moq toregardless of the inventory life after delivery of moq. Used in the evaluation of profitability, the use-intelligent-orders-right must be turned on.
intelligent-rounding-force-round-to-min-set-from-provider	0	Allowed values {0, 1}. 1 = Force rounding to the smallest package regardless of the endurance of the stock after delivery of the package for PLIDs loaded by the supplier. Used for profitability evaluation, the use-intelligent-orders-right must be turned on.
intelligent-rounding-force-round-to-min-set-from-other-source	0	Allowed values {0, 1}. 1 = Force rounding to the smallest package regardless of the endurance of the stock after delivery of the package for PLIDs loaded with redistribution or production. Used for profitability evaluation, the use-intelligent-orders-rounding right must be enabled.
supplier-and-order-administration-v2	1	Allowed values {0, 1}. Enable (1) or disable (0) the use of the periodic orders module: https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Admin-periodical-ordering
intelligent-rounding-enabled-from-udm	0	Allowed values {0, 1}. 1 = Profitability evaluation rounding is turned on from udm. Do not set with a differential, udm will overwrite it. Independent of udm, you can enable by the use-intelligent-orders-rounding right.
intelligent-rounding-use-moq-as-set	0	Takeas a multiple and round to MOQ similar to packaging. Used only for profitability evaluation, the use-intelligent-orders-rounding right must be enabled.
alternative-supplier-gui	0	Allowed values {0, 1}. 1 = enable, 0 = disable. Setting of the possibility of displaying alternative suppliers in the orders GUI. More information in the wiki -> Display of alternative suppliers https://wiki.logio.cz/bin/view/planning-wizard/pw-tech-doc/Zobrazen%C3%AD_alternativn%C3%ADch_dodavatel%C5%AF
allow-nonpreferred-providers	0	Allowed values {0/1}. 1 = Enables support for the use of non-preferred suppliers under favorable conditions. See getBestProviderForStockout in order-method-normal.
ignore-leadtime-first-greater-than	0	Range of values: [0..∞), the value is in percent. Specifies the threshold from which leadtime_first is no longer extended until the first future move is delivered. Percentages express a multiple (leadtime + std) by which the leadtime can be extended as much as possible. More on the wiki: h
back-redistribution-gui-limitation	potential	How much quantity can be added to the reverse distribution cart. Options (default potential): potential = most overstock from the source PLID, available-supply = most available stock from the source PLID, none = no limitation, it is possible to give any quantity.
back-redistribution-gui-show	potential	Setting of the display of source PLID in the table of potential back redistributions. Options (default potential): potential = only PLIDs that have an overstock are displayed, available-supply = PLIDs that have an available inventory are displayed, all = all are displayed.
periodical-ordering-only-working-days	0	Allowed values {0/1}. 1 = Set the order days to working days only.
back-redistribution-basket	0	Allowed values {0/1}. 1 = Turns on the functionality of "reverse redistribution basket".
disabled-suppliers-at-the-bottom-gui	0	Allowed values {0/1}. 1: Suppliers with the setting enabled = 0 are displayed in the list below under active suppliers. It is a view in showhide of product detail - information about suppliers.
back-redistribution-potential-suggest-target	0	Allowed values {0/1}. 1 = The report of Overstock identification shows suitable warehouse for redistribution.
back-redistribution-potential-suggest-on-level	0	Allowed values {0/1}. 1 = The report of Overstock identification is looking for a suitable warehouse for redistribution only in the same warehouse category.
cancel-order-amount-real-to-amount-ratio	0	The ratio of amount real and amount at which we cancel the order. If the amount real <ratio * amount, we cancel the order.
cancel-order-amount-real-to-ss-ratio	0	The ratio of the amount real and safety stock at which we cancel the order. If amount real <ratio * ss, we cancel the order.
ordering-strategy	SS-P	Allowed values {SS-P, BS-BSMAX, MAX-MAX}. SS-P = After safety stock and stock intersection amount on period is ordered, BS-MAX = After blocked stock (stock + future move) and base stock intersection amount on base stock max is ordered, MAX = ?
return-first-found-order-index-for-delivery-index	0	Allowed values {0/1}. 0 = Returns the last possible order index for the specified delivery index. 1 = Returns the first possible order index for the specified delivery index.
disable-providers-with-zero-leadtime	0	Interval <0,1>. Default is 1. If set to 0, no action is taken. If set to 1, it sets the value enabled = 0 in the product_provider table where leadtime = 0..
order-limit-include-promo-orders	1	If set to 0, promotional orders (order_suggested.promo_action_id IS NOT NULL) will not be shifted within the Order Limits functionality.
order-limit-skip-groups-with-special-preorders	0	If set to 1, groups (client_order_limit) within the Order Limits functionality that contain a special preorder for a promo (order_suggested.special_preorder) on the current day are considered to automatically meet the limit (i.e., the limit is not checked for them).
promo-use-normal-method	1	If set to 1, the order method NORMAL will be enforced for all items in the promotion
order-limit-skip-groups-with-promo-orders	0	If set to 1, groups (client_order_limit) within the Order Limits functionality that contain a promo order (order_suggested.promo_action_id IS NOT NULL) for the current day are considered to automatically meet the limit (i.e., the limit is not checked for them).
order-limit-group-future-orders	0	The Order Limits functionality normally works by shifting orders for future days to the current day in order to meet today's limit. However, this means that the limit is not met for the future days. By enabling this configuration, orders will instead be shifted in a way that ensures limits are met for future days as well. WARNING: If this configuration is enabled, the value of client_order_limit.period_to_cover will always be treated as 1. For more details, see the chapter 'Issue of Order Limits for Future Days'
disable-providers-with-high-price	0	Interval <0,1>. Default is 0. If set to 0, no action is taken. If set to 1, it sets the value enabled = 0 in the product_provider and product_locator tables where the purchase price is higher than the selling price.
default-leadtime-when-zero-leadtime	0	Default is 0. If set to 0, no action is taken. Otherwise, this value is used as the lead time (LT) to be assigned to the supplier if the resulting LT is 0.
wacc-price-round-to-dec-if-lesser-than	30	Default is 30. WACC value above which the WACC price is rounded to whole numbers.
stockout-provider-price-weight	2	"Value ≥ 1. Specifies how many times the lead time (LT) must decrease relative to the price increase. With a value of 1, the percentage increase in price must match the percentage decrease in LT. With the default value of 2, a 10% price increase must be offset by at least a 20% reduction in LT
promo-days-before-end-to-lower	0	<0, ∞). 0: disabled. Number of days before the end of the promotion during which the promotional safety stock should start decreasing linearly to zero.
basestock-order-on-min	0	0 – stock must be less than the minimum to trigger an order; 1 – stock must be less than or equal to the minimum to trigger an order
zero-safetystock-when-zero-forecast	1	Allowed values: {0/1}. If $enableForceZeroForecast is enabled and the forecast is zeroed out, then based on this configuration, the safety stock (SS) will also be zeroed. See abstract-order-method::loadDataInner.
increase-reserve-by-order-instantly	0	Specifies whether the stock should be increased by the order quantity on the day of receipt. This setting can also be configured individually for specific PLIDs in order_configuration_product_locator.
increase-reserve-by-future-move-instantly	0	Specifies whether the stock should be increased by the amount of the future move on the day of receipt. This setting can also be configured individually for specific PLIDs in order_configuration_product_locator.
decrease-reserve-by-forecast-instantly	0	Specifies whether the stock should be reduced by the forecast/OFC at the beginning of the day. This setting can also be configured individually for specific PLIDs in order_configuration_product_locator.
max-days-to-next-redistribution-suggested	999	Distribution of new product will be suggested in quantity defined in SIDI.warehouse_product, if there is no suggested distribution based on forecast in the future period (leadtime + this parameter). Default value is 999, meaning there must be no suggested order at all to create new product distribution suggestion
expiration-compute-bottom-up	0	If order is limited by expiration: 1 - rounding up is performed on previous order amount, 0 - rounding down is performed on amount computed by expiration limiter algorithm
partial-expiration-future-move	0	Allowed values {0/1}. Allows processing of partial expiration of future moves. Upon delivery, the expiration date is calculated and handled as batch/lot expiration. The expiration date is calculated according to the delivery date + expiration_days_for_orders.
partial-expiration-available-supply	0	Allowed values {0/1}. Allows processing of partial expiration of available supply. The expiration date is calculated by pwdate + expiration_days_for_orders. When enabled, records for batch/layer partial expiration are ignored.
new-product-next-order-min-days-after-first-possible-delivery	999	Order for new product will be suggested in quantity defined in SIDI.warehouse_product, if there is no suggested order based on forecast in the future period (leadtime + this parameter). Default value is 999, meaning there must be no suggested order at all to create new product order.
partial-expiration-available-supply-future-move-sale-out-days	1	partial-expiration-available-supply-future-move-sale-out-days
period-ss-recompute-type	1	Determines how to set period_ss (1) = LT (2) = period (3) = MIN(LT, period) (4) = SUM(LT, period) (5) = MAX(LT, period). If the period_ss is set in the Periodical ordering settings or in the SIDI, this setting is ignored for the given item.

Name	PossibleValues	Description
Configuration for batch-outliers
enabled	1	Range of values {0, 1}. Turns outliers evaluation on (1) and off (0).
sensitivity	3	Range of values {1, 3, 5}. Outlier detection sensitivity. 1 - smallest, indicates only very strong extremes in the off-season. 5 - the largest, also indicates small sales, even in the season.
aggregate-per-day	1	Aggregation of movements by days for movements from the same clients. It can cause even small movements being labeled as extreme, as they have been aggregated and judged along with larger movements. 0 - do not aggregate, 1 - aggregate.
outlier-group-definition	1	Range of values {0, 1, 2}. Determines the formation of aggregation groups on which the extremes are analyzed. 0 - by products, 1 - by PLIDs, 2 - by filled in table product_locator_group.
history-cutoff-enabled	1	Range of values {0, 1}. If set to 1, it allows truncation of irrelevant history in Outliers. Truncated movements will never be marked by automatic detection as extremes!
overdetection-enabled	1	Range of values {0, 1}. If set to 1, it captures the trimming of groups in which too much movement would be cleaned (according to the sensitivity max: 1 - 10%, 3 - 20%, 5 - 30%), or according to the overdetection-percentage-override setting.
min-moves	10	Range of values {3, ∞}. Specifies the minimum number of movements after which the full Outliers algorithm will be used. Until then, a simplified version will be used, outliers in the group do not count at all for 3 moves!
overdetection-percentage-override	0	Range of values <0, 1>. The percentage value if the setting is> 0 will be used when comparing the ignore-overdetected-enabled mechanism instead of the classic 0.1, 0.2, 0.3.
threshold-force-ratio	3	Range of values (1, ∞). If the movement will be X times greater than the used threshold, it will be cleaned despite the insufficient error component in the month.
maximal-error-to-outlier-ratio	0.4	Range of values (0, 1>. A setting that determines how many% of outliers can cut to a quantity that was not originally marked as an error in order to crop the detected motion. Formula (error caused = current error - amount of motion) if abs (caused by error
use-old-stl-decomposition	0	Range of values {0, 1} If set to 1, the original STL decomposition is used in the outliers without linking to global seasonality
include-outlier-ids	NONE	Range of values {ALL, NONE, comma-separated values}. Affects which movements marked as outliers will be sent to .net. ALL - all moves, NONE - only outlier = 0, or enumeration of allowed values from the field outlier.
regression-months-before	3	Value range: <0, ∞). Maximum number of months before the promotion from which the average sold quantity within the promotion will be calculated for the purpose of decomposition balancing. The surrounding period will be divided into three parts, and the smallest one meeting the sale-threshold condition will be used
regression-months-after	3	Value range: <0, ∞). Maximum number of months after the promotion from which the average quantity sold during the promotion will be calculated for the purpose of decomposition balancing. The surrounding period will be divided into three parts, and the smallest one meeting the sale-threshold condition will be used
regression-sale-threshold	0.6	Value range: <0, 1>. Minimum ratio of days with sales to the total number of days required to select a shorter period for calculating the quantity from surrounding values, based on the months-before and months-after settings.

Name	PossibleValues	Description
Configuration for batch-promo_baseline
relevant-promo-distance	1095	Maximum relevant (daily) distance between historical promotions and the target promotion in promo-prediction. Historical promotions that are too far away are penalized according to the penalty-out-of-distance parameter.
relevant-seasonal-distance	90	Maximum relevant seasonal distance between historical promotions and target promotion in promo-prediction. Historical off-season promotions are penalized according to the penalty-out-of-season parameter.
relevant-discount-difference	20	The maximum relevant distance between the discounts of historical promotions and the discount of the target promotion in the promo-prediction. Historical promotions with too different a discount are penalized according to the penalty-large-discount-difference parameter.
relevant-length-ratio	43556	Maximum relevant distance between the lengths of historical promotions and the length of the target promotion in the promo-prediction. Historical promotions with too different length are penalized by penalty-large-length-ratio.
penalty-out-of-distance	0.2	Penalty on historical promotions that are too far away from the target promotion in the promo-prediction.
penalty-out-of-season	0.5	Penalty on a historical promotion that is out-of-season relative to the target promotion in the promo-prediction.
penalty-large-discount-difference	1.0	Penalty of the historical promotion of which the discount is too different from the discount of the target promotion in the promo-prediction.
penalty-large-length-ratio	1.0	Penalty on a historical promotion whose length is too different from the length of the target promotion in the promo-prediction.
relevant-close-nonpromo-distance	60	Maximum relevant (daily) distance between training non-promotional intervals and the target interval when calculating the promo baseline. Intervals that are not promotional or are too far away are penalized according to the penalty-close-nonpromo parameter.
penalty-close-nonpromo	0.1	Penalty for training intervals that are either promotional or too far from the target interval.
minimal-percentual-discount-for-nonpromo-sale	0	IMPORTANT! Minimum discount (percentage) for non-promotional sales. On some projects where most sales are promotional, non-promotional sales are often just a symptom of a missing promotion. In this case, we also assign a minimum discount to non-promotional sales, which then ensures that these non-promotional sales do not unnecessarily increase the baseline. The higher this minimum discount, the less the non-promotional sales will increase the baseline, and the lower the baseline will come out.
minimal-percentual-discount-for-promo-sale	0	IMPORTANT! The minimum discount (in percentage) for promotional sales. On some projects where most sales are promotional, it is sometimes convenient to consider a minimum discount for promotional sales, because promotions with too low a discount are often not sufficiently discounted. The higher this discount, the more sales we are able to explain as a consequence of the discount, and the lower the baseline comes out.
maximal-percentual-increase-per-discount-point	5	IMPORTANT! The maximum percentage increase in increment (relative to the baseline) per 1 percent discount. This parameter de-facto upper bounds the amount of promo-increment (relative to the baseline) that we can explain as a consequence of the discount. The higher the value of this parameter, the more sales we are able to explain as a consequence of the discount, and the lower the baseline comes out.
promo-action-padding-days-left	0	The number of days we want to shift the left edge of the baseline promotion.
promo-action-padding-days-right	0	The number of days we want to shift the right edge of the baseline promotion.
merge-predecessors-successors-enabled	0	Allowed values {0, 1}. If it is set to 1, SKUs will be inserted into the merge_sales_relation table under promo-analysis-v2 according to the predecessor's successor session. These sessions are then used to accumulate sales within the .net batch.
merge-top-down-relation-enabled	0	Allowed values {0, 1}. If set to 1, all SKUs in the top-down relation will be inserted into the merge_sales_relation table in promo-analysis-v2 (including top-down relations gained from predecessors and successors if enabled). These sessions are then used to accumulate sales within the .net batch.
promo-analyse-max-promo-action-length	122	Maximum length of a promotion in days, which can be considered in the promo analysis.
promo-analyse-reimport-promo-sales-table-days	0,1,2,3,4,5,6	Allowed values {0, 1, 2, 3, 4, 5, 6}. Indices of the days when the whole promo_sales table is to be filled again. On other days it will be filled incrementally. The separator is a comma, 0 - Sunday, 6 - Saturday.
promo-analyse-save-real-amount	2	The way to save calculated values into result columns (increment, baseline, total) of promo_action table (default = 2). 0 -> overwrite nothing, 1 -> overwrite total, overwrite baseline, calculate increment as total - increment, 2 -> overwrite all
minimal-percentual-increase-per-discount-point	0	Value range: <0, ∞). Likely important as well! Minimum percentage increase in increment (relative to baseline) per 1 percent of discount.
minimal-percentual-baseline-factor	0	<0, 100>. Ultra super important!! All days of any promotion will be guaranteed at least this percentage of the baseline compared to the total sales.
maximal-percentual-baseline-factor	100	<0, 100>. Ultra super important!! All days of any promotion will be guaranteed at most this percentage of the baseline compared to the total sales.

Name	PossibleValues	Description
Configuration for batch-cannibalization
enabled	1	Obor hodnot {0, 1}. Zapíná počítání kanibalizace.
part-size	100	Obor hodnot (0, ∞). Počet skupin, které se mají počítat na jednom threadu.
save-to-forecast	0	Obor hodnot {0, 1}. Zapíná ukládání odhadů budoucí kanibalizace do forecastu.
save-to-history	1	Obor hodnot {0, 1}. Zapíná narovnání prodejů o odhad historické kanibalizace.
min-length	5	Obor hodnot <0, ∞). Minimální délka promoakce pro kterou může být spočítán kanibalizační efekt.
max-length	31	Obor hodnot <0, ∞). Maximální délka promoakce pro kterou může být spočítán kanibalizační efekt.
max-overlap	0.25	Obor hodnot <0, 1>. Nejvyšší poměr počtu dní k délce promoakce ve kterém může být kanibalizovaný produkt také v promoakci a může být spočítán kanibalizační efekt.
min-confidence	0.5	Obor hodnot <0, 1>. Minimální jistota pro zohlednění historické kanibalizace.

Name	PossibleValues	Description
Configuration for batch-promo
promo-analyse-enabled	1	Range of values {0,1}. If it is set to 1, promo analysis will be calculated.
promo-prediction-enabled	1	Range of values {0,1}. If it is set to 1, promo prediction will be calculated.
promo-prediction-save-to-forecast	1	Range of values {0,1}. If it is set to 1, the results from promo-prediction will be saved to forecast.
post-promo-effect-enabled	0	Range of values {0, 1}. If it is set to 1, post-promo effect will be calculated.
post-promo-effect-compute-length	0	Range of values {0, 1}. If it is set to 1, the lenght of the post-promotion effect will be calculated. If it is set to 0, the value `post-promo-effect-default-length` is used as the lenght of the post-promotion effect.
post-promo-effect-default-length	14	The default length of the post-promotion effect in days.
post-promo-effect-max-length	14	The length of the maximum post-promotion effect in days. Indicates the number of days since the end of the event during which post-promo candidates are sought. If `post-promo-effect-compute-length` is off,` post-promo-effect-default-length` will be set regardless of this setting.
report-promo-detail	0	Range of values {0,1}. If it is set to 1, promo detail report is shown. Designed for promo-analysis-v1.
report-promo-evaluation-on-detail	1	Range of values {0,1}. If it is set to 1, promo evaluation in detail report is shown. Designed for promo-analysis-v2.
report-promo-evaluation	1	Range of values {0,1}. If it is set to 1, promo evaluation report is displayed in quick reports.
promo-prediction-overlapping	1	Range of values {1, 2, 3}. How to calculate overlapping promotions in promo-prediction (default = 1). 1 = The effects of the overlapping parts are added together, 2 = We take the maximum effect in the overlapping parts, 3 = We shorten the right edge of all overlapping promotions.
copy-promo-from-past-to-future	0	Increase forecast by promotions from the past (0 = off, 1 and more: fd.outlook, from which it will increase amount_promo based on the past. Overwrites only increment according to the increment of the sale_month table of the given month last year)
fast-adapt-enabled	1	Range of values {0,1}. Enable (1)/ disable (0) calculation of promo-fast-adapt.
fast-adapt-promo-days-running	3	How many days must the promotion be running to take effect in the adaptation.
fast-adapt-minimal-difference-ratio	0.1	Range of values <0, 1>. How many percentages must historical daily sales and proposed daily sales differ in order for the value to be overwritten.
promo-prediction-running	1	Range of values <1, 2>. The decay type of the currently running promotion during promo-prediction (default = 1). 1 = The whole promotion will be broken down according to the split into the whole period, 2 = The rest of the promotion, which has not yet been sold, will fall apart, from today to the end of the promotion.
promo-prediction-share-split-type	4	1: FIRST DAY: RUN-the rest of theuntil the current day. NERUN-whole promo on the first day, FA-IGN 2: UNIFORM: evenly throughout the promotion. FA-AKC, RUN-AKC 3: USER: according to promo_user_split. RUN-IGN, FA-AKC. 4: AUTO: dayshare based on min., RUN-IGN, FA-AKC
promo-prediction-dayshare-type	0	Range of values {0, 1, 2}. Setting whether the dayshare breaks out of INCREMENT or TOTAL. 0: by split-type (FIRST DAY: TOTAL, other INCREMENT), 1: INCREMENT, 2: TOTAL. The default is 0. If TOTAL breaks down, it is also possible to add minus amounts.
promo-fast-adapt-use-share-indices	1	Range of values {0, 1}. If set to 1, it allows the use of disintegration indices for days when evaluating the sold quantity during an ongoing promotion. If set to 0, only the number of running days takes into the evaluation.
promo-prediction-use-month-indices	1	Range of values {0, 1}. If it set to 1, allows the use of indexes from forecast_history_month_share when calculating the share of days in the promotion effect. If it set to 0, it will use an even proportional distribution.
post-promo-save-to-history	1	Range of values {0, 1}. If it is set to 1, calculation and subsequent storage of historical antipostpromo in the tables sale, sale_month, [sale_week, forecast_history] is enabled (0 = disabled).
promo-report-important-date	auto_promo	Specifies which dates to display in the promotion report. Values range: {promo, delivery, auto, auto_promo, auto_delivery}. If auto, auto_promo, or auto_delivery is set, the batch can reset this value to auto_promo or auto_delivery (depending on which dates are more similar to tocompute). Values promo and delivery are not overwritten.
promo-compute-target-v2-log-enabled	0	The value range is {0, 1}. If it is set to 1, it enable logging of the computeTargetPromoActionPredictionV2 method (0 = disable).
batch-promo-baseline-v2-part-size	2000	Number of computational units (product-locators) in one thread in .NET compute of baseline v2.
batch-promo-history-share-part-size	2000	Number of computational units (product-locators) in one thread in .NET compute of promo-history-share.
batch-promo-training-promoactions-part-size	200	Number of computational units ( product-locators) in one thread in the calculation of training promotions..
batch-promo-prediction-share-part-size	200	Number of calculation units (product-locators) in one thread in .NET calculation of promo-prediction-share.
batch-promo-prediction-part-size	200	Number of calculation units (product-locators) in one thread in calculation of promo-prediction.
promo-prediction-share-retail-provider-enabled	0	The value range {0, 1}. If it is set to 1, calculation of promo-predictions (mainly promo-prediction-share) in the case of a retail supplier is enabled (0 = disabled).
promo-prediction-relation-enabled	0	The value range {0, 1}. If it is set to 1, the calculation of promo-prediction using promo-prediction-relation is enabled (0 = disabled).
fast-adapt-distribution-enabled	1	The value range {0, 1}. If it is set to 1, It allows redistribution of running amount based on promo-prediction-relation. Enable this parameter if you want the promo-fast-adapt to respond based on the total quantity sold in the promotion.
promo-prediction-share-relation-enabled	1	Range of values {0, 1}. Calculation of promo-prediction share using promo-prediction-relation. If it is turned off, a promo-prediction-share is calculated for every PLID separately. If it is enabled, it is calculated only for parent product-locators (PLIDs).
promo-prediction-training-weight-sum-threshold	2.0	Threshold of the sum of the training promotion weights in the prediction to limit their number. If the sum of the weights of the best training promotions exceeds this limit, and at the same time the minimum number of training promotions is exceeded, further promotions are ignorated.
promo-prediction-min-training-promoactions	40	The minimum number of training promotions required for prediction. If the real number is smaller, nothing is predicted.
promo-matrix-data-enabled	0	Range of values {0, 1}. If it is set to 1, precalculate the promo matrix for the future actions and save the result in the promo_matrix_data table. If it set to 0, precalculation is not realized.
batch-promo-prediction-tuning-part-size	100	Number of calculation units (tuning groups) in one computation thread in the calculation of promo-prediction-tuning.
promo-prediction-tuning-enabled	0	Range of values {0, 1}. Default = 0. If it is set to 1, tuning of promo-prediction parameters is enabled (0 = disabled)..
promo-prediction-tuning-validation-length	90	Length of the validation section of the history in days, from which we select validation historical promotions designed for parameter tuning.
promo-prediction-tuning-compute-days	0	Range of values {0, 1, 2, 3, 4, 5, 6}. Indices of days when tuning parameters in the promo-prediction should be calculated. The divider is a comma, 0 - Sunday, 6 - Saturday.
promo-prediction-tuning-validation-max	10	Maximum number of validation promotions per product locator.
promo-analyse-accept-promo-from-move-date-from		The date from which the promo_action_id from the moves will be accepted. Before this date, the promo_action_id will be found automatically. An empty value or a value that is not a date means that the promo_action_id from the moves is not accepted at all (default).
promo-prediction-increase-training-action-by-stockout	1	Range of values {0,1}. If it is set to 1, then the lost amount during the training promoaction will be added to its real sale and this sum will be used for prediction.
promo-prediction-share-training-copy-enabled	1	Range of values {0, 1}. Default = 1. If it set to 1, then only promo-prediction-share training promotions are copied from promo-prediction. Otherwise, training promotions are calculated separately for promo-prediction and separately for promo-prediction-share.
promo-prediction-type	2	Promo prediction type. Range of values {1, 2}. 1 = total amount prediction, 2 = promo increment prediction.
promo-prediction-result-backup-enabled	1	Range of values {0, 1}. If it is set to 1, then promo-prediction results are backed up to tthe backup tables. 0 = back up is not realized.
promo-prediction-result-backup-days	14	Number of days (in the past) for which we want to back up the results of the promo-prediction to the backup tables. Range of values {0, 1, 2, 3, ...}.
promo-prediction-result-backup-months	12	Number of months (in the past) for which we want to back up the results of the promo-prediction to the backup tables. Range of values {0, 1, 2, 3, ...}.
promo-analyse-save-full-amount-enabled	0	Range of values {0, 1}. 1 = Enable storing the total sold amount (total baseline) during the promotion in the promo_plid table. If the parameter is not enabled, the sold amounts are redistributed among the overlapping promotions according to the promo_action_id in the promo_sales table.
promo-action-group-by		Range of values {"", product_id, c1_id ... }. List of columns according to which we want to group PLIDs. Allowed columns are: product_id, all c_id. Empty string means do not group, i.e., each PLID is in its own group of size 1.
promo-product-minimal-sale-days	60	Number of days from the first sale after which the PLID can be identified as promo_product.
promo-product-evaluate-months	0	Number of months in which pl.promo_product will be detected. If 0 is specified, the entire history will be used.
promo-prediction-bias-correction-enabled	0	Range of values {0, 1}. If it is set to 1, enables the use of bias correction in prediction. 0 (default) = off, 1 = on. if it is set on, also promo-prediction-bias-correction-group-by setting must be set.
promo-prediction-bias-correction-group-by	c1_id	Range of values {c1_id, c2_id ...}. List of IDs from the locator (separate commas, without spaces), according to which the bias coefficient is aggregated. ! It is necessary to set this value when enabling bias correction!
compute-training-promo-actions-enabled	1	Range of values {0, 1}. Enables recalculation of training actions (default 1 = enabled). Practically never turn off, it turns off unnecessary calculations during verification.
compute-promo-prediction-share-enabled	1	Range of values {0, 1}. Enables calculation of the prediction share (default 1, on). Practically never turn off, it turns off unnecessary calculations during verification.
promo-prediction-2d-output-filter-enabled	1	Enables a "2d" filter of training actions by the output with respect to action length and discount. Assumption is that shorter actions and actions with smaller discount are less effective, therefore higher values are filtered more aggressively then in actions with bigger discounts. Weights are set in the promo_configuration_parameters table.
promo-prediction-trimming-bottom-min	0	Minimum number of training samples to be excluded from the calculation of statistics (median, deviation) from the bottom of the population.
promo-prediction-trimming-bottom-max	0	Maximum number of training samples to be excluded from the calculation of statistics ( median, deviation) from bottom of the population.
promo-prediction-trimming-bottom-percentile	0	Lower percentile of training samples which are excluded from the calculation of statistics (median, deviation). Number of deleted promotions is limited to min <percentile <max.
promo-prediction-trimming-top-min	0	Minimum number of training samples to be excluded from the calculation of statistics (median, deviation) from the top of the population.
promo-prediction-trimming-top-max	0	Maximum number of training samples to be excluded from the calculation of statistics ( median, deviation) from the top of the population.
promo-prediction-trimming-top-percentile	0	Upper percentile of training samples to be excluded from the calculation of statistics (median, deviation). The number of removed promoactions is min <percentile <max.
promo-matrix-discount-count	19	Number of different discounts in the promomatic. Default 19.
promo-matrix-length-count	31	Number of different lengths in the promomatic. Default 31.
promo-prediction-max-amount-history-length	0	Number of historical months from which the max amount will be calculated. If set to 0, the entire history is taken from the forecast_history. Default 0.
fast-adapt-max-increase-ratio	0	Value range: <0, ∞). If greater than 0, it limits the maximum effect of the promotion factor to the specified multiple of the original total forecast
fast-adapt-running-index-min	0	Value range: <0, ∞). If fast-adapt-distribution-enabled is enabled, the promotion must have a higher cumulative index sum of past days in order to calculate promotional fast adapt.
promo-prediction-share-disallow-stock-outs	0	Value range: {0, 1}. If set to 1, promotions with detected lost sales will be excluded from training the promo prediction share
promo-prediction-version	2	Promo prediction version. Possible values: 2, 3
promo-history-share-min-index-value	0.1	Value range: (0, 1]. Minimum value of the daily index below which the actual sales are zeroed. If enabled, they will be replaced by the average adjusted sales during the promotion.
promo-history-share-average-zero-index	0	Value range: {0, 1}. If enabled, all indices below the value specified in promo-history-share-min-index-value will be replaced by the average adjusted sales during the promotion.
batch-promo-prediction-day-part-size	2000	Value range: (0, ∞). Number of PLIDs per thread for calculating the daily forecast in batch-promo-prediction.php.

Name	PossibleValues	Description
Configuration for batch-promo_detection
history-length	2	Range of values <0, ∞). It is possible to set the number of whole months in the history (after the first evaluation in the whole history), on which the search for missing events and the calculation of discounts will be evaluated. If set to 0, it uses the entire possible history.
max-promo-length	61	Maximum promotion length in days.
min-promo-length	3	Minimum promotion lenght in days. In retail, it must be 1 day.
min-promo-discount	0.03	Range of values <0, 1>. Minimum discount size for promotions.
update-promo-dates	0	Range of values {0, 1}. Adjust promotion dates according to price size?
find-missing-promo	0	Range of values {0, 1}. If it is set to 1, then the looking for missing promotions is enabled. 0 = disabled.
compute-purchased-amount	0	Range of values {0, 1}. If it is set to 1, then for each completed promotion upload purchases from move table during the delivery period is enabled.
find-only-null-prices	0	Range of values {0, 1}. Setting whether to update only prices with a value of NULL (value = 1) or all (value = 0). It only makes sense if detection-find-prices setting is enabled.
update-promo-discount-and-price	0	Range of values {0, 1}. If it is set to 0, the calculation of sales promotional and sales non-promotional prices and subsequent calculation of discounts are enabled. If it is set to 0, then calculation is disabled.
find-purchase-prices	pn>0,pp>0	Range of values: 0/1 (off / on). Recalculation of purchase prices: pn -> purchase improper, pp -> purchase promotional. Default: pn> 0, pp> 0.

Name	PossibleValues	Description
Configuration for batch-prs
field_ord_period_to_cover	S	Enabling or disabling of the ""Period"" field for orders aggregation. It can take values: S - for suppliers.
warehouse_category_type_id	1	Defining category_type_id which determines the warehouses.
field_ord_ratio_max	S	Enabling or disabling the field " Min. load". It can take the values: S - for suppliers.
field_lt_ignore_deviation	SR	Enabling or disabling the field "Ignore variability". It can take the values: S - for suppliers.
field_lt_leadtime_bs	SR	Enabling or disabling the field "Leadtime for BS". It can take the values: S - for suppliers.
field_lt_leadtime	SR	Enabling or disabling the field "Leadtime". It can take the values: S - for suppliers.
use_order_limits	S	Enabling or disabling order limits. It can take the values: S - for suppliers, R - for redistribution and SR for both.
field_period_minimal_ss	SR	Enabling or disabling the field "Min. period for SS ". It can take the following values: S - for suppliers.
field_period_minimal_bs	SR	Enabling or disabling the field "Min. period for BS ". It can take values: S - for suppliers.
field_period_minimal	SR	Enable or disable field "Min. period". It can take the following values: S - for suppliers.
use_standard_provider_group_administration	0	Enable or disable standard management of supplier groups. 1 - use standard PW group management, 0 - use group management in this module
field_ord_amount_min	S	Enable or disable field "Min. amount for orders". It can take the values: S - for suppliers.
field_ord_amount_max	S	Enable or disable the field "Quantity for utilization ". It can take the following values: S - for suppliers.
field_ord_value_min	S	Enabling or disabling the field "Min order value". It can take the values: S - for suppliers.
field_ord_value_max	S	Enabling or disabling the field "Value for utilization". It can take the values: S - for the suppliers.
field_days_in_week	SR	Enable or disable the setting of days of the week for the field "Term of period ". It can take the values: S - for the suppliers.
field_days_in_month	SR	Enable or disable the setting of days of the month for the field "Term of period". It can take the values: S - for suppliers.
field_fixed_period	SR	Enable or disable the setting of a fixed period for the field "Term of period ". It can take the values: S - for suppliers.
field_clients_groups	S	Enable or disable client groups. It can take the values: S - for suppliers, R - for redistribution and SR for both.
field_warehouses_groups	SR	Enable or disable warehouse groups. It may take the values: S - for suppliers, R - for redistribution and SR for both.
field_products_groups	SR	Enable or disable product groups. It may take the values: S - for suppliers, R - for redistribution and SR for both.
field_ord_max_days_to_cover	S	Enable or disable field "Max days for aggregation of orders". It can take the values: S - for suppliers.
product_category_type_id	NULL	Definov
field_minimum_order_quantity	SR	Enable or disable the field "MOQ". It can take the values: S - for suppliers.
field_minimum_order_set	SR	Enable or disable the field "SET". It can take the values: S - for suppliers.
use_ordering_limits	SR	Enabling or disabling order limits. It can take values: S - for suppliers, R - for redistribution and SR for both.
batch-periodical-ordering-part-size	2000	Number of items per computation thread in the .NET batch.
enable_exceptions_ordering	0	Enable or disable sorting of exceptions before/after other settings. 0 - disabled (default), 1 - enabled.

Name	PossibleValues	Description
Configuration for batch-pt
split-header-enabled	0	Range of values {0, 1}. If it is set to 1, then display of the breakdown of the total promo volume in the promotion header is enabled. 0 = disabled.
split-row-enabled	0	Range of values {0, 1}. If it is set to 1, then display of the breakdown of the total promo volume in the promotion line is enabled. 0 = disabled.
split-period	0	Range of values {0, 1, 2}. Period for the breakdown of the total volume of the promoaction, options: 0 = transitional week, 1 = week, 2 = month.
promo-discount-rounding	2	On how many decimal places the resulting promo total discount will be rounded.
promo-price-rounding	2	On how many decimal places the resulting promo price will be rounded.
promo-discount-switch-condition-enabled	0	Range of values {0, 1}. Displays all discount conditions specified in the discount_condition_type table in the case of a value of 0, otherwise it displays one field for the discount, which is the default value and the rest will be displayed on the + icon, when a selectobox is displayed with the option to add another.
promo-discount-multi-condition-discount-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) multi-discount settings for individual products.
split-auto-enabled	0	Range of values {0, 1}. Display of automatic split according to the selected scenario if it is set to 1. 0 = nothing is displayed.
promo-detail-bonus-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) the display of bonus prices on product details
price-nonpromo-discount-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) the calculation of product price discounts.
price-nonpromo-bonus-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) the calculation of bonus discounts on product level.
promo-discount-multi-condition-bonus-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) multi-bonus settings for individual products.
display-concurrent-promotions-enabled	0	Range of values {0, 1}. If it is set to 1, it display competing promotions in the tooltip in the table of products.
workflow-v2-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) the workflow system of states version 2.
amount-prediction-button-enabled	0	Range of values {0, 1}. If it is set to 1, display of the button for volume calculating in the detail of promotion row is enabled. 0 = disabled.
row-list-checkboxes-enabled	0	Range of values {0, 1}. If it is set to 1, then the checkboxes column in the promotion row is displayed. 0 = the checkboxes column is hidden.
evaluation-v2-enabled	1	Range of values {0, 1}. Enables (1) or disables (0) evaluation version 2
evaluation-v2-showhide-header	0	Range of values {0, 1}. Enables (1) or disables (0) the display of the evaluation header in the showhide.
evaluation-v2-showhide-row	0	Range of values {0, 1}. Enables (1) or disables (0) the display of the evaluation row in the showhide.
row-promo-actions-enabled	0	Range of values {0, 1}. 1 = Displays a list of promotions in the product detail (pormoaction row) that are created for the given product. 0 = list of promotion is not displayed.
promo-prediction-debug-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) debugging reports in promo-prediction.
graph-show-promo-actions	0	Range of values {0, 1}. 1 = Displays a list of promotions in the tooltip in a graph that is on the detail of the promotion row.
bulk-actions-enabled	0	Range of values {0, 1}. Enables (1) or disables (0) bulk actions in promotion.
load-value-after-auto-save	0	1: For values that are saved via autoSave via ajax, the value is reloaded from the database immediately after saving and displayed on the form. So if we save the text in the numeric db column, the text will not be left in the form, but exactly what will be displayed will be displayed.
promotool-promo-copy-enabled	0	Range of values {0, 1}. Enables (1) or disabled (0) promotion copying.
amount-user-change-logging	0	Range of values {0, 1}. If it is set to 1 then the date of amount change (amount_promo, amount_base) is saved - only if it was changed by the user in the form. It is stored in amount_promo_user_change and amount_base_user_change. If the value 0 is set then the amount changes by the user is not logged.
report-forecast-and-history-enabled	0	Range of values {0, 1}. 1 = Display forecast and history report. 0 = forecast and history report is not displayed.
price-nonpromo-bonus-save-as-percent	0	Calculated nonpromo bonus discount in CPromotoolPrice module is saved in percentage or in absolute value?
amount-report-button-enabled	0	Range of values {0, 1}. If it is set to 1 then the button for the report of the incorrectly calculated volume in the detail of the promotion line is displayed . If it is set to 0, button is not displayed.
amount-progressive	0	Range of values {0, 1}. Turns on (1) continuous drawing of the promotion. Ie. that the real amount for amount_promo is used during the promotion if it is greater than the amount predicted by the user. The original user-predicted amount is stored in user_amount_promo.
list-price-aggregation-function	min	If several different list prices are selected, how is the right one chosen. Possible values: min, max, avg, sum
list-price-date-selection	date-from-only	Range of values {date-from-only, date-to-only, date-from-date-to }.date-from-only: select the list price, which is valid on the day of the start of the promotion; date-to-only: similarly, only on the day of the end of the promotion; date-from-date-to: all list price prices that affect the promotion are selected, and the aggregation is used for this.
report-evaluation-enabled	0	Range of values {0, 1}. If the value 1 is set, then the evaluation report is displayed.
client-filter-use-pt-header-client	0	Range of values {0, 1}. 1 = Enables the filling of the pt_header_client table.
product-filter-enabled	0	Range of values {0, 1}. 1 = Turns on the product filter.
product-filter-use-clients-products-checkbox	1	Range of values {0, 1}. If it is set the value 1, then in the product filter it displays a checkbox for filtering only those products for which SKUs for the selected customer exist.
price-listprice-enabled	0	Range of values {0, 1}. If it is set to 1 then the use of the list_price table when changing SKUs or data in PT (ie also when creating a new row) is enabled.
product-list-enabled	0	Range of values {0, 1}. If it is set to 1 then the product list at the promotion is displayed.
add-blank-product-locator-enabled	0	Range of values {0, 1}. 1 = If a product should be added to the PT for a customer for which there is no PLID, the Add Blank PLID (SKU) functionality will be used.
customer-code-enabled	0	Range of values {0, 1}. If it is set to value 1, then customer code for promoaction is displayed.
promo-tm-enabled	0	Range of values {0, 1}. 1 = Allow assignment of TM action to TA.
admin-tm-enabled	0	Range of values {0, 1}. 1 = Administration of TM action is allowed.
delivery-date-erasable	1	Range of values {0, 1}. 1 = Allows to delete already entered delivery date in promo form.
promo-owner-enabled	0	Range of values {0, 1}. 1= Display of owner settings for promoaction.
promo-ignore-for-training-enabled	0	Range of values {0, 1}.1 = Display of checkbox with permission of promoignore from learning.
row-promo-actions-graph-enabled	0	Range of values {0, 1}. 1 = Displays graph of promo action in product detail (promoaction row), which are created for the product.
batch-promo-change-enabled	0	Range of values {0, 1}. 1 = Enables the promotool-batch-promo-change module, which performs automatic promo changes in a batch.
promo-coverage-enabled	0	Range of values {0, 1}. 1 = Turns on the possibility to set coverage in the promo form.
promo-export-enabled	0	Range of values {0, 1}. 1 = Turns on the possibility to export TA from the form.
promo-file-upload-enabled	0	Range of values {0, 1}. 1 = Turns on the possibility to upload files to TA.
row-unique-product	0	Range of values {0, 1}. 1 = Each product can be inserted into the promotion only once.
promo-row-delivery-date-enabled	0	Range of values {0, 1}. 1 = Turns on the possibility of changing the delivery date for the TA row.
price-nonpromo-label-type	shortcut	Range of values {shortcut / name / both}. What will be displayed in the tooltip for nonpromo discounts.
product-group-enabled	0	Range of values {0, 1}. 1 = Turns on the display of entries for product group.
revision-history-show-history-branch-only	0	1: Historical revisions are listed from the current pt_header_id and then back to history according to previosu_id. 0: All revisions active 0 or 1 are.
promotool-approval-limits-table	0	Range of values {0, 1}. 1 = Displays the promotool-approval module table, which shows the approval limits and whether they are met or not.
promo-discount-auto-recompute-no-negative	1	Range of values {0, 1}. 1 = If ptr_promo is fixed, discount_promo will never be calculated negative.
promotool-report-dpa-enabled	0	Range of values {0, 1}. 1 = Enable dpa report display.
promotool-dashboard-enabled	0	Enables recalculations of the Promotool dashboard.
promo-amount-rounding	2	Number of decimal places to round the final volume to.
commercial-costs-split-method	1	Determines the selected split method for commercial costs. Default is 1: evenly distributes the amount based on the number of products. Option 2: distributes the amount proportionally based on the quantity of each product.
pidi-import-default-category-type	2	Promotion import settings. The level at which promotions should be imported.
pidi-import-enabled	0	Enable the import bridge for Promotool actions.
pidi-import-date-to-computation		Set the date for which promotions should be imported from PIDI
page-promotion-dashboard-enable	0	Turns on the promotions dashboard page
promotool-approval-limits-allow-for-products	0	Enable limits directly for products.
promotool-approval-limits-categories		Categories for limits.
promotool-approval-limits-direction-loading-limit	FROM_TOP	Limit setting direction

Name	PossibleValues	Description
Configuration for batch-safetystock
whatif-enabled	1	Range of values {0, 1}. 1 = Toggle whether to calculate data for the whatif-safetystock report and whether to display the report. Valid only in combination with daily variability v2. No additional data needs to be calculated for v1 and the report is always displayed.
skip-computation-for-zero-safetystock	0	Range of values {0, 1}. 1 = It completely skips the calculation for PLIDs that have zero_safetystock = 1 and at the same time have only a reflexive relationship in the safetystock_relation.
sale-deviation	1	Range of values {0, 1}. 1 = Allows error forecast.
safetystock-day-smoothing	1	Range of values {0, 1}. If set to 1, enables smoothing of the difference of the safetystock during the transition between months (manipulated for a total of 20 days - 10 of the current and 10 of the next month). If a daily breakdown (dayshare) is used, overloaded values or promotion SafetyStock are received, this quantity will not be smoothed!
rounding-threshold	0.2	Range of values (0, 1). Limit value for rounding safetystock_order, if the next decimal places after safetystock_prerequisites.decimal_places (product_locator.rounding) <= this value, it will be rounded down to decimal_places, otherwise it will be rounded up to decimal_places. Example: key value 0.2, decimal_places 2 - input 0.001 will be rounded to 0, input 0.002 will be rounded to 0.01
purchase-deviation	0	Range of values {0, 1}. 1 = Allows deviation of the purchase amount.
part-size	500	Number of calculation units (product-locators) in one computation thread in .NET safetystock calculation.
minimal-period-ss	0	Range of values <0, 1>. Minimum period value in months that will be taken when setting lower-safetystock-mode to PERIOD_SS.
min-forecast-error	10	Minimum percentage forecast error. 100 = 100%.
lower-safetystock-percent	200	Range of values <0, ∞). If it is set to more than 0, safetysotck will be limited to the lower-safetystock-percent percent of the lower-safetystock-mode indicator.
lower-safetystock-mode	MONTH	Range of values {MONTH, SS_PERIOD}. If it is set to SS_PERIOD, the period will be taken into account when calculating the safetystock limiter (a period of 15 days means that only half of the monthly forecast is taken as the basis for the limiter) before calculating the final value using lower-safetystock-percent, if set to MONTH, the whole monthly forecast will be used.
lower-safetystock-before	2	Allowed value: integer. Number of months in the history from which data will be taken for the safetystock limit according to the forecast (can be set to negative, but not more than lower-safetystock-after: value -1 says that it will start 1 month AFTER THE CURRENT OUTLOOK and will be taken until lower-safetystock-after).
lower-safetystock-after	2	Allowed value: integer. The number of months into the future from which data will be taken for the safetystock limit according to the forecast (can be set to negative, not more than lower-safetystock-before: the value -1 says that it will be taken from lower-safetystock-before and will end 1 month BEFORE THE CURRENT OUTLOOK).
leadtime-deviation	1	Range of values {0, 1}. 1 = Enable leadtime deviation.
ignore-sporadic-redistribution	0	Range of values {0, 1}. If it is set to 1, updates safetystock_relation.is_relevant to 0 for all redistributed and sporadic products and thus excludes them from the session.
ignore-sporadic-production	0	Range of values {0, 1}. If it is set to 1, updates safetystock_relation.is_relevant to 0 for all manufacturing and sporadic products and thus excludes them from the session.
ignore-outliers	0	Default 0. Number if extremes to be ignored when calculating the daily variability (usually 0 or 1).
day-variability-season-yes-boundary	43586	Range of values (day -var iability-season-no-boundary, 12>. If the absolute difference between the highest and lowest seasonal index for a product is greater than this value, it will be taken as a seasonal item for use in daily variability.
day-variability-season-no-boundary	0.5	Range of values <0, day-variability-season-yes-boundary). If the absolute difference between the highest and lowest seasonal index for a product is less than this value, it will be taken as a non-seasonal item for use in daily variability.
day-variability-max-leadtime	21	Maximum lead time lenght in days for daily variability.
day-variability-decrease-from-leadtime	7	The minimum lead time lenght in days from which the daily variability begins to be linearly reduced.
day-variability-close-months	3	Range of values (0, ∞). Number of months in history to be considered as current daily variability "(obtained from the immediate vicinity)".
day-sale-deviation	1	Range of values {0, 1}. 1 = Allow daily variability.
actual-day-variability-weight	0.6	Range of values (0, 1). Specifies the ratio between the current (PwDate-3 months) and historical daily variability (3-month floating window) that will be used when calculating the SS (1 = 100% current, 0% historical)
ignore-dont-order	0	Whether to exclude PLIDs from the relation that are not being sold (dont_order = 1)
ignore-sellout	1	Whether to exclude PLIDs from the relation that are clearance items (sellout_new_product_type_id = 2)
day-variability-history-years	1	Range of values (0, ∞). Number of years of history to be used for calculating the daily distribution error.
day-variability-maximal-leadtime	31	Range of values <0, ∞). If greater than 0, defines the maximum lead time of an item for which the daily distribution error is calculated.
day-variability-positive-residual-ratio	1	Range of values (-∞, ∞). Defines the multiplier of daily error in situations where the expected sales were higher than the actual sales.
day-variability-negative-residual-ratio	1	Range of values (-∞, ∞). Defines the multiplier of daily error in situations where the expected sales were lower than the actual sales.
day-variability-normalization-zero-level	1e-6	Range of values (-∞, ∞). Specifies the minimum value of daily decomposition for which normalization is allowed; if the decomposition is lower than this value, the day will be zeroed out.
day-variability-compute-what-if	0	Range of values {0, 1}. Enables the calculation of underlying data for the "what-if" analysis of daily decomposition error.
batch-safetystock-day-part-size	2000	Range of values (0, ∞). Number of PLIDs per thread for calculating daily safety stock in batch-safetystock.php
promo-prediction-overlapping		Method of calculating safety stock for overlapping promotions during ordering (default = empty string). The meaning of the settings is the same as in promo-prediction-overlapping. Default empty string = use the setting from promo_configuration.promo-prediction-overlapping
promo-safetystock-up-limiter	0	Value range <0; ∞). For 0, the feature is disabled; otherwise, it represents the maximum percentage value of the safety cap against the calculated promotion effect, which will be applied if necessary.
promo-safetystock-down-limiter	0	Value range <0; ∞). If set to 0, the feature is disabled; otherwise, it defines the minimum percentage safety threshold against the calculated promotion effect, to which it will be increased if necessary.

Name	PossibleValues	Description
Configuration for batch-seasonality
protected-months	12	Range of values <1, 12> separated by commas. Specifies months that cannot be used by smoothing when manipulating the environment, and at the same time must not be degraded by smoothing.
explicit-category	AUTO	Specifies from which category seasonality will be calculated. It is not recommended to use strong category_type. If AUTO is used, all product categories are automatically used. Calculating seasonality from a category can be turned on or off using the settings item in the seasonal configuration. Category_types are entered using the following syntax: cX_id, cY_id (i.e., a comma-separated list of categories). Only one combination of categories can be specified (as opposed to middleout-forecast).
settings	plid;product;category;	Allowed values: plid, product, category or company. Specifies from which parts the seasonality will be calculated.
short-season-months	12	Allowed values 1-12. Separator ;. Determines which months have less seasonality confirmation requirements.
part-size	20000	Allowed values (0, ∞). Specifies by which parts the work for .NET threads will be distributed. A good guideline when selecting this number is the sizes of the top_down groups/categories configured in seasonality_configuration.explicit-category to avoid unnecessary duplicate calculations. The larger the number of units the more memory intensive, but the less time consuming it is to create and manage threads.
computation-type	1	pre-set the full / increment conversion to .Net. Not adjustable, recalculates each time the batch is started.
seasonality-compute-days	0,1,2,3,4,5,6	Which days to count batch-seasonality or batch-seasonality-v2. The other days the counted value from the last full recalculation is used and the new SKUs are given seasonal indices that contain only 1. The separator is a comma, 0 = Monday. If the seasonal index tables are empty, the full recalculation is performed regardless of this setting.
min-history-length	24	Allowed values (0, ∞). Specifies minimal history length for seasonality analysis to be computed for plid.

Name	PossibleValues	Description
Configuration for batch-smi
mark-seasonal-product-as-non-sporadic	1	Range of values {0, 1}. 1 = Mark seasonal products as non-sporadic.
mark-new-product-as-sporadic	0	Range of values {0, 1}. 1 = Marks new products as sporadic to be ordered via basestock.
mark-all-products-as-non-sporadic	0	Range of values {0, 1}. 1 = Marks all items as not sporadic, without exception.
accept-target-smi	1	Range of values {0, 1}. If set to 1, the value is_smi = 0 is set via the product_locator_component binding.
compute-with-current-month	1	Range of values {0, 1}. If it is set to 1, the current month is also used when calculating SMI and sporadic items.
accept-ofc	1	Range of values {0, 1}. If set to 1, the OFC is also used when calculating SMI and sporadic items.
months-sale	0-1	Values 0.0-1.0 – sets a ratio of months with sales to all months (maximum 12) under which the product is marked as SMI.
sporadic-less-than	2	Limit for sporadic products: if the number of sales is less than or equal to this value, the product will be forcibly classified as sporadic. This is to prevent new products from immediately being treated as non-sporadic.

Name	PossibleValues	Description
Configuration for batch-stockout
enabled	1	Range of values {1, 0}. Enables start of stockout analysis.
part-size	5000	Range of values <1, ∞). Specifies the number of PLIDs that will be calculated in one computation thread.
max-length	60	Range of values <0, ∞>. If the stockout is longer than this value, the stockout will be automatically deleted-
baseline-loss-ratio	0.9	Range (-∞, ∞). Determines how many % of the estimated amount will be calculated as lost sales for regular sales.
promo-loss-ratio	0.9	Range of values (-∞, ∞). Determines how many % of the estimated amount will be calculated as lost sales for the promotional Sales.
redistribution-loss-ratio	0.9	Range of values (-∞, ∞). Determines how many % of the estimated amount will be calculated as lost sales for redistribution.
months-before	3	Range of values <0, ∞). Maximum number of months (v2 counts for this setting * 30 number of days) before the detected stockout, from which the amount will be calculated. The area will be divided into 3 parts in the calculation and the smallest possible satisfying the sale-treshold condition will be used.
months-after	3	Range of values <0, ∞). Maximum number of months (v2 counts for this setting * 30 number of days) after the detected stockout from which the elapsed amount will be calculated. The area will be divided into 3 parts in the calculation and the smallest possible condition satisfying the sale-treshold condition will be used.
month-weight	0.5	Range of values <0, 1>. Weight of the estimated value of the lost amount calculated from the surrounding values according to the days-before and days-after settings.
year-weight	0.5	Range of values <0, 1>. Weight of the estimated value of the lost amount calculated from the stockout period of the previous and next year.
sale-threshold	0.6	Range of values <0, 1>. Minimum ratio of days with sales to the total number of days to select a shorter period for the calculation of the lost amount from the surrounding values according to the days-before and days-after settings
analyse-report-enabled	1	Range of values {0, 1}. 1 = Enables the stockout evaluation report.
ignore-sporadic	1	Field of values {0, 1}. When it is set to 1, it does not calculate stockouts on sporadic items.
disable-stockout-masking	0	Domain of values {0, 1}. If set to 1, it disables the masking of periods with stock levels below the corresponding threshold when calculating the average daily lost sales quantity.
normalization-zero-level	1e-6	Domain of values <0, ∞). Specifies the threshold index for normalization based on daily distribution (day-share, season-indices, Easter, and Christmas), below which the input sales will be zeroed instead of divided.
normalization-index-minimum	0.1	Domain of values <0, ∞). Specifies the minimum index value for normalization based on daily distribution (day-share, season-indices, Easter, and Christmas) by which the input sales can be divided.
output-index-maximum	10	Domain of values <0, ∞). Specifies the maximum index value for normalization based on daily distribution (day-share, season-indices, Easter, and Christmas) by which the resulting lost sales can be multiplied.
should_compute_stockout_level_by_avg_day_sale	0	Range of values { true, false }. Determines whether the stockout level is recalculated based on average sales in the past or not.
stockout_level_avg_day_sale_history_length	30	Range of values { 1, ∞ }. The number of days in the past from which the average daily sales are taken to recalculate the stockout level.
stockout_level_avg_day_sale_index	1	Range of values <0, ∞). An index that multiplies average daily sales.

Name	PossibleValues	Description
Configuration for batch-validation_scenario
acceptable_deviation_percent_sales_amount	1	Permitted deviation of sales quantity in %.
acceptable_deviation_percent_sales_value	1	Permitted deviation of sales value in %.
acceptable_deviation_percent_reserve_amount	1	Permitted deviation of stock quantity in %.
acceptable_deviation_percent_reserve_value	1	Permitted deviation of stock value in %.

Name	PossibleValues	Description
Configuration for batch-promo_history
enabled	1	Range of values {0, 1}. If it is set to 1, allows batch-promo-detection, batch-promo-and-move-pairing, and batch-promo-analyze-v2 to be replaced by a new calculation.
part-size	750	Range of values (0, ∞). Number of groups to be calculated in one thread.
move-type-sale	1	Range of values: comma-separated list of numbers. Specifies which move_type_id will be loaded from the move table as sales moves.
move-type-purchase	2, 4	Scope of values: comma-separated list of numbers. Specifies which move_type_id will be loaded from the move table as purchase movements.
promo-amounts-compute-purchased	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the purchased quantity for the historical promotions.
promo-prices-compute-nonpromo-purchase	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the non-promotional purchase price.
promo-prices-compute-promo-purchase	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the promotional purchase price.
promo-prices-compute-nonpromo-sale	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the non-promotional sales price.
promo-prices-compute-promo-sale	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the promotional sale price.
promo-prices-compute-discount	0	Range of values {0, 1}. If it is set to 1, it allows the calculation of the discount from the promotional and non-promotional price.
promo-prices-compute-only-null	0	Range of values {0, 1}. If it set to 1, it allows the calculation of the price only if it is empty.
promo-prices-default-discount	0	Range of values <0, 1>. The value of the discount that will be assigned to the promotion if it cannot be calculated.
pairing-type	DATE	Range of values {NONE, DATE, PRICE}. Specifies the type of motion pairing for promotions NONE = pairing is off; DATE = pairs according to the date of movement, priority at overlap - earlier starting - shorter - lowest ID; PRICE = same as DATE, but in addition the price rounded according to the pairing-rounding-precision setting must be matched.
pairing-clear-imported	0	Range of values {0, 1}. If it is set to 1, it deletes the promo_action_id imported from the customer on the loaded movements. WARNING! If the pairing-type is NONE it automatically sets to DATE and creates a warning!
pairing-rounding-precision	1	Range of values <0, ∞). Number of decimal places to be checked if the pairing-type is set to PRICE.
promo-only-plid-enabled	1	Range of values {0, 1}. When it is set to 1, it allows the detection of PLIDs that are only sold as part of the promotion.
promo-only-plid-pre-neighborhood-days	7	Range of values <0, ∞). The number of days before the promotion that will count towards the promoaction period for the detection of promo only PLIDs.
promo-only-plid-post-neighborhood-days	7	Range of values <0, ∞). The number of days after the promotion that will count towards the promoaction period for the detection of promo only PLIDs.
promo-only-plid-set-zero-forecast-and-ss	1	Range of values {0, 1}. If it is set to 1, detected promo only PLIDs, zero_forecast and zero_safetystock will be automatically set to 1.
baseline-pre-neighborhood-days	0	Range of values <0, ∞). The number of days before the promotion that will count towards the promoaction period to calculate the baseline.
baseline-post-neighborhood-days	0	Range of values <0, ∞). The number of days after the promotion that will count towards the promoaction period to calculate the baseline.
baseline-merge-predecessors	0	Range of values {0, 1}. If it is set to 1, the baseline calculation will be "learned" from predecessor and successor data.
baseline-merge-top-down	0	Range of values {0, 1}. If it is set to 1, the baseline calculation will be "learned" from the top-down session data.
baseline-max-promo-length	122	Range of values <0, ∞). The maximum length of the action that can enter the baseline calculation.
promo-only-plid-minimal-sale-days	60	Domain of values <0, ∞). Minimum number of days since the first sale required to identify a PLID as promo only.
pairing-price-tolerance	0	Domain of values <0; 1>. Specifies the maximum allowed relative difference between the movement sales price and the promotion price when pairing-type = PRICE_TOLERANCE.
pairing-clear-missing	0	Domain of values {0, 1}. If set to 1, it allows the removal of non-existent promo_action_id entries from the move table.
pairing-only-defined-promo-moves	0	Domain of values {0, 1}. If set to 1, pairing is enabled only for moves that have unknown promotion specified (-1).

Name	PossibleValues	Description
Configuration for batch-promo_configurat
relevant-promo-distance	1825	Maximum relevant (daily) distance between historical promotions and the target promotion in the promo-prediction. Too far-reaching historical promotions are penalized according to the penalty-out-of-distance parameter. The relevant-promo-distance parameter specifies the width of the Gaussian penalty curve. The wider is this curve, the greater deviation is tolerated.
relevant-seasonal-distance	120	Maximum relevant season distance between historical promotions and the target promotion in the promo-prediction. Historical off-season promotions are penalized according to the penalty-out-of-season parameter. The relevant-seasonal-distance parameter specifies the width of the Gaussian penalty curve. The wider is this curve, the greater deviation is tolerated.
relevant-discount-distance	0.3	The maximum relevant distance between the discounts of historical promotions and the discount of the target promotion in the promo-prediction. Too diferent historical promotion discounts are penalized according to the penalty-out-of-discount parameter. The relevant-discount-distance parameter specifies the width of the Gaussian penalty curve. The wider is this curve, the greater deviation is tolerated.
relevant-length-ratio	43955	The maximum relevant ratio between the lengths of historical promotions and the length of the target promotion in promo-prediction. Historical promotions with too different lengths are penalized according to the penalty-out-of-length parameter. The relevant-length-distance parameter specifies the width of the Gaussian penalty curve. The wider is this curve, the greater deviation is tolerated.
penalty-out-of-distance	0.2	Range of values the interval <0, 1>, with a penalty in the worst (limit) case. Penalty of the historical promotion, which is located too far in relation to the target promotion in the promo-prediction. The smaller is this penalty, the stronger is the penalty of the resulting weight.
penalty-out-of-season	0.2	Range of values the interval <0, 1>, with a penalty in the worst (limit) case. Penalty of the historical promotion, which is located out of season due to the target promotion in the promo-prediction. The smaller is this penalty, the stronger ia the penalty of the resulting weight.
penalty-out-of-discount	0.1	Range of values the interval <0, 1>, with a penalty in the worst (limit) case. Penalty of the historical promotion, the discount of which is too different from the discount of the target promotion in the promo-prediction. The smaller this penalty, the stronger the penalty of the resulting weight.
penalty-out-of-length	0.1	Range of values the interval <0, 1>, with a penalty in the worst (limit) case. Penalty of the historical promotion, the length of which is too different from the length of the target promotion in the promo-prediction. The smaller is this penalty, the stronger is the penalty of the resulting weight.
penalty-next-level	0.8	Range of values the interval <0, 1>, with a penalty for each higher level. Penalty the weight of the historical promotion for each higher level in the hierarchy of categories in the promo-prediction. The smaller is this penalty, the stronger is the penalty of the resulting weight.
penalty-promo-type	0.1	Range of values the interval <0, 1>, being penalized only if the promo_type_id of the training promotion differs from the promo_type_id of the target promotion.Penalty the weight of the historical promotion for a different promotion_type_id in the promotion. The smaller is this penalty, the stronger is the penalty of the resulting weight.
penalty-attribute	0.5	Range of values the interval <0, 1>, being penalized only if the attribute of the training promotion differs from the attribute of the target promotion. Penalty the weight of the historical promotion for each different attribute (leaflet, secondary_placement, etc.) during the promotion. The smaller is this penalty, the stronger is the penalty of the resulting weight.
secondary-discount-weight	0	Range of values the interval <0, 1>. Default weight for the secondary discount of the promotion. Used if secondary_discount_weight = NULL is in the target promotion.
promo-cannibalization-min-ratio	0.25	Minimum allowed factor of sales reduction due to cannibalization.
promo-cannibalization-combine-coefficient	0.65	Coefficient in the interval <0.5, 1.0>., which determines the strength of the cannibalizing effect of several simultaneously acting promotions.
penalty-product	0.8	Range of values the interval <0, 1>, being penalized only if the product_id of the training promotion differs from the product_id of the target promotion. Penalize the weight of the historical promotion for a different product_id in the promotion. The smaller is this penalty, the stronger is the penalty of the resulting weight.
secondary-length-weight	0	Range of values the interval <0, 1>. Default weight for the secondary length of the promotion. Used if secondary_length_weight = NULL in the target promotion.
filter-heavy-weight-threshold	0.5	Percentage threshold that determines the minimum weight of high-weight training promotions. The threshold is always related to the toughest training promotion.
filter-heavy-weight-count-min	1	The minimum number of high-weight training promotions that must remain in the training sample after the extremes have been filtered out.
filter-heavy-weight-count-threshold	0.5	The minimum percentage of high-weight training promotions that must remain in the training sample after the extremes have been filtered out. The threshold refers to the total number of high-weight training promotions.
filter-quantile-up	43953	Quantile for filtering high extremes in promo-prediction. The higher is this quantile, the higher extremes are allowed, ie. the weaker filter.
filter-quantile-down	2	Quantile for filtering low extremes in promo-prediction. The higher is this quantile, the lower extremes are allowed, ie. the weaker filter.
filter-enabled	1	Range of values {0, 1}. Enable (=1) extreme filtering in promo-prediction.
filter-zeros-enabled	1	Range of values {0, 1}. Enable (=1) filtering of zero-effect training promotions in the promo-prediction.
filter-heavy-weight-enabled	1	Range of values {0, 1}. Allowing (=1) the inclusion of high-mass training promotions in filtering extremes in the promotion.
percentile-model-enabled	0	Range of values {0, 1}. Permission (=1) to use the 50% percentile prefix instead of the origin length of the promotion.
filter-target-promoaction-enabled	1	Range of values {0, 1}. Enable (=1) filtering of the target promotion from a set of training promotions.
filter-future-promoaction-enabled	0	Range of values {0, 1}. Enable (=1) filtering of training promotions that are older than the target promotion.
filter-quantile-up-2d	1.5,2.5,2.5,3.5	Quantile values for 2d high extremum filter (depending on head / length), values are for head / length normalized to the interval 0-1 in points: [0,0], [0,1], [1,0], [ 1.1]. The other values are calculated by bilinear interpolation.
filter-quantile-down-2d	3.5,2.5,2.5,1.5	Quantile values for 2d low extremum filter (depending on head / length), values are for head / length normalized to the interval 0-1 in points: [0,0], [0,1], [1,0], [ 1.1]. The other values are calculated by bilinear interpolation.
penalty-holiday	0.8	Domain of values <0; 1>. Penalty weight for differing values of the "holiday" attribute.

Name	PossibleValues	Description
Configuration for STOCK in general
pwdate	43770	NULL
batch-crashed	FALSE	NULL
batch_id		NULL
smi_36_computed	40161	NULL
check_php_test	1	NULL
is_test_db	0	NULL
project		NULL
company		NULL
has-virtual-no-supply-relation		NULL
project-for-cleanup-pw	sandbox	NULL
pwmessages_checksum	0	NULL
fulltext-search	without-star	NULL
password-validity-period	90	NULL
check_user_hash_cookie	0	Range of values {0,1}. Enable (=1) / disable (=0) the user when the user copying the URL into a different browser / computers.
kill	1	NULL
kill_reason		NULL
views-imported	1	NULL
treeview_category_hiding_mode	HIDE/SKIP	NULL
max_date_from_move	2019-11-07\|2019-10-31	NULL
min_date_from_move	2019-11-07\|2017-11-01	NULL
default_veritico_type	1	Default Veritico type setting (1 - stock / 2 - price / 3 - plan)
computation_type_id	1	Type of comptation batch. 1 - normal batch, 2 - custom small batch, 3 and more - custom types
disable-batch-kill-in-user-mode	1	If the configuration is enabled, an error in the GUI will not terminate the computation.
proc-keep-history-months	36	How many months we want to retain records in proc_history

Name	PossibleValues	Description
The keys and values are identical to those in OUTLIERS_CONFIGURATION table. Configuration for STOCK outliers computation, tied to the product/warehouse unit (SKU)
see OUTLIERS_CONFIGURATION where rewritable_for_plid = 1	see OUTLIERS_CONFIGURATION	see OUTLIERS_CONFIGURATION

Name	PossibleValues	Description
The keys and values are identical to those in FORECAST_CONFIGURATION table. Configuration for STOCK forecast computation, tied to the product/warehouse unit (SKU)
see FORECAST_CONFIGURATION where rewritable_for_plid = 1	see FORECAST_CONFIGURATION	see FORECAST_CONFIGURATION

Name	PossibleValues	Description
Configuration for STOCK stockout computation, tied to the product/warehouse unit (SKU) The keys and values are identical to those in STOCKOUT_CONFIGURATION table.
see STOCKOUT_CONFIGURATION where rewritable_for_plid = 1	see STOCKOUT_CONFIGURATION	see STOCKOUT_CONFIGURATION

Name	PossibleValues	Description
The keys and values are identical to those in ORDER_CONFIGURATION table. Configuration for STOCK suggested orders computation, tied to the product/warehouse unit (SKU)
see ORDER_CONFIGURATION where rewritable_for_plid = 1	see ORDER_CONFIGURATION	see ORDER_CONFIGURATION