The following table describes the analysis for variable mappings where variables associated with the source or target fields are different:
|
COLUMN |
CHANGE |
RESULT |
PROCESSING |
|
Coding Dictionary ID |
Null to Specified |
OK |
|
|
Coding Dictionary ID |
Specified to Null |
|
Deletes all coding values |
|
Coding Dictionary ID |
Different Dictionary |
|
Deletes all coding values |
|
Coding Dictionary ID |
Same Dictionary Name, different Dictionary version |
|
Deletes all coding entries where the dictionary code or level combination does not exist in the new dictionary version. |
|
Data Dictionary ID |
Null to Specified |
OK |
|
|
Data Dictionary ID |
Specified to Null |
OK |
|
|
Data Dictionary ID |
Different Dictionary |
OK |
|
|
Data Format |
Different Format |
OK |
|
|
Derivation ID |
Null to Specified |
OK |
|
|
Derivation ID |
Specified to Null |
OK |
|
|
Derivation ID |
Different Derivation |
OK |
|
|
OID |
Different Name |
|
The variable was mapped manually to a different OID. |
|
Unit Dictionary ID |
Null to Specify |
OK |
|
|
Unit Dictionary ID |
Specify to Null |
OK |
|
|
Unit Dictionary ID |
Different Dictionary |
OK |
|
|
Variable Name |
Different Name |
OK |
|
Note: If the original data becomes non conformant prior to migration, the system sets the field to non conformant after migration. For example, if the original field format was $30 and on entering a string of data that is 27 characters, becomes a new field format $15. after migration, this field is set to non conformant.
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.