Validation and error messages
This table lists the validation messages and their associated validation level which can be used in the ‘Stop on End Status’ parameter to determine whether the macro fails or is ignored.
| Validation Condition | Validation Message | Level |
|---|---|---|
| Checks that the Planning Engine Definition exists and is valid. | Planning Engine {0} cannot be created. Planning Engine Definition {1} cannot be found. | Error |
| Checks that the user has access to the Planning Engine Definition. | Planning Engine {0} cannot be created. User {1} does not have access to Planning Engine Definition {2}. | Error |
| Checks that the Planning Engine name does not already exist. | Cannot create Planning Engine {0}. Planning Engine already exists. | Warning |
| Checks that the user has permission to create Planning Engines. | Cannot create Planning Engine {0}. User {1} does not have appropriate permissions. | Error |
| Where specified, ensure the roles are valid. | Cannot create Planning Engine {0}. Role "{1}" cannot be found. | Error |
| Where specified, ensure the Tags are valid. | Cannot create Planning Engine {0}. Tag "{1}" cannot be found. | Error |
| If Tag Parameter is Null, ensure Planning Engine Definition, has valid Tags defined. | Cannot create Planning Engine {0}. Tags are undefined in Planning Engine Definition "{1}". | Error |
| Checks that the Calendar name is valid. | Cannot create Planning Engine {0}. Calendar {1} cannot be found. | Error |
| Checks that the StartPeriod is a valid base level bucket within the Calendar specified. | Cannot create Planning Engine {0}. StartPeriod {1} is not a valid base level calendar bucket in Calendar {2}. | Error |
| Checks that the Horizon is a valid integer. | Cannot create Planning Engine {0}. Horizon {1} is not a valid integer | Error |
| Checks that the Horizon does not exceed the size of the defined calendar from the Start Period |
Cannot create Planning Engine {0}. Calendar {1} does not contain sufficient {2} buckets from StartPeriod {3}. where {1} = Calendar parameter value, {2} = Horizon parameter value, 3 = StartPeriod parameter value. |
Error |
| If any of Calendar, StartPeriod or Horizon parameters are populated, then they must all be populated. | Cannot create Planning Engine {0}. Optional calendar parameters are used in conjunction and therefore must all be populated. Please check parameter values for Calendar {1}, StartPeriod {2} and Horizon {3}. | Error |
| Checks for the Name or Cycle are defined. | Cannot create Planning Engine no Name or Cycle are defined. | Error |
| Checks that the Calendar, StartPeriod or Horizon parameters are populated if Cycle is defined. | Cannot create Planning Engine {0} with Cycle {1}. All Calendar parameters are required when using a Cycle. Please check parameter values for Calendar {2}, StartPeriod {3} and Horizon {4}. | Error |
| If the Cycle is populated, check the cycle is defined. | Cannot create Planning Engine {0}, Cycle {1} is not defined. | Error |
| Checks that there is no other running or master Planning Engines with the same Cycle. | There is already a Running or Master Planning Engine using cycle {0}, the cycle is unique when creating a new planning engine. | Error |
| Checks that the Level definition is valid for the Calendar. | Cannot create Planning Engine {0}, Level {1} is invalid for Calendar {2}. | Error |
| Checks that the Planning Definition has Status Ready. | Cannot Create Planning Engine {1}. Planning Engine Definition {2} is invalid. | Error |