Appendix

This section contains special case scenarios and additional information about the processes taking place during the migration.

1. Ignore List
2. Disable Copy Node List
3. Disable Copy Value List
4. Category Definition
5. Exception Scenarios
6. Merge Rules
7. MDX Script
8. Renaming Measures
9. Validation Rules
10. Tree Node Ignore List

Ignore List

The list of ignored nodes contains the XPath of the nodes in the .ASDATABASE XML file that are not compared by the tool (MDX scripts are on the list because they constitute special procedures). The current implementation of the DELMIA Apriso MPI Migration tool does not allow the user to alter this list.

• Dimensions/Dimension/Annotations
• Cubes/Cube/Annotations
• Cubes/Cube/MdxScripts
• Dimensions/Dimension/Attributes/Attribute/AttributeRelationships
• Dimensions/Dimension/Hierarchies
• Dimensions/Dimension/Attributes/Attribute/KeyColumnsDataSourceViews/DataSourceView/Annotation

Disable Copy Node List

A Merge Instruction with the Copy Node action for a node name that is in the list below sets the Enable field to false by default. This value can be manually changed by the user.

• NameColumn
• CaptionColumn

Disable Copy Value List

A Merge Instruction with the Copy Value action for a node name that is in the list below sets the Enable field to false by default. This value can be manually changed by the user.

• ID
• Name
• Description
• DimensionID
• DataType
• TableID
• ColumnID
• DataSize

Category Definition

The list below outlines each category by specifying the XPath of the node where the entities are defined in the .ASDATABASE XML file structure. These categories are displayed on the Compare Files page (on the Compare Results tree).

Exception Scenarios

Exception scenarios define the situations when a comparison cannot be performed.

• KPI IDs are automatically generated (e.g., Kpi, Kpi 1, Kpi 2, etc.), which is why the ID must be kept when it is referenced in a given perspective of a Cube
• The Update flag (Enable) should be set to false for KPI changes
• The Update flag should only be set to true if new KPIs are created



• The Dimension Attribute Name cannot be changed for a given ID
• The Dimension attribute relationship requires both the ID and the Name to match
• If the name changes, the attribute relationship will be invalid, which is why there are no Merge Instructions for attributes (they are not merged)

Merge Rules

1. If a node has an attribute named Type, it is considered a binding type node. In this case:
   • The values of the attribute type must match in order to perform the comparison of their child node
   • If a new Type node is detected, the Add Merge Instruction is created but the Enable flag is set to false by default
2. Nodes with a child node with the names of ID and Name are considered keys for the entity (e.g., Dimension). These values should be unique values in all of the IDs and Names of the similar node entity.
3. By default, Copy Value and Copy Node Merge Instructions have the Enable flag set to false for the node name listed in the Disable Copy Value Disabled List and Disable Copy Node Disabled List respectively. Merge Instructions are not created when a new ID is encountered but the Name already exists.

MDX Script

1. A new Measure Name is only detected in the MDX script in Your Existing Version. Measure contents with the same Measure Name are not compared.
2. A Measure Name must have the following format in the MDX script: [Measures].[<measure name>]. Non-conforming Measure Names are ignored.

Renaming Measures

The Rename Measure Configuration file, RenameMeasuresConfig.xml, is located in the same directory as the DELMIA Apriso MPI Migration tool. If the location of this file is changed, the file path and the name must be updated in the MPIMigration.exe.config file under the <appSettings> section.

The Rename Measure Configuration file contains two sections: RenameMDX and RenameMeasures. Under each section there is a list of Measure Names to be renamed. They are specified by the FromValue and ToValue attributes.

Rename Measure Configuration File Structure

<MPIMigration_RenameConfig>
   <RenameMDX>
       <Rename FromValue="[Measures].[Operation STD Quantity Variance]" ToValue="[Measures].[Operation STD Quantity]"/>
       <Rename FromValue="[Measures].[Planned Down Time]" ToValue="[Measures].[Planned Downtime]"/>
   </RenameMDX>
   <RenameMeasures>
       <RenameMeasure FromValue="[Measures].[Operation STD Quantity]" ToValue="[Measures].[WIP Order Count]"/>
   </RenameMeasures>
</MPIMigration_RenameConfig>

Scenario 1 – Rename Calculated in Measures in MDX Script

This scenario handles the renaming of measures defined inside the MDX script. The measures that matched the From Value in the MDX script and which are under the Calculation Reference are to be renamed according to the Rename Measure Configuration file under the RenameMDX section.

Below are some example rename entries under the RenameMDX section:

• Under Cubes/Cube/MdxScripts/MdxScript/Commands/Command/Text
  • Change [Measures].[<FromMeasureValue>] to [Measures].[<ToMeasureValue>]
• Under Cubes/Cube/MdxScripts/MdxScript/CalculationProperties/CalculationProperty/CalculationReference
  • Change [Measures].[< FromMeasureValue>] to [Measures].[<ToMeasureValue>]
• Rename Measure Names in Perspectives under the Name node under Cubes/Cube/Perspectives/Perspective/Calculations/Calculation/Name
  • Change [Measures].[< FromMeasureValue>] to [Measures]. [<ToMeasureValue>]

Scenario 2 – Rename the Raw Measures under Measure Groups

This scenario handles the renaming of measures that matched the From Value under Measure Groups to new Measure Names specified by the To Value according to the Rename Measures Configuration file under the RenameMeasures section.

Below are some example rename entries under the RenameMeasures section:

• Rename Measure Names under Measure Groups. Under Cubes/Cube/MeasureGroups/MeasureGroup/Measures/Measure/Name
  • Change <FromMeasureValue> to <ToMeasureValue>
• Under Cubes/Cube/MdxScripts/MdxScript/Commands/Command/Text
  • Change [Measures].[<FromMeasureValue>] to [Measures].[<ToMeasureValue>]
• Under Cubes/Cube/MdxScripts/MdxScript/CalculationProperties/CalculationProperty/CalculationReference
  • Change [Measures].[<FromMeasureValue>] to [Measures].[<ToMeasureValue>]

Validation Rules

Validation rules are applied against the new .ASDATABASE file resulting from the merge process. It is not enough to have the syntax of the .ASDATABASE file correct – the relationship of the entities must also be correct.

• The Measure Name must be unique throughout the Cube
  • A warning message will be displayed if duplicate Measure Names are encountered
• The Measure ID must be unique throughout the Cube
  • A warning message will be displayed if duplicate Measure IDs are encountered
• The CubeDimensionID must have a correct reference to the DimensionID under Cubes/Cube/Dimensions/Dimension/ID, e.g., <CubeDimensionID>MACHINE</CubeDimensionID> wherein MACHINE must be defined under Cubes/Cube/Dimensions/Dimension/ID
• IntermediateCubeDimensionID must have a correct reference to the CubeDimensionID under Cubes/Cube/Dimension/Dimension/ID, e.g., <IntermediateCubeDimensionID>MACHINE</IntermediateCubeDimensionID> wherein MACHINE must be defined under Cubes/Cube/Dimensions/Dimension/ID

• The Dimension ID/Name and Cube Dimension ID/Name can be different, for example:

Dimension ID and Name:



Cube Dimension ID and Name that inherits from Dimension ID = Group:



• The AttributeID must be unique in the AttributeRelationship for a particular Dimension
  
  • Also, the Name and AttributeID must match (if they do not, a warning message is displayed)

Tree Node Ignore List

The tree control on the Compare Files page displays the result of the comparing process, but sometimes it can be filled with internal properties that are not important to the user. To reduce the redundant properties presented at each entity, the following properties are not displayed on the tree:

• CreatedTimestamp
• LastSchemaUpdate
• State
• LastProcessed

This can sometimes result in the nodes on the tree not displaying any child nodes or other properties.