When upgrading an ENOVIA Variant Configuration Central database to V6R2012x, you should analyze your data to ensure that the following guidelines are met.
- There cannot be any parenthesis, ( or ), or space ' ' characters in a symbolic name. You must remove these characters and replace them with another character, such as an underscore _.
- There cannot be any custom types, relationships, attributes or policies that conflict with the V6R2012x ENOVIA Variant Configuration Central schema. For example, you cannot have a custom type, ‘GBOM’ as this is a new type installed with 2012x. You must modify your custom admin type so that there are no name conflicts. It is recommended to append a suffix of _custom to all custom schema that are in conflict. The following table summarizes the schema that were added for V6R2012x:
| Admin |
Name |
|---|
| Type |
CONFIGURATION FEATURES Configuration Feature Configuration Option LOGICAL STRUCTURES Logical Feature Manufacturing Feature |
| Relationship |
CONFIGURATION STRUCTURES Configuration Features Configuration Options Mandatory Configuration Features LOGICAL STRUCTURES Logical Features Logical Products MANUFACTURING STRUCTURES Manufacturing Features Candidate Configuration Features Candidate Manufacturing Features Committed Configuration Features Committed Logical Features Committed Manufacturing Features Committed Context GBOM Inactive GBOM Custom GBOM Inactive Custom GBOM Inactive Varies By GBOM Valid Contexts Invalid Contexts |
| Attribute |
Configuration Selection Criteria Configuration Selection Type Display Name Display Text Logical Selection Criteria Logical Selection Type Rolled-Up |
| Policy |
Configuration Feature Configuration Option Logical Feature Manufacturing Feature |
| Interface |
Inherited |
- If you have added any custom attributes on the Software Feature type, these attributes need to be added on the Logical Feature type after running the ENOVIA Business Process Services upgrade and before running ENOVIA Variant Configuration Central installation. If this step is not followed, those attributes will be lost.
- If the schema is inheriting any custom attributes from the Feature type, these attributes need to be moved to the corresponding new feature type (Configuration Feature, Configuration Option, Logical Feature or Manufacturing Feature), as appropriate. Additionally, any new custom types need to be created for all existing custom types, and should be derived from the new feature type (Configuration Feature, Configuration Option, Logical Feature or Manufacturing Feature), as appropriate. It will then be possible to use the Migration Property File Settings to migrate the old custom types to the new custom types.
- Any custom attributes that had been added to the Feature List or GBOM types need to be added to the appropriate new ENOVIA Variant Configuration Central schema types. It will then be required to write a custom migration method to migrate these custom attributes.
|