Validation of input measures

The validation of input measures for each item and location:

• The history and mask vectors must be of the same length (if the leading zeros are removed from the history vector).
• SCP does not store ‘0’ values. Therefore, any missing values after the first non-zero value are considered as 0 and included in the history vector at the appropriate point.
• The history and weighting measures must have at least one common period > 0 within the cycle period history horizon. Else, history data is not available for calculation. The item/location is not passed to the engine for processing and an appropriate exception is logged in the Audit Logs discard log.
• If the DoNotFit measure is mapped in the Mappings tab of the history replacement engine and the value is set as > 0 for an item and location combination, the history values of the item-location are not passed to the engine.
• Replacement Start Date is mapped to a Start History Index for the engine. This is the index number of the period containing the Replacement Start Date at the defined Period Level of the history replacement engine configuration. The index number is inclusive, that is Replacement Start Date >= PeriodLevel.PeriodStart and <= PeriodEnd. The corresponding period is converted to an index based on historic periods in the cycle period horizon at this level. ‘0’ indicates the oldest history period and the highest index represents the most recent history period prior to the current planning period.
  Note: If the value is not populated, the lowest history index ‘0’ (that is the oldest history period) is used.
• Replacement End Date is mapped to an End History Index for the engine. This is the index number of the period containing the Replacement End Date at the defined Period Level of the history replacement engine configuration. The corresponding period is converted to an index based on historic periods in the cycle period horizon at this level. ‘0’ indicates the oldest history period and the highest index represents the most recent history period prior to the current planning period.
  Note: If the value is not populated, the highest history index (that is the most recent history period) is considered.

  For example,

  Cycle = Demand (PW), Cycle History Horizon = 200 (PW), Cycle Period = FY19 M07.

  Engine.PeriodLevel = Months

  Index0 = FY16 M04, Index38 = FY19 M06

  ReplacementStartDate = 2019-03-01, ReplacementEndDate = 2019-06-01. Periods containing dates at PeriodLevel = FY19 M03 and FY19 M06, respectively.

  HistoryStartIndex = 35 (FY19 M03). HistoryEndIndex = 38 (FY19 M06).

• If index cannot be determined, that is, the specified start or end date is before the first non-zero history point or outside of the cycle period's history horizon, the item/location is not passed to the engine for processing and application logs this exception message in the Audit log's discard log:

  Replacement Start Date {0} is outside the first non-zero history point and the last history period. 

  Replacement End Date {0} is outside the first non-zero history point and the last history period.