Setup checks and messages

The Setup Checker page displays the subsequent levels of check, based on the Configuration menu structure. To view a functional area's checks and messages, click the appropriate link:

These tables show the checks that are performed and the messages that can be displayed:

Cycle


Code	Check	Status	Message
SC001	Check the validity of each of the module hierarchy selections. Modules that are not selected are flagged. Or, if a previously selected location hierarchy is deleted, the selection is no longer valid and the value is NULL in the Cycles page and is flagged.	Warning	Cycle period [cycle]-[period] with the [module] module and the required fields, which are not completed. The [module] module is unavailable.
SC004	Check for a calendar selection in the cycle period. If the user deletes the calendar that is defined in the cycle, the selection is no longer NULL and is flagged.	Incomplete	Cycle [cycle] with no Calendar defined.
SC005	Check for a calendar level to store the scenario values in the cycle period. If the user updates the selected calendar, the level selection can be invalid. For example, the removal of the quarters from the selected calendar can generate an error, if the quarters are the default calendar level. The selection is no longer valid and the value is NULL.	Incomplete	Cycle [cycle] with no Calendar level defined.
SC007	Check for an item hierarchy in the cycle period. If the user deletes the selected item hierarchy, the selection in Cycles is no longer valid and the selection is marked NULL.	Incomplete	Cycle period [cycle]-[period] with no Item Hierarchy defined.
SC008	Check for an item hierarchy level to store scenario values in the cycle period. If the user updates the selected item hierarchy, the selection can be invalid. For example, the removal of a level from the selected hierarchy can generate an error. The selection is no longer valid and is marked NULL.	Incomplete	Cycle period [cycle]-[period] with no Item Hierarchy level defined.
SC009	Check for a base currency in the cycle period. If the currency from MDM is deleted, the selection in Cycles is no longer valid and the selection is marked NULL.	Incomplete	Cycle period [cycle]-[period] with no Base Currency defined.
SC040	Check for a periodicity selection. If the user updates the selected calendar, the level selection can be invalid. For example, the removal of the quarters from the selected calendar can generate an error, if quarters are the periodicity setting for this cycle. The selection is no longer valid and is marked NULL, which leads to this error.	Incomplete	Cycle [cycle] with no periodicity defined.
SC041	Check for a cycle process selection. If the user deletes the selected cycle process, the selection is no longer valid and is marked NULL. The cycle can be created successfully without a process definition, but data is blank and can differ from the expected result, if a process is previously defined.	Warning	Cycle period [cycle]-[period] with no cycle process defined.
SC042	Check the validity of the scenario process selection, for each default scenario. If the user deletes the selected scenario process, the selection is no longer valid and is marked NULL. As the default scenarios are versioned, at the time of creating a cycle period (not starting), this check must be made against the cycle definition and the creation of a new cycle period must be prevented.	Incomplete	Cycle [cycle] with a default scenario [scenario] and no scenario process defined.
SC043	Check the validity of the initialization macro selection for each default scenario. It the macro is deleted, the selection is no longer valid and is marked NULL. The status is set to Warning, because the scenario is successfully created without a workflow, but may differ from the expected result if a workflow is previously defined.	Warning	Cycle period [cycle]-[period] with a default scenario [scenario], and no initialization macro defined.
SC074	Check that the cycle is set up to start automatically (Process is Started > Manually), but the Next Period field is empty (NULL). In this case, the application cannot automatically create periods for this cycle because the period that must be started cannot be determined. The user must edit the cycle definition and set a valid Next Period value or set Process is Started to Manually.	Warning	Cycle [cycle] with the automatic 'Process is Started' setting, however the Next Period is not determined. No new cycle periods are started by the system until the Next Period is populated with a period value. (Configuration \ Cycle). If automatic creation of new cycle periods is not required set 'Process is Started' = Manually.
SC075	Check the status of the calendar in Cycles. If the status is Invalid due to a failure during the creation of calendar buckets, or the calendar has Disabled status, an issue is raised.	Incomplete	Cycle is using calendar "{0})" with a status "Invalid" or "Disabled". Revise the calendar definition and correct the problem before starting the cycle period.
SC096	Check the cycle process linked to a cycle. If a cycle process setup is invalid, the start of the cycle period is prevented.	Incomplete	Cycle [cycle] using cycle process [cycle process] with an invalid setup. Revise the cycle process and rectify before the creation of a new cycle period for this cycle.
SC098	Check the planning hierarchies linked to a cycle. If a planning hierarchy setup is invalid or disabled, the start of the cycle period is prevented.	Incomplete	Cycle is using a planning hierarchy [planning hierarchy] with status Invalid or Disabled. Revise the planning hierarchy and correct the problem before starting the cycle period.
SC102	A module defined in Cycles does not contain measures. This prevents the creation of the measure dimension in the cube, causing problems. At least one measure must be defined for each module.	Incomplete	Cycle period [cycle]-[period] contains a module [module] that does not have measures defined. Disable this module in the Cycle, or define at least one measure for this module.
SC103	The additional planning hierarchy definitions must be complete. If a planning hierarchy that is in use by a cycle as an additional hierarchy is deleted, this leads to an incomplete definition.	Incomplete	Cycle period [cycle]-[period] with an incomplete additional planning hierarchy definition for module [module].
SC106	If the cycle process is set to start automatically, check that the previous cycle period can be calculated.	Warning	Cycle period [cycle]-[period] with an automatic 'Process is Started' setting. However, the previous cycle period cannot be calculated.
SC107	If an additional Pivot Attribute is defined in the cycle, all elements of the selected code list must be populated for that attribute. If a null value exists for any element in the corresponding code list, the cube is not populated correctly.	Incomplete	Cycle period [cycle]-[period] with an additional pivot attribute defined [code list].[attribute], which contains undefined values for elements within the code list. All code list elements must be populated for this to be a valid additional pivot attribute for this cycle.
SC108	Check the note type for a mandatory note during unlock and save changes. If a note type that is in use by a cycle is deleted, this leads to an incomplete definition.	Incomplete	Cycle period [cycle]-[period] with the Force Add Note on Unlock selected but no valid Default Note Type selected. Select a new note type or clear the Force Add Note on Unlock option
SC109	Check the note type for a mandatory note during worksheet recalculation. If a note type that is in use by a cycle is deleted, this leads to an incomplete definition.	Incomplete	Cycle period [cycle]-[period] with the Force Add Note on Recalculate selected but no valid Default Note Type selected. Select a new note type or clear the Force Add Note on Recalculate option
SC124	Check the measures that are used in a cycle. If the setup for the measure is invalid, the start of the cycle period is prevented.	Incomplete	Cycle period [cycle]-[period] is using a measure [measure] with an invalid setup. Revise the measure and correct the problem before starting the cycle period.
SC126	Check to ensure that the location hierarchy selection for each module is a planning hierarchy with defined levels, as the bottom level of each module's location hierarchy is used as the level to store scenario values.	Incomplete	Cycle period [cycle]-[period] is using a location hierarchy [hierarchy] with no levels defined. Revise the location hierarchy selection for module [module] and correct the problem before starting the cycle period
SC127	Verify that at least one module hierarchy is selected for a cycle.	Incomplete	Cycle "{0}" with no location hierarchies defined. Define a location hierarchy for at least one module.
SC128	Verify that the cycle has a valid combination of modules (location hierarchies selected). If a planning hierarchy is removed, the combination of modules can become invalid for a cycle.	Incomplete	Cycle has an invalid planning hierarchy selection of ("{0}", "{1}", "{2}", "{3}"). Revise the cycle and select location hierarchies for a valid combination of modules.
SC131	Check to ensure that any additional pivot attributes that are defined against the cycle do not contain values longer than 71 characters.	Incomplete	Cycle [cycle] with an additional pivot attribute defined [code list].[attribute], which contains elements greater than 71 characters. Modify each element to be not more than 71 characters for this attribute.
SC133	Check enabled calculation rules for the cycle to ensure that the referenced measures are also enabled for this cycle.	Warning	Cycle has a calculation rule [calc-rule] which references a measure [measure] that is not enabled for the cycle.
SC135	Create a set in the OLAP dimensions that corresponds to each level in the planning hierarchies used by a cycle, using Set and the level name (for example, Set_Level4Items). You must check if all the hierarchies for a dimension have a unique level name, wherein the code list differs. A same code list and level name can be used because you create the set for a unique code list. Level1 of a hierarchy is not checked as this contains a single element (no Set required).	Incomplete	Cycle has {0} hierarchies "{1}" with a non-unique level "{2}" that does not validate the {3} data cube. Edit the hierarchies to make all non-root levels unique.
SC137	When additional pivot attributes are defined for a cycle, check that the hierarchy used contains the same list of elements as the corresponding Cycle. Module hierarchy.	Incomplete	Cycle contains a {0} pivot attribute {1} for module {2} which is based on a hierarchy that contains elements which do not match the distinct pivot attributes.
SC139	Check if all the node/level names referenced by business metrics are valid when the cycle period is started/resumed.	Incomplete	Cycle contains a business metric "{0}" which refers to invalid "{1}" with names: "{2}"
SC140	Check additional hierarchies in comparison with the cycle hierarchies that do not have levels shared with the primary hierarchy, above the base level, and are not in sequence (consecutive) from the base level and higher.	Incomplete	Cycle includes hierarchies "{0}, {1}" with shared elements which are non-consecutive from the base level upwards. For shared elements, the child levels must also be shared in both hierarchies up to the base level. ({2})
SC141	Check additional hierarchies defined in comparison with the cycle hierarchies that have the same parent definitions for any shared levels. Different hierarchies can have different parent attributes and therefore, parent-child associations. Primary and Additional hierarchies in the Cycle with different parent-child relations for the shared levels are not allowed. The top shared level can have a different parent.	Incomplete	Cycle includes hierarchies "{0}, {1}" with shared elements on two or more levels; however some shared child levels are linked to different parent levels in the two hierarchies. ({2})
SC142	Check if any additional location hierarchies have a suitable primary location hierarchy defined for the specified module. There is no restriction on defining an additional hierarchy within any module.	Warning	Cycle with an additional hierarchy "{0}" of type location for module {1}, although the correspondent primary hierarchy is not defined. This additional hierarchy is not considered.
SC143	Check additional hierarchies to ensure that the root node is not the same as the primary hierarchy. Hierarchies can share levels from the base. However, the root node must be different.	Incomplete	Cycle has a hierarchy "{0}" which has a root element that is a duplicate of an element in another hierarchy "{1}". The root element must be unique. "{2}".
SC144	Check that each rolling period definition contains a calendar level that exists in the selected calendar.	Incomplete	Cycle has a Rolling Period [RP Top Level] which uses a calendar level that is not defined.
SC145	Check that each rolling period definition contains a calendar that is valid for the current cycle, based on the primary calendar or additional period hierarchies.	Incomplete	Cycle "{0}" with a Rolling Period "{1}" which uses a calendar that does not match either the primary calendar "{2}" or any calendars referenced in additional planning hierarchies "{3}".
SC146	Check that each rolling period definition is linked to a valid periodicity selection, based on the cycle periodicity and calendar level, to store scenario values. The selected periodicity must be between these ranges.	Incomplete	Cycle "{0}" with a Rolling Period "{1}" and a periodicity below "{2}".
SC147	Validate that all nodes between all period hierarchies defined for the cycle level are unique (except the shared bottom level).	Incomplete	Cycle with period hierarchies "{0}" which contain a non-unique node "{1}" that does not validate the {2} data cube.
SC149	Check business metrics for the cycle to ensure that the base measure is also enabled for this cycle.	Warning	Cycle has a business metric "{0}" which references a measure "{1}" that is not enabled for the cycle.
SC150	Check whether the current planning period can be defined.	Incomplete	Cycle Period "{0}" with no available planning periods.
SC152	An expert calculation rule can have a null target measure, using the filter field to specify the target. If a measure is removed, this cascade to a linked calculation rules, however, only invalidates the rule where no filter exists. Check for the existence of a measure or filter on all (expert) calculation rules.	Warning	Calculation rule with module {0} and calculation sequence {1} with neither Filter nor Measure defined.
SC153	If background validation is in progress for a planning hierarchy that is in use by the cycle, this cannot be started or resumed (with refresh).	Incomplete	Planning hierarchy "{0}" with a status = "Building". The processes for the hierarchy must be executed prior to starting a new cycle period.
SC154	If background validation is in progress for a calendar that is in use by the cycle, this cannot be started or resumed (with refresh).	Incomplete	Calendar "{0}" with a status = "Building". The processes for the calendar must be executed prior to starting a new cycle period.
SC155	When part-weeks are enabled for a cycle, the calendar level to store scenario values must also be set to part-weeks.	Incomplete	Cycle is using a calendar with part-weeks enabled, but has the wrong calendar level {1} selected, it should be using {2}.
SC156	Check whether the interpolation calendar and an enabled period spread measure are defined as these are required to automatically create the period spread measure. If the base measure or interpolation calendar is deleted, then it will be removed from the cycle meaning the definition is not complete and cannot be started or resumed (with refresh).	Incomplete	Cycle must have an enabled Period Spread Measure and Interpolation Calendar defined. Both are required to create a default spread measure for periods
SC157	Check the pivot attributes selected for use within the Cycle are of type Text. Only code list elements that are of type text can be used as pivot attributes.	Incomplete	Cycle has a {0} pivot attribute "{1}" for module {2} which is not of type Text in the code list "{3}". Pivot Attributes must be type=Text
SC158	Check business metrics for the cycle to ensure that the base measure is also enabled for this cycle.	Warning	Cycle has a business metric {0} which references a measure {1} that is not enabled for the cycle.
SC163	Check whether the macros defined within the initialization macro are correctly tagged for the Cycle. In this situation the macro is not executed upon start of a cycle period.	Warning	Cycle has default scenario " {0}" whose initialization macro is not enabled for the cycle with tags.
SC164	Check whether a Market Intelligence record for which the tag is set to enabled in a cycle, references any measures for which tags are not enabled for the same cycle. In this situation, the MI record is invalid and is not created at the start of a cycle period.	Warning	Cycle has an enabled Market Intelligence {0} which references measures {1,2,3 ...} that are not enabled for the cycle. Enable the relevant tags in the Cycle Configuration window.
SC165	Check whether multiple MI records using the same measure/module are set to enabled for the same cycle. In this situation, the MI records are invalid and are not created at the start of a cycle period.	Warning	Cycle has more than one enabled Market Intelligence record for module "{0}" using the same measure "{1}
SC166	Check whether multiple enabled MI records with the same Net Forecast Measure are set to Edit Net Forecast Directly. The Net Forecast Measure can only be edited directly in one MI record. In this situation, the MI records are invalid and are not created at the start of a cycle period.	Warning	Cycle has more than one enabled Market Intelligence record for module "{0}" using the same Net Forecast Measure "{1} set to Edit Net Forecast Directly.
SC168	Check whether a calculation rule is based on a measure which is defined as a Market Intelligence record. In this situation, the calculation rule is invalid and is not created a the start of a cycle period.	Warning	Cycle has an enabled Calculation rule {0} which is based on a measure {1} that is defined as a Market Intelligence record. Update the Calculation rule accordingly.
SC169	Check whether a calculation rule is based on a measure which is defined as a Transactional Data record and both are enabled for the same cycle. In this situation, the calculation rule is invalid and is not created at the start of a cycle period.	Warning	Cycle has an enabled Calculation rule {0} which is based on a measure {1} that is defined as a Transactional Data record. Update the Calculation rule accordingly.
SC170	Check whether a measure is defined as a Transactional Data record and is enabled in a cycle, which also is defined as a Market Intelligence record and enabled for the same cycle. In this situation, the measure is invalid and the configuration cannot be completed.	Incomplete	Cycle has an enabled measure {0} which is defined as a Transactional Data record and a Market Intelligence record. Measure can only be used in one definition.
SC173	Check whether an enabled MI definition has the MI measure defined as a Net Forecast Measure in another enabled MI definition.	Warning	Cycle has an enabled Market Intelligence Measure {0} whose Net Forecast Measure measure {1} is defined as a Market Intelligence Measure. Update the Market Intelligence measure accordingly.
SC176	If a Replenishment Engine is defined, check that the engine is enabled for the cycle. If the engine is not enabled, the engine is not available for selection for the cycle.	Warning	Cycle has a Replenishment Engine {0} which is not enabled for the cycle.
SC177	Check to ensure no duplicate components in the rolling period.	Incomplete	Cycle has a rolling period "{0}" which has a "{1}" element that is a duplicate of an element in another hierarchy "{2}". This element must be unique. "{3}"
SC179	If the cycle has an enabled Replenishment Engine, check the defined Supply Allocations for the engine settings (with measures), contain valid attributes in the base code list of the cycle’s item and location hierarchies for the specified module of the engine. Checks against Item dimension = Item attribute, Routing (item) Location dimension = Location attribute, Source Location, Customer, Supplier, Resource, Routing (location).	Incomplete	Cycle has a Replenishment Engine {0} with Supply Allocation {1} which contains an Attribute {2} which cannot be found in the {3} dimension.
SC180	If the cycle has an enabled Replenishment Engine, check that the Order Data Measures defined in the engine settings are enabled for this cycle and exist for this cycle.	Incomplete	Cycle has a Replenishment Engine {0} which contains an Order Data Mapping {1} which is incomplete or not enabled for the cycle.
SC181	If the cycle has an enabled Replenishment Engine, check the measures defined in Item Location Measure Mapping, Purchase Measure Mapping, Transfer In Measure Mapping, and Transfer Out Measure Mapping for the engine settings are enabled (tagged) and available for this cycle and module.	Incomplete	Cycle has a Replenishment Engine {0} where the Measure Mapping {1} is incomplete or not enabled.
SC182	If the cycle has an enabled Replenishment Engine, check each calendar defined in Engine Calendar Mappings for the engine settings is complete. If the interpolation calendar is deleted, it is removed from the cycle meaning the definition is not complete and cannot be started or resumed (with refresh).	Incomplete	Cycle has a Replenishment Engine {0} with Calendar Mapping {1} that is incomplete.
SC183	If the cycle has an enabled Replenishment Engine, check that the measures defined in Item Location Measure Mappings for output parameters, are not Market Intelligence measures.	Incomplete	Cycle has a Replenishment Engine {0} where the Measure Mapping {1} is a Market Intelligence measure. Measures of this type are not allowed for engine output.
SC184	If the cycle has an enabled Replenishment Engine, check that the measures defined in Item Location Measure Mappings for output parameters, are not Transactional Data measures.	Incomplete	Cycle has a Replenishment Engine "{0}" with Measure Mapping "{1}" that is a Transactional Data measure. Measures of this type are not allowed for engine output.
SC185	If the cycle has an enabled Replenishment Engine, check that at least one supply allocation mapping is defined. We can define an RP engine with one supply allocation type mapped, however, the measure referenced in that mapping is deleted. In this case we no longer have a supply allocation types mapped, and we always require at least one type mapped for the engine to be valid.	Incomplete	Cycle has a Replenishment Engine {0} for which some supply allocation measure mappings {1} are undefined.
SC187	Check whether a Transactional Data definition whose tag is set to enabled in a cycle references measures whose tags are not enabled for the same cycle. In this situation the Transactional data definition is invalid and is not created upon start of a cycle period.	Warning	Cycle has an enabled Transactional Data {0} which references measure {0} which is not enabled for the cycle. Enable the relevant tags in the cycle configuration screen.
SC189	Check whether multiple Transactional Data definitions using the same measure or module are set to enabled for the same cycle. In this case, the Transactional Data records are invalid and not be created upon start of a cycle period.	Warning	Cycle has more than one enabled Transaction Data for module "{0}" referencing the same measure "{1}
SC193	If Enable Telescopic is defined, ensure all calendar levels defined are available within the primary Calendar hierarchy.	Incomplete	Cycle is set to use Telescopic Calendar buckets for Calendar Levels that cannot be found.
SC194	If Enable Telescopic is defined, ensure all Horizon Levels used to determine granularity are available within the primary Calendar hierarchy.	Incomplete	Cycle is set to use Telescopic Calendar buckets which references Horizon Levels that cannot be found.
SC199	Check whether the macro defined as the initialization macro is enabled or accessible to users. Else, the macro is not executed upon start of the cycle period.	Warning	Cycle has default scenario "{0}" with an Initialization macro {1} which is not enabled or user does not have access.
SC201	Check that all transactional data measures used within a cycle, contain unique to (destination) and from (source) measures.	Incomplete	Cycle has a measure "{0}" that is used in more than one Transactional Data definition. A given measure can only be used in one Transactional Data, and as source or destination only.
SC202	Check attributes which are included in the hierarchy (that is, Include = True/ON) that the names of the attributes do not contain invalid characters. Note: The planning hierarchy is not invalidated by invalid characters.	Warning	Cycle has a planning hierarchy ""{0}"" with Included attribute ""{1}"" which contain invalid characters ""{2}"" This attribute is not available in the cycle. ""{0}"" = Planning Hierarchy display name ""{1}"" = Attribute name ""{2}"" = Invalid character

Code list


Code	Check	Status	Message
SC095	Code List element name has a limit of 71 characters due to a restriction on each element name within OLAP.	Warning	Code List [code list] contains element names greater than 71 characters. Modify each element name to be no more than 71 characters.

Calendar


Code	Check	Status	Message
SC017	Check for the existence of a calendar.	Incomplete	No Calendars defined.
SC018	Check that the calendar ending year is current, that is, this year or some time in the future.	Warning	Calendar [calendar] horizon is in the past.

Interface Service/Data Source


Code	Check	Status	Message
SC020	Check for the existence of an interface service.	Incomplete	No Interface Services defined
SC022	Check the validity of the import/export measure selection(s). If the user deletes a measure that is defined in the interface service, the entry is incomplete. For example, the removal of a measure defined in an interface service prevents that measure from being imported/exported as part of the interface service. The status is Warning because, although other defined measures may be valid, running the interface service in this state generates unexpected results.	Incomplete	Interface Service [service] has an incomplete measure entry. The associated measure label is [measurelabel].
SC070	Check the validity of the data source selection. If the data source is deleted, the value is NULL and the interface service definition becomes incomplete.	Incomplete	Interface Service [service] with no Data Source defined.
SC024	Check for the existence of a data source.	Incomplete	No Data Sources defined.

Measure/Calculation Rule


Code	Check	Status	Message
SC027	Check for the existence of measures.	Incomplete	No Measures defined.
SC028	Check for a unit of measure selection. If the unit of measure or currency from MDM is deleted, the selection in Measure is no longer valid and is marked NULL. If no measures are defined for any modules, the status is set to Warning. Otherwise, the status is set to Incomplete.	Incomplete/ Warning	Measure [measure] with no Unit of Measure defined.
SC030	Check for the existence of calculation rules.	Warning	No Calculation Rules defined
SC031	Check the completeness of a simple calculation rule definition by the measures selected. If one of the measures used in a rule is deleted, the selection is longer valid and is marked NULL. If no measure is defined, the status is set to Warning. Otherwise, the status is set to Incomplete.	Incomplete/ Warning	Simple calculation rule [rule] refers to a measure which no longer exists.
SC072	Check the simple or expert calculation rule definition to ensure that the measure code on which the rule is based is valid. If the measure used in the rule is deleted, the measure selection is no longer valid and is marked NULL. The user must correct this before using the calculation rule	Incomplete	Calculation rule [rule] with no measure defined.
SC167	Check the completeness of a Market Intelligence definition. If one of the measures used in the definition is deleted then the MI definition is no longer valid. In this situation, the MI records are invalid and are not created at the start of a cycle period.	Warning	Market Intelligence {0} refers to a measure which no longer exists.

Note Type


Code	Check	Status	Message
SC033	Check for the existence of an enabled note type.	Warning	No Note Types are enabled.

Planning Hierarchy


Code	Check	Status	Message
SC035	Check for the existence of a planning hierarchy.	Incomplete	No Planning Hierarchies defined.
SC097	Check the Planning Hierarchies do not contain an element whose name is one of the following reserved words: ICONST, CONST, and PCONST.	Warning	Code List "Code List Name" contains an element with name "ICONST" or "LCONST" or "PCONST". Modify the name of this element.
SC132	Check the status of a planning hierarchy. If Invalid, a Warning is displayed.	Warning	Planning hierarchy [hierarchy] has a status Invalid.

Cycle process


Code	Check	Status	Message
SC054	Check for the existence of a cycle process.	Incomplete	No Cycle Processes defined.
SC055	Check each cycle process event for a task management workflow selection. If the workflow from WLM is deleted, the selection in Cycle Process is no longer valid and the selection is marked NULL. If no cycle process is defined for any cycles, the status is set to Warning. Otherwise, the status is set to Incomplete.	Incomplete/ Warning	Cycle Process event for [process] with no Task Management Workflow defined.

Mapping


Code	Check	Status	Message
SC057	Check that each of the hierarchies that are defined in the mapping is a valid planning hierarchy.	Warning	Mapping "{0}" is using hierarchy "{1}" with a status "Incomplete". Revise the hierarchy and correct the problem before the creation of new mapping.
SC058	Check for a source hierarchy level selection. If a previously selected location hierarchy is edited or deleted so that the selection is no longer valid, the location hierarchy is marked NULL in the associated mapping and flagged.	Warning	Mapping [mapping] with no Source Hierarchy level defined.
SC059	Check for a destination hierarchy level selection. If a previously selected location hierarchy is edited or deleted so that the selection is no longer valid, the location hierarchy is marked NULL in the associated mapping and flagged.	Warning	Mapping [mapping] with no Destination Hierarchy level defined.
SC094	Check each mapping for status = Invalid and display a warning here. Any mapping can be used in a macro, however, if the status = Invalid, the execution of the macro fails.	Warning	Mapping [mapping] with a status = Invalid. The mapping must be corrected prior to usage.
SC122	Any code list used as part of a mapping definition requires additional validation upon changes to the mapping configuration or changes to the code list attributes or elements. The share factor defined for each mapping pair must be a positive number > 0.	Warning	Mapping [mapping] contains a share attribute value [share] that is invalid. Edit the associated code list [code list] to ensure the share of each element is a positive number greater than 0.
SC123	Any code list used as part of a mapping definition requires additional validation upon changes to the mapping configuration or changes to the code list attributes or elements. Each source and destination combination must appear only once.	Warning	Mapping [mapping] contains a duplicate mapping pair [source]-[destination], which may lead to unexpected results. Review the associated code list [code list] to remove duplicates and ensure that the correct mapping pair is used.

Replenishment Engine


Code	Check	Status	Message
SC200	Check the replenishment engine has all required attributes populated when the supply allocation measure is also populated.	Incomplete	Cycle has a Replenishment Engine {0} with Supply Allocation {1} which does not have required attribute {2}