<Bold>DCA Utility for PLM (PLM.DCA.Utility.exe)</Bold>

<Bold>General</Bold>
<Bold>About DCA Utility for PLM</Bold>
The DCA Utility for PLM is used as a part of Data Migration project. And this utility is used prior to performing Data Migration process (via the DCA Application). 

Due to data model changes and functional enhancements in target application and technical constraints of DCA Tool, data migration logic of certain tables requires pre-processing of data; where-in data is generated into interim tables. 

Also, as master data (standard data dumps) too is provided as part of standard target application, data migration logic of certain tables requires custom approach for migration; where-in instead of creating the data dumps using the DCA Tool, the data is Exported as XML files and then imported in the target application through a special session “PLM Data Migration: Pre/Post Operations” (pdadm8161m00). 

As Text Data and Thumbnail Images are stored differently in the target application, as compared to source application, these too requires different approach. These are not exported via DCA Tool, instead these are exported via this utility and imported via a special session “PLM Data Migration: Pre/Post Operations” (pdadm8161m00). 

This utility also provides ability for a data migration user to analyze the differences in the meta-data of the
<List>
<ListItem>
	Customized Source Application wrt Standard Source Application. 
</ListItem>
<ListItem>
	Customized Target Application wrt Standard Target Application.
</ListItem>
</List>


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Known Issues/Limitations</Bold>
<List>
<ListItem>
	<Bold>Issue with DataGrid Control</Bold>
	If filter conditions are set in the Secondary Grid, then secondary grid does not listen to Items Selection Event of Primary Grid. 
	It is requested to carefully use the filter conditions provided on the Data Grid control of this utility.
</ListItem>
<ListItem>
	<Bold>Text Data</Bold>
	Migration of Text Data (fields of type “Text”) is supported only for those tables whose indices in the target contains only the fields of type “String” or “Enum” or “Integer”. 
</ListItem>
<ListItem>
	<Bold>Migration Profile Tab (under "Standard" tab)</Bold>
	If a Mapping Script has multiple dumps, then this will not show it correctly. 
	This also does not take into account the migration profile derivation structure. This means that, if the Standard Migration Profile is derived from any other Migration Profile, then it will not show the mapping rules of the parent profile.
	It is advised to refer to Mapping Scripts in the DCA Application Server.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>General/Tabs Details</Bold>
Provides a summary of various tabs in this dialog.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Database</Bold>
Use this tab to specify the database connection details.

Connection details can be specified for following databases:
<List>
<ListItem>
	Standard Application
</ListItem>
<ListItem>
	Custom Application
</ListItem>
<ListItem>
	DCA Application
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Database/Standard</Bold>
This is used by PLM Development Team. 
Use this tab to specify the database details of Standard Application and download meta-data into xml files. 
Following files are used to store/maintain the meta-data information:
<List>
<ListItem>
	standard.source.list.values.xml
</ListItem>
<ListItem>
	standard.source.table.fields.xml
</ListItem>
<ListItem>
	standard.source.logical.defs.xml
</ListItem>
<ListItem>
	standard.source.logical.attr.defs.xml
</ListItem>
<ListItem>
	standard.target.table.fields.xml
</ListItem>
<ListItem>
	standard.target.used.domains.xml
</ListItem>
<ListItem>
	standard.target.table.fields.descriptive.names.xml
</ListItem>
<ListItem>
	standard.list.mapping.xml
</ListItem>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
</List>

<Bold>(Textbox) Server</Bold>
Specify source database server name.

<Bold>(Textbox) User</Bold>
Specify database username.

<Bold>(Textbox) Password</Bold>
Specify user's password.

<Bold>(Textbox) Database</Bold>
Specify database name.

<Bold>(Button) Set </Bold>
To set/store the connection details.

<Bold>(Button) Test </Bold>
To test and verify if the connection details are correct.

<Bold>(Button) Export Source List Types</Bold>
To download the List Types available in the source database.
Data is exported to following file:
<List>
<ListItem>
	standard.source.list.values.xml
</ListItem>
</List>

<Bold>(Button) Export Source Tables List</Bold>
To download the List of Tables available in the source database.
Data is exported to following file:
<List>
<ListItem>
	standard.source.table.fields.xml
</ListItem>
</List>

<Bold>(Button) Export Object Def and Link Def</Bold>
To export the Logical Object Definitions of the source database.
Data is exported to following files:
<List>
<ListItem>
	standard.source.logical.defs.xml
</ListItem>
<ListItem>
	standard.source.logical.attr.defs.xml
</ListItem>
</List>

<Bold>(Button) Generate Tables Mapping</Bold>
This is performed when Development  Team is starting to use this utility to develop a new migration solution:
<List>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
</List>

<Bold>(Button) Update List Types Mapping</Bold>
Whenever any changes are made to the following files:
<List>
<ListItem>
	standard.source.list.values.xml
</ListItem>
<ListItem>
	standard.target.used.domains.xml
</ListItem>
</List>

It requires updating the below file:
<List>
<ListItem>
	standard.list.mapping.xml
</ListItem>
</List>

Use this command to update the same.

<Bold>(Button) Update Tables Mapping</Bold>
Whenever any changes are made to the following files:
<List>
<ListItem>
	standard.source.table.fields.xml
</ListItem>
<ListItem>
	standard.target.table.fields.xml
</ListItem>
</List>

It requires updating the below file:
<List>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
</List>

Use this command to update the same.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Database/Custom</Bold>
This Tab is meant for Customers. 
Use this tab to specify the database details of customized (source) application and download meta-data into xml files. 
Following files are used to store/maintain the meta-data information:
<List>
<ListItem>
	custom.source.list.values.xml
</ListItem>
<ListItem>
	custom.source.table.fields.xml
</ListItem>
<ListItem>
	custom.source.logical.defs.xml
</ListItem>
<ListItem>
	custom.source.logical.attr.defs.xml
</ListItem>
<ListItem>
	custom.target.table.fields.xml
</ListItem>
<ListItem>
	custom.target.used.domains.xml
</ListItem>
<ListItem>
	custom.target.table.fields.descriptive.names.xml
</ListItem>
<ListItem>
	custom.list.mapping.xml
</ListItem>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
</List>

<Bold>(Textbox) Server</Bold>
Specify source database server name.

<Bold>(Textbox) User</Bold>
Specify database username.

<Bold>(Textbox) Password</Bold>
Specify user's password.

<Bold>(Textbox) Database</Bold>
Specify database name.

<Bold>(Button) Set </Bold>
To set/store the connection details.

<Bold>(Button) Test </Bold>
To test and verify if the connection details are correct.

<Bold>(Button) Export Source List Types</Bold>
To download the List Types available in the source database.
Data is exported to following file:
<List>
<ListItem>
	custom.source.list.values.xml
</ListItem>
</List>

<Bold>(Button) Export Source Tables List</Bold>
To download the List of Tables available in the source database.
Data is exported to following file:
<List>
<ListItem>
	custom.source.table.fields.xml
</ListItem>
</List>

<Bold>(Button) Export Object Def and Link Def</Bold>
To export the Logical Object Definitions of the source database.
Data is exported to following files:
<List>
<ListItem>
	custom.source.logical.defs.xml
</ListItem>
<ListItem>
	custom.source.logical.attr.defs.xml
</ListItem>
</List>

<Bold>(Button) Generate List Types Mapping</Bold>
To generate the Lists Mapping details for customized application based on Lists Mapping details of standard application.
Data is exported to following file:
<List>
<ListItem>
	custom.list.mapping.xml
</ListItem>
</List>

<Bold>(Button) Generate Tables Mapping</Bold>
To generate the Tables Mapping details for customized application based on Tables Mapping details of standard application.
Data is exported to following file:
<List>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
</List>

<Bold>(Button) Update List Types Mapping</Bold>
Whenever any changes are made to the following files:
<List>
<ListItem>
	standard.list.mapping.xml
</ListItem>
<ListItem>
	custom.source.list.values.xml
</ListItem>
<ListItem>
	custom.target.used.domains.xml
</ListItem>
</List>

It requires updating the below file:
<List>
<ListItem>
	custom.list.mapping.xml
</ListItem>
</List>

Use this command to update the same.

<Bold>(Button) Update Tables Mapping</Bold>
Whenever any changes are made to the following files:
<List>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
<ListItem>
	custom.source.table.fields.xml
</ListItem>
<ListItem>
	custom.target.table.fields.xml
</ListItem>
</List>

It requires updating the below file:
<List>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
</List>

Use this command to update the same.


<Bold>(Button) Save Metadata to Tables</Bold>
Use this command to store the metadata information stored in xml files into the database tables. This command shall be performed after provisional mapping information for tables and fields are specified.

Information from following files is saved to tables:
<List>
<ListItem>
	standard.source.list.values.xml
</ListItem>
<ListItem>
	standard.source.table.fields.xml
</ListItem>
<ListItem>
	standard.list.mapping.xml
</ListItem>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
<ListItem>
	standard.target.table.fields.xml
</ListItem>
<ListItem>
	standard.target.used.domains.xml
</ListItem>
<ListItem>
	standard.target.table.fields.descriptive.names.xml
</ListItem>
<ListItem>
	custom.source.list.values.xml
</ListItem>
<ListItem>
	custom.source.table.fields.xml
</ListItem>
<ListItem>
	custom.list.mapping.xml
</ListItem>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
<ListItem>
	custom.target.table.fields.xml
</ListItem>
<ListItem>
	custom.target.used.domains.xml
</ListItem>
<ListItem>
	custom.target.table.fields.descriptive.names.xml
</ListItem>
</List>


Tables for storing the meta-data:
<List>
<ListItem>
	MIG_SOURCE_LIST
</ListItem>
<ListItem>
	MIG_SOURCE_LIST_VALUES
</ListItem>
<ListItem>
	MIG_SOURCE_TABLE
</ListItem>
<ListItem>
	MIG_SOURCE_TABLE_FIELD
</ListItem>
<ListItem>
	MIG_TARGET_LIST_TYPES
</ListItem>
<ListItem>
	MIG_TARGET_LIST_VALUES
</ListItem>
<ListItem>
	MIG_TARGET_TABLE
</ListItem>
<ListItem>
	MIG_TARGET_TABLE_FIELD
</ListItem>
<ListItem>
	MIG_LIST_TYPES_MAPPING
</ListItem>
<ListItem>
	MIG_LIST_VALUES_MAPPING
</ListItem>
<ListItem>
	MIG_PROV_TABLE_MAPPING
</ListItem>
<ListItem>
	MIG_PROV_TABLE_FIELD_MAPPING
</ListItem>
<ListItem>
	MIG_MAPPING_RULES_META (for storing descriptive names of the fields)
</ListItem>
</List>

Use this command to update the same.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Database/DCA</Bold>
This is used ONLY by PLM Development Team for downloading Table Mapping Scripts of Migration Profile of Standard Application from DCA Application Server.

Use this tab to specify the database details of DCA Application. 
Information is exported into following files:
<List>
<ListItem>
	DcaAplication.xml
</ListItem>
<ListItem>
	DcaLnTable.xml
</ListItem>
<ListItem>
	DcaLnField.xml
</ListItem>
<ListItem>
	DcaLnDomain.xml
</ListItem>
<ListItem>
	DcaLnEnumSetValue.xml
</ListItem>
<ListItem>
	DcaLegacyTable.xml
</ListItem>
<ListItem>
	DcaLegacyField.xml
</ListItem>
<ListItem>
	DcaLibrary.xml
</ListItem>
<ListItem>
	DcaStdFunctions.xml
</ListItem>
<ListItem>
	DcaMigProfile.xml
</ListItem>
<ListItem>
	DcaTableMap.xml
</ListItem>
<ListItem>
	DcaTableMapRule.xml
</ListItem>
<ListItem>
	DcaFieldMapRule.xml
</ListItem>
<ListItem>
	DcaLocalFunctions.xml
</ListItem>
</List>

<Bold>(Textbox) Server</Bold>
Specify source database server name.

<Bold>(Textbox) User</Bold>
Specify database username.

<Bold>(Textbox) Password</Bold>
Specify user's password.

<Bold>(Textbox) Database</Bold>
Specify database name.

<Bold>(Button) Set </Bold>
To set/store the connection details.

<Bold>(Button) Test </Bold>
To test and verify if the connection details are correct.

<Bold>(Button) Export DCA Profile</Bold>
To download the Mapping Scripts of the Migration Profile of Standard Application from DCA Application Server.
Data is exported to the files as listed above.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Components</Bold>
To perform the operations, this utility requires certain SQL Components (tables, stored procedures and functions) to be created in the customer’s database. 
This tab provides a list of all the components that needs to be created in customer’s database. 
If required, customers can also add new components.

The information is maintained in following file:
<List>
<ListItem>
	components.xml
</ListItem>
</List>

<Bold>(Button) New</Bold>
To add a new entry in the DataGrid.

<Bold>(Button) Save</Bold>
To save changes (if any) in the DataGrid. Note that when you save, the value of Order column is re-generated for all the records whose Order column value is not 0.

<Bold>(Button) Undo</Bold>
To revert any changes made to the DataGrid which are not yet saved.

<Bold>(Button) Create</Bold>
To create the components in the customer’s database.

<Bold>(Button) Reset</Bold>
To reset the value of component's status (see "Status" Column).

<Bold>(Button) Delete</Bold>
To delete all the listed components (if already created) from customer's database.

<Bold>(Primary DataGrid) </Bold>
Lists the details of all the SQL Components.
It has following columns:
<List>
<ListItem>
	Ignore – True/False to indicate if the components shall be ignored during creation or not.
</ListItem>
<ListItem>
	Order – SQL Components have dependencies, components shall be created in a specific order. This column indicates the order of creating the components. If the value is 0, then also the component is ignored.
</ListItem>
<ListItem>
	Type – Indicates if the component is a “Table”, “Stored Procedure”, “SQL Function” or “View”.
</ListItem>
<ListItem>
	Name – Name of the component
</ListItem>
<ListItem>
	Description – Short description of the component.
</ListItem>
<ListItem>
	Status – Indicates the component's creation status.
</ListItem>
<ListItem>
	Directory – The sub-directory where the file exists.
</ListItem>
<ListItem>
	File Name – Name of the file containing the definition of the SQL component.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Settings</Bold>
Use this tab to define and view the data migration settings. 

The utility maintains the settings information in following table:
<List>
<ListItem>
	MIG_SETTINGS
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_CREATE_ENTRIES_IN_MIG_SETTINGS_Sp
</ListItem>
</List>

You can change these settings by modifying this stored procedure and re-executing it.

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_SETTINGS table. 
It has following columns:
<List>
<ListItem>
	Name – Name of the setting.
</ListItem>
<ListItem>
	Value – Value for the setting.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_SETTINGS.

<Bold>(Button) Load</Bold>
To view the data from MIG_SETTINGS table.


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard</Bold>
This tab is used by PLM Development Team to maintain the meta-data details of Standard Application.
Customers can use this tab to view these details of Standard Application.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Source List Types</Bold>
Lists the List Types available in the source application.

<Bold>List Types (Primary DataGrid)</Bold>
The name of all the List Types are listed.
It has following columns:
<List>
<ListItem>
	Type Name – Name of the List Type.
</ListItem>
</List>

<Bold>List Values</Bold>
Lists all the List Values available under the selected Type Name.
It has following columns:
<List>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Short Description – Description of the List Value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Source Tables</Bold>
Lists the Tables available in the source application.

<Bold>Tables (Primary DataGrid)</Bold> 
The name of the Tables are listed.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
</List>

<Bold>Table Fields</Bold>
Lists all the fields available under the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Data Type – SQL data type of the given field.
</ListItem>
<ListItem>
	Char Max Length – Max Length of the field (as per SQL Table definition)
</ListItem>
<ListItem>
	Attr Type – Attribute Type of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
<ListItem>
	Udtp Reference – List Type Name of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Source Logical Objects</Bold>
Lists the details of logical definitions of PLM objects of source application.

<Bold>Primary DataGrid</Bold> 
The names of all the logical objects are listed.
(Data exported from OBJECT_DEF and LINK_DEF tables are listed).

It has following columns:
<List>
<ListItem>
	Type – Indicates if it is an Object Type definition of a Link Type Definition.
</ListItem>
<ListItem>
	Table
</ListItem>
<ListItem>
	Object Title
</ListItem>
<ListItem>
	Link Title
</ListItem>
<ListItem>
	Description
</ListItem>
</List>

<Bold>Attributes</Bold>
The names of all the logical attributes for the selected logical object is listed.
(Data exported from table OBJ_DEF_ATTR is listed).

It has following columns:
<List>
<ListItem>
	Object Title
</ListItem>
<ListItem>
	Link Title
</ListItem>
<ListItem>
	Attribute Name
</ListItem>
<ListItem>
	Attribute Type
</ListItem>
<ListItem>
	Legacy Attribute – Table Field
</ListItem>
<ListItem>
	Description
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Target List Types</Bold>
Lists the List Types (Domains of type “Enumerated”) available in the target application.

<Bold>Primary DataGrid</Bold> 
The name of all the domains of type “Enumerated” are listed.
It has following columns:
<List>
<ListItem>
	Domain – Name of the domain.
</ListItem>
</List>

<Bold>Enumeration Values</Bold>
Lists all the Enumeration Values available under the selected domain.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Target Tables</Bold>
Lists the Tables available in the target application.

<Bold>Primary DataGrid </Bold>
The name of the Tables are listed.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
<ListItem>
	Description – Description of the table.
</ListItem>
</List>

<Bold>Table Fields</Bold>
Lists all the fields available under the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the given field.
</ListItem>
<ListItem>
	Db Type – Db Type of the given field
</ListItem>
<ListItem>
	Default Value – Default value of the given field.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/List Types Mapping</Bold>
In general, for every Type Name (List) of source application, a corresponding domain of type “Enumerated” has been created in the target application. However, the numeric values of their list values have been changed in the target application.

This tab is used to define the mapping of Type Name of source application to the corresponding domain of the target application; along with the mapping of their List Values as well. 
A List Type to Domain Mapping is also designated a specific function name. VBScript code is generated based on this information and used in DCA Tool to specify the mapping function for table fields.

<Bold>(Source) Source List Types</Bold> 
List Types available in source application are listed.
It has following columns:
<List>
<ListItem>
	Type Name – Name of the List Type 
</ListItem>
</List>

<Bold>(Target) Target List Types</Bold> 
Domains of type “Enumerated” available in target application are listed.
It has following columns:
<List>
<ListItem>
	Domain – Name of the Domain.
</ListItem>
</List>

<Bold>(Button) Define Mapping</Bold>
To define the mapping of source Type Name to the Target Domain Name.
On click on this button, a Type Name to Domain mapping record is created in the “List Types Mapping” secondary DataGrid.

<Bold>List Types Mapping (Secondary DataGrid)</Bold>
Lists all the list types mapping defined.
It has following columns:
<List>
<ListItem>
	Type Name – Type Name of the source list type.
</ListItem>
<ListItem>
	Domain – Domain name of the target list type.
</ListItem>
<ListItem>
	Script Name – Name of the VBScript file to generate functions.
</ListItem>
<ListItem>
	Function Name – Name of the VBScript function to be generated for the given mapping.
</ListItem>
</List>

<Bold>(Button) Save </Bold>
To save the mapping information into following file:
<List>
<ListItem>
	standard.list.mapping.xml
</ListItem>
</List>

<Bold>(Button) Delete </Bold>
To delete the selected mapping.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/List Values Mapping</Bold>
This tab is used to define the mapping between the List Values of a given Type Name of the source application to the Enumerated Values of the corresponding Domain of the target application. 

<Bold>Primary DataGrid (List Types Mapping)</Bold>
Lists the Types Names to Domains Mapping defined.
It has following columns:
<List>
<ListItem>
	Type Name – Type Name of the source list type.
</ListItem>
<ListItem>
	Domain – Domain name of the target list type.
</ListItem>
<ListItem>
	Script Name – Name of the VBScript to generate function.
</ListItem>
<ListItem>
	Function Name – Name of the VBScript function to be generated for the given mapping.
</ListItem>
</List>

<Bold>(Source) List Values Mapping (Source to Target)</Bold>
Source List Values (along with its corresponding target list value information) are listed.
It has following columns:
<List>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Value Description – Description of the List Value.
</ListItem>
<ListItem>
	Constant – The corresponding enumerated value (for the given list value) in the target application.
</ListItem>
<ListItem>
	Constant Description – Description of the enumeration value.
</ListItem>
</List>

<Bold>Target List Values</Bold>
Lists all the Enumeration Values available under the selected domain.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Bold>(Button) Map</Bold>
To set the corresponding enumerated constant for the given source list value.

<Bold>(Button) Clear</Bold> 
To clear the corresponding enumerated constant value set for the given source list value.

<Bold>(Button) Map (By Sequence) </Bold> 
The Map button is used to map the list values one at a time. In a scenario where the source list values and the target list value have one-to-one correspondence as per there numeric order. In that case, one can use this option to automatically map multiple list values in one go.

<Bold>(Button) Save</Bold> 
To save the mapping information into following file:
<List>
<ListItem>
	standard.list.mapping.xml
</ListItem>
</List>

<Bold>(Button) Generate Enum Mapping Scripts</Bold>  
For all the List Types Mapping specified, code is generated in VBScript. These scripts are used in DCA Application to specify the mapping function for table fields. Use this to generate the VBScripts.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Provisional Mapping – Tables</Bold>

This tab is used to indicate the source table for a given target table.
Note that this is called Provisional Mapping, the reason being that it is mainly an indicative information. The actual fields mappings are defined in the DCA Application (as part of Migration Scripts). 

Certain tables contains field names in their data. As an example, 
<List>
<ListItem>
	Mapping Rules
</ListItem>
<ListItem>
	Mask Rules
</ListItem>
<ListItem>
	Sync Rules
</ListItem>
<ListItem>
	Security Rules
</ListItem>
</List>


Provisional mapping information is used by the utility in generating the data migration logic for these tables.

<Bold> Primary DataGrid (Target Tables)</Bold> 
Lists the Tables of the target application.
It has following columns:
<List>
<ListItem>
	Target Table – Name of the target table.
</ListItem>
<ListItem>
	Target Table Description – Description of the target table.
</ListItem>
<ListItem>
	Migrated – Indicates if the table is supposed to be migrated. (This is only an indicative information).
</ListItem>
<ListItem>
	Completed – Indicates if the Data Migration logic has been developed for this table. (This is only an indicative information).
</ListItem>
<ListItem>
	Source (Base) Table– Name of the primary source table for this target table.
</ListItem>
<ListItem>
	Complexity – Indicates the complexity level of the Data Migration logic for the given target table. (This is only an indicative information).
</ListItem>
<ListItem>
	Comments – Indicates if any specific comments are mentioned for the given target table. (This is only an indicative information).
</ListItem>
</List>

<Bold>Source Tables </Bold> 
Lists the tables available in source application.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
</List>

<Bold>(Text Box) Comments</Bold>
To note down comments (if any) for the selected target table.

<Bold>(Button) Set (Base Table)</Bold>
To mark the primary source table for a given target table.

<Bold>(Button) Clear (Base Table)</Bold>
To clear the corresponding base table name specified for the given target table.

<Bold>(Button) Save</Bold> 
To save the provisional mapping information into following file:
<List>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Provisional Mapping – Table Fields</Bold>

This tab is used to indicate the primary source field name for a given target field.
Note that this is called Provisional Mapping, the reason being that it is mainly an indicative information. The actual fields mappings are defined in the DCA Application (as part of Migration Scripts). 

<Bold>Primary DataGrid (Target Table)</Bold>
Lists the Tables in the target application.
It has following columns:
<List>
<ListItem>
	Target Table – Name of the target table.
</ListItem>
<ListItem>
	Target Table Description – Description of the target table.
</ListItem>
<ListItem>
	Source (Base) Table – Name of the primary source table.
</ListItem>
<ListItem>
	Migrated – Indicates if the table is supposed to be migrated. (This is only an indicative information).
</ListItem>
<ListItem>
	Completed – Indicates if the Data Migration logic has been developed for this table. (This is only an indicative information).
</ListItem>
</List>

<Bold>Target Fields</Bold>
Lists the fields of the selected target table.
It has following columns:
<List>
<ListItem>
	Target Field Name – Name of the target field.
</ListItem>
<ListItem>
	Target Field Description – Description of the target field.
</ListItem>
<ListItem>
	Source (Base) Field Name – Name of the field of source table.
</ListItem>
</List>

<Bold>Base Table Fields </Bold>
Lists the fields of the specified base source table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field of base table.
</ListItem>
</List>

<Bold>(Button) Set (Base Field)</Bold>
To set the base field information of the selected target field.

<Bold>(Button) Clear (Base Field)</Bold>
To clear the base field name set for the selected target field.

<Bold>(Button) Guess (Base Fields) </Bold>
The Set button is used to mark the base field information of a given field one at a time. In a scenario where the source list values and the target list value have similar description, system can automatically guess the base field names of the multiple fields in one go by using this button.

<Bold>(Button) Save</Bold>
To save the provisional mapping information of the target tables into following file:
<List>
<ListItem>
	standard.tables.mapping.xml
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Standard/Migration Profile</Bold>
This tab is used to view the mapping script defined for target tables in the DCA Application.
For more details on this, refer DCA Application.

<Bold>Note that if a Mapping Script has multiple dumps, then this will not show it correctly. It is advised to refer to Mapping Scripts in the DCA Application Server.</Bold>

<Bold>Note that this also does not take into account the migration profile derivation structure. This means, the Standard Migration Profile should not be derived from any other Migration Profile.</Bold>

<Bold>Primary DataGrid (Target Tables)</Bold>
Lists the Tables of the target application.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
<ListItem>
	Description – Description of the table.
</ListItem>
<ListItem>
	Migrated – Indicates if the table is supposed to be migrated. (This is only an indicative information).
</ListItem>
</List>

<Bold>Table Mapping Script</Bold>
Displays the various parts/sections of the mapping script logic of the selected table:
<List>
<ListItem>
	Pre-conditions
</ListItem>
<ListItem>
	Variables/Includes
</ListItem>
<ListItem>
	Source Tables
</ListItem>
<ListItem>
	Body
</ListItem>
</List>

(Note, the Libraries section lists the name of all the VB Script libraries used in the data migration logic of various tables)

<Bold>Fields Mapping Rules</Bold>
Lists the mapping logic of the individual fields of the selected target table.
It has following columns:
<List>
<ListItem>
	Sequence – Sequence number of the field as per the table definition (in target application)
</ListItem>
<ListItem>
	Field – Name of the field of target table.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the field.
</ListItem>
<ListItem>
	Data Type – Data Type of the field.
</ListItem>
<ListItem>
	Rule – Migration logic for the field.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized</Bold>
This tab is used by Customers to view/maintain the meta-data details of their customized application.

Users can also use this to analyze the differences in the meta-data of the
<List>
<ListItem>
	Customized Source Application wrt Standard Source Application. 
</ListItem>
<ListItem>
	Customized Target Application wrt Standard Target Application.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source List Types</Bold>
Lists the List Types available in the customized application.
The data is categorized into following types:
<List>
<ListItem>
	Available
	All the List Types of standard application which are also available in the customized application are listed here. 
</ListItem>
<ListItem>
	New 
	All the List Types that are newly added in the customized application are listed here. 
</ListItem>
<ListItem>
	Missing
	Any List Type of standard application which is missing in the customized application is listed here.
</ListItem>
</List>


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source List Types/Available</Bold>
All the List Types of standard application which are also available in the customized application are listed here

<Bold>Primary DataGrid</Bold> 
The name of all the List Types are listed here, along with details of differences in the list values of customized application as compared to standard application.

It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Type Name – Name of the List Type.
</ListItem>
<ListItem>
	Mismatch – Count of List Values that have mismatch (in terms of Value-ID's) as compared to standard application.
</ListItem>
<ListItem>
	Duplicates – Count of List Values that have same description (ignoring the care-sensitiveness).
</ListItem>
<ListItem>
	Newly Added – Count of List Values that are newly added in customized application.
</ListItem>
<ListItem>
	Missing – Count of List Values that are missing in customized application as compared to standard application.
</ListItem>
</List>

<Bold>Custom List Values</Bold>
Lists all the List Values available under customized application the selected Type Name.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Short Description – Description of the List Value.
</ListItem>
</List>

<Bold>Standard List Values</Bold>
Lists all the List Values available under standard application for the selected Type Name.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Short Description – Description of the List Value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source List Types/Newly Added</Bold>
All the List Types that are newly added in the customized application are listed here.

<Bold>Primary DataGrid</Bold> 
The names of newly added List Types are listed here.
It has following columns:
<List>
<ListItem>
	Type Name – Name of the List Type.
</ListItem>
</List>

<Bold>List Values</Bold>
Lists all the List Values available under selected Type Name.
It has following columns:
<List>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Short Description – Description of the List Value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source List Types/Missing</Bold>
Any List Type of standard application which is missing in the customized application is listed here.

<Bold>Primary DataGrid</Bold> 
The name of the missing List Types are listed here.
It has following columns:
<List>
<ListItem>
	Type Name – Name of the List Type.
</ListItem>
</List>

<Bold>List Values</Bold>
Lists all the List Values available under the selected Type Name.
It has following columns:
<List>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Short Description – Description of the List Value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source Tables</Bold>
Lists the Tables available in the customized application.
The data is categorized into following types:
<List>
<ListItem>
	Available
	All the tables of standard application which are also available in the customized application are listed here. 
</ListItem>
<ListItem>
	New 
	All the Tables that are newly added in the customized application are listed here. 
</ListItem>
<ListItem>
	Missing
	Any table of standard application which is missing in the customized application is listed here.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source Tables/Available</Bold>
All the Tables of standard application which are also available in the customized application are listed here

<Bold>Primary DataGrid</Bold> 
The name of all the Tables are listed here along with details of differences in the field definitions of customized application as compared to standard application.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the Table.
</ListItem>
<ListItem>
	Mismatch – Count of fields whose definition differs as compared to standard application.
</ListItem>
<ListItem>
	Newly Added – Count of fields that are newly added in customized application.
</ListItem>
<ListItem>
	Missing – Count of fields that are missing in customized application as compared to standard application.
</ListItem>
</List>

<Bold>Custom Fields</Bold>
Lists all the fields available under customized application for the selected table.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Data Type – SQL data type of the given field.
</ListItem>
<ListItem>
	Char Max Length – Max Length of the field (as per SQL Table definition)
</ListItem>
<ListItem>
	Attr Type – Attribute Type of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
<ListItem>
	Udtp Reference – List Type Name of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
</List>

<Bold>Standard Fields</Bold>
Lists all the fields available under standard application for the selected table.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Data Type – SQL data type of the given field.
</ListItem>
<ListItem>
	Char Max Length – Max Length of the field (as per SQL Table definition)
</ListItem>
<ListItem>
	Attr Type – Attribute Type of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
<ListItem>
	Udtp Reference – List Type Name of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source Tables/Newly Added</Bold>
All the Tables that are newly added in the customized application are listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the newly added tables are listed here.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
</List>

<Bold>Fields</Bold>
Lists all the fields available under customized application for the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Data Type – SQL data type of the given field.
</ListItem>
<ListItem>
	Char Max Length – Max Length of the field (as per SQL Table definition)
</ListItem>
<ListItem>
	Attr Type – Attribute Type of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
<ListItem>
	Udtp Reference – List Type Name of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source Tables/Missing</Bold>
Any table of standard application which is missing in the customized application is listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the missing tables are listed here.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
</List>

<Bold>Fields</Bold>
Lists all the fields available under customized application the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Data Type – SQL data type of the given field.
</ListItem>
<ListItem>
	Char Max Length – Max Length of the field (as per SQL Table definition)
</ListItem>
<ListItem>
	Attr Type – Attribute Type of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
<ListItem>
	Udtp Reference – List Type Name of the given field (as per PLM Object Definition; based on the field ZZ_CLASS_ATTR.ATTR_TYPE)
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Source Logical Objects</Bold>
Lists the details of logical definitions of PLM objects of source application.

<Bold>Primary DataGrid</Bold> 
The names of all the logical objects are listed.
(Data exported from OBJECT_DEF and LINK_DEF tables are listed).

It has following columns:
<List>
<ListItem>
	Type – Indicates if it is an Object Type definition of a Link Type Definition.
</ListItem>
<ListItem>
	Table
</ListItem>
<ListItem>
	Object Title
</ListItem>
<ListItem>
	Link Title
</ListItem>
<ListItem>
	Description
</ListItem>
</List>

<Bold>Attributes</Bold>
The names of all the logical attributes for the selected logical object is listed.
(Data exported from table OBJ_DEF_ATTR is listed).

It has following columns:
<List>
<ListItem>
	Object Title
</ListItem>
<ListItem>
	Link Title
</ListItem>
<ListItem>
	Attribute Name
</ListItem>
<ListItem>
	Attribute Type
</ListItem>
<ListItem>
	Legacy Attribute – Table Field
</ListItem>
<ListItem>
	Description
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target List Types</Bold>
Lists the List Types (Domains of type “Enumerated”) available in the customized target application.
The data is categorized into following types:
<List>
<ListItem>
	Available
	All the List Types of standard application which are also available in the customized application are listed here. 
</ListItem>
<ListItem>
	New 
	All the List Types that are newly added in the customized application are listed here. 
</ListItem>
<ListItem>
	Missing
	Any List Type of standard application which is missing in the customized application is listed here.
</ListItem>
</List>


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target List Types/Available</Bold>
All the List Types of standard application which are also available in the customized application are listed here

<Bold>Primary DataGrid</Bold> 
The name of all the List Types are listed here along with details of differences in the list values of customized List Type as compared to standard List Type.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Domain – Name of the Domain.
</ListItem>
<ListItem>
	Mismatch – Count of Enumerated Values that have mismatch as compared to standard application.
</ListItem>
<ListItem>
	Duplicates – Count of Enumerated Values that have same description (ignoring the care-sensitiveness).
</ListItem>
<ListItem>
	Newly Added – Count of Enumerated Values that are newly added in customized application.
</ListItem>
<ListItem>
	Missing – Count of Enumerated Values that are missing in customized application as compared to standard application.
</ListItem>
</List>

<Bold>Custom List Values</Bold>
Lists all the Enumeration Values available under the selected Domain.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Bold>Standard List Values</Bold>
Lists all the List Values available under standard application for the selected Domain Name.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target List Types/Newly Added</Bold>
All the List Types that are newly added in the customized application are listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the newly added List Types are listed here.
It has following columns:
<List>
<ListItem>
	Domain – Name of the Domain.
</ListItem>
</List>

<Bold>List Values</Bold>
Lists all the List Values available under customized application the selected Domain Name.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target  List Types/Missing</Bold>
Any List Type of standard application which is missing in the customized application is listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the missing List Types are listed here.
It has following columns:
<List>
<ListItem>
	Domain – Name of the Domain.
</ListItem>
</List>

<Bold>List Values</Bold>
Lists all the List Values available under customized application the selected Domain Name.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target Tables</Bold>
Lists the Tables available in the customized application.
The data is categorized into following types:
<List>
<ListItem>
	Available
	All the tables of standard application which are also available in the customized application are listed here. 
</ListItem>
<ListItem>
	New 
	All the Tables that are newly added in the customized application are listed here. 
</ListItem>
<ListItem>
	Missing
	Any table of standard application which is missing in the customized application is listed here.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target Tables/Available</Bold>
All the Tables of standard application which are also available in the customized application are listed here

<Bold>Primary DataGrid</Bold> 
The name of all the Tables are listed here along with details of differences in the field definitions of customized table as compared to standard table.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the Table.
</ListItem>
<ListItem>
	Description – Description of the Table.
</ListItem>
<ListItem>
	Mismatch – Count of fields whose definition differs as compared to standard application.
</ListItem>
<ListItem>
	Newly Added – Count of fields that are newly added in customized application.
</ListItem>
<ListItem>
	Missing – Count of fields that are missing in customized application as compared to standard application.
</ListItem>
</List>

<Bold>Custom Fields</Bold>
Lists all the fields available under customized application for the selected table.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the given field.
</ListItem>
<ListItem>
	Db Type – Db Type of the given field
</ListItem>
<ListItem>
	Default Value – Default value of the given field.
</ListItem>
</List>

<Bold>Standard Fields</Bold>
Lists all the fields available under standard application for the selected table.
It has following columns:
<List>
<ListItem>
	(Record Status) Column with symbols indicating of differences (if any).
</ListItem>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the given field.
</ListItem>
<ListItem>
	Db Type – Db Type of the given field
</ListItem>
<ListItem>
	Default Value – Default value of the given field.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target Tables/Newly Added</Bold>
All the Tables that are newly added in the customized application are listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the newly added tables are listed here.
It has following columns:
<List>
<ListItem>
	Name – Name of the table.
</ListItem>
<ListItem>
	Description – Description of the table.
</ListItem>
</List>

<Bold>Fields</Bold>
Lists all the fields available under the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the given field.
</ListItem>
<ListItem>
	Db Type – Db Type of the given field
</ListItem>
<ListItem>
	Default Value – Default value of the given field.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Target Tables/Missing</Bold>
Any table of standard application which is missing in the customized application is listed here.

<Bold>Primary DataGrid</Bold> 
The name of all the missing Tables are listed here.
It has following columns:
<List>
<ListItem>
	Name – Name of the table.
</ListItem>
<ListItem>
	Description – Description of the table.
</ListItem>
</List>

<Bold>Fields</Bold>
Lists all the fields available under the selected table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field.
</ListItem>
<ListItem>
	Description – Description of the field.
</ListItem>
<ListItem>
	Domain – Domain of the given field.
</ListItem>
<ListItem>
	Db Type – Db Type of the given field
</ListItem>
<ListItem>
	Default Value – Default value of the given field.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/List Types Mapping</Bold>
In general, for every Type Name (List) of source application, a corresponding domain of type “Enumerated” has been created in the target application. 
The numeric values of the their list values have been changed in the target application.

This tab is used to define the mapping of Type Name of source application to the corresponding domain of the target application; along with the mapping of their List Values as well. 
A List Type to Domain Mapping is also designated a specific function name. VBScript code is generated based on this information and used in DCA Tool to specify the mapping function for table fields.

<Bold>(Source) Type Name</Bold> 
The List Types available in source application are listed.
It has following columns:
<List>
<ListItem>
	Type Name – Name of the List Type 
</ListItem>
</List>

<Bold>(Target) Enumerated Domain </Bold>
The Domains of type “Enumerated” available in target application are listed.
It has following columns:
<List>
<ListItem>
	Domain – Name of the Domain.
</ListItem>
</List>

<Bold>(Button) Define Mapping</Bold>
To define the mapping of source Type Name and the Target Domain Name.
On click on thus button, a Type Name to Domain mapping record is created in the “Type Names Mapping” secondary DataGrid.

<Bold>Type Names Mapping (Secondary DataGrid)</Bold>
Lists all the type name mapping defined.
It has following columns:
<List>
<ListItem>
	Type Name – Type Name of the source list type.
</ListItem>
<ListItem>
	Domain – Domain name of the target list type.
</ListItem>
<ListItem>
	Script Name – Name of the VBScript to generate function.
</ListItem>
<ListItem>
	Function Name – Name of the VBScript function to be generated for the given mapping.
</ListItem>
</List>

<Bold>(Button) Save</Bold> 
To save the mapping information into following file:
<List>
<ListItem>
	custom.list.mapping.xml
</ListItem>
</List>

<Bold>(Button) Delete</Bold> 
To delete the selected mapping.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/List Values Mapping</Bold>
This tab is used to define the mapping between the List Values of a given Type Name of the source application to the Enumerated Values of the corresponding Domain of the target application. 

<Bold>Primary DataGrid (Type Names Mapping)</Bold>
Lists the Types Names to Domain Mapping defined.
It has following columns:
<List>
<ListItem>
	Type Name – Type Name of the source list type.
</ListItem>
<ListItem>
	Domain – Domain name of the target list type.
</ListItem>
<ListItem>
	Script Name – Name of the VBScript to generate function.
</ListItem>
<ListItem>
	Function Name – Name of the VBScript function to be generated for the given mapping.
</ListItem>
</List>

<Bold>Source to Target List Values Mapping</Bold> 
Source List Values (along with its corresponding target list value information) are listed.
It has following columns:
<List>
<ListItem>
	Value-ID – Numeric ID of the List Value.
</ListItem>
<ListItem>
	Value Description – Description of the List Value.
</ListItem>
<ListItem>
	Constant – The corresponding enumerated value (for the given list value) in the target application.
</ListItem>
<ListItem>
	Constant Description – Description of the enumeration value.
</ListItem>
</List>

<Bold>Target List Values</Bold>
Lists all the Enumeration Values available under the selected Domain.
It has following columns:
<List>
<ListItem>
	Constant – Numeric ID of the enumeration value.
</ListItem>
<ListItem>
	Constant Name – Technical name of the enumeration value.
</ListItem>
<ListItem>
	Description – Description of the enumeration value.
</ListItem>
</List>

<Bold>(Button) Map</Bold>
To set the corresponding enumerated constant for the given list value.

<Bold>(Button) Clear</Bold>
To clear the corresponding enumerated constant value set for the given list value.

<Bold>(Button) Map (By Sequence)</Bold> 
The Map button is used to map the list values one at a time. In a scenario where the source list values and the target list value have one-to-one correspondence as per there numeric order. In that case, one can use this option to automatically map multiple list values in one go.

<Bold>(Button) Re-Adjust</Bold> 
On source side, the Value-ID of customized application can differ with respect to the Value-ID of standard application; however the description of list value could be same. In that case, the Value-ID needs to be correctly mapped to the target enumeration value.
This action can re-adjust the mapping based on the description of list values of standard list value and customized list value.

<Bold>(Button) Save</Bold> 
To save the mapping information into following file:
<List>
<ListItem>
	custom.list.mapping.xml
</ListItem>
</List>

<Bold>(Button) Generate Enum Mapping Scripts</Bold> 
For all the List Types Mapping specified, code is generated in VBScript. These scripts are used in DCA Tool to specify the mapping function for table fields

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Provisional Mapping – Tables</Bold>

This tab is used to indicate the source table for a given target table.
Note that this is called Provisional Mapping, the reason being that it is mainly an indicative information. The actual fields mappings are defined in the DCA Tool (as part of Migration Scripts). 
Certain tables contains field names in their data. As an example, 
<List>
<ListItem>
	Mapping Rules
</ListItem>
<ListItem>
	Mask Rules
</ListItem>
<ListItem>
	Sync Rules
</ListItem>
<ListItem>
	Security Rules
</ListItem>
</List>

Provisional mapping information is used by the utility in the data migration logic for these tables.

<Bold>Primary DataGrid (Target Tables)</Bold>
Lists the Tables of the target application.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
<ListItem>
	Description – Description of the table.
</ListItem>
<ListItem>
	Migrated – Indicates if the table is supposed to be migrated. (This is only an indicative information).
</ListItem>
<ListItem>
	Completed – Indicates if the Data Migration logic is completed. (This is only an indicative information).
</ListItem>
<ListItem>
	Source (Base) Table– Name of the primary source table for this target table.
</ListItem>
<ListItem>
	Complexity – Indicates the complexity level of the Data Migration logic for the given target table. (This is only an indicative information).
</ListItem>
<ListItem>
	Comments – Indicates if any specific comments are mentioned for the given target table. (This is only an indicative information).
</ListItem>
</List>

<Bold>Source Tables</Bold> 
Lists the tables available in source application.
It has following columns:
<List>
<ListItem>
	Name – Name of the Table.
</ListItem>
</List>

<Bold>Comments</Bold> 
To note down comments (if any) needed for the selected target table.

<Bold>(Button) Set (Base Table)</Bold> 
To mark the primary source table for a given target table.

<Bold>(Button) Clear (Base Table)</Bold> 
To clear the corresponding enumerated base table name specified for the given target table.

<Bold>(Button) Save</Bold> 
To save the provisional mapping information of the target tables into following file:
<List>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Customized/Provisional Mapping – Table Fields</Bold>

This tab is used to indicate the primary source field name for a given field of the target field.
Note that this is called Provisional Mapping, the reason being that it is mainly an indicative information. The actual fields mappings are defined in the DCA Application (as part of Migration Scripts). 

<Bold>Primary DataGrid (Target Table)</Bold>
Lists the Tables in the target application.
It has following columns:
<List>
<ListItem>
	Target Table –Name of the target table.
</ListItem>
<ListItem>
	Target Table Description – Description of the target table.
</ListItem>
<ListItem>
	Source (Base) Table – Name of the primary source table.
</ListItem>
<ListItem>
	Migrated – Indicates if the table is supposed to be migrated. (This is only an indicative information).
</ListItem>
<ListItem>
	Completed – Indicates if the Data Migration logic has been developed for this table. (This is only an indicative information).
</ListItem>
</List>

<Bold>Target Fields</Bold>
Lists the fields of the selected target table.
It has following columns:
<List>
<ListItem>
	Target Field Name – Name of the target field.
</ListItem>
<ListItem>
	Target Field Description – Description of the field of target table.
</ListItem>
<ListItem>
	Source (Base) Field Name – Name of the field of source table.
</ListItem>
</List>

<Bold>Base Table Fields</Bold> 
Lists the fields of the specified base source table.
It has following columns:
<List>
<ListItem>
	Name – Name of the field of base table.
</ListItem>
</List>

<Bold>(Button) Set (Base Field)</Bold>
To set the base field information of the selected target field.

<Bold>(Button) Clear</Bold>
To clear the base field name set for the selected target field.

<Bold>(Button) Guess (Base Fields)</Bold> 
The Set button is used to mark the base field information of a given field one at a time. In a scenario where the source list values and the target list value have similar description, system can automatically guess the base field names of the multiple fields in one go by using this action.

<Bold>(Button) Save</Bold> 
To save the provisional mapping information of the target tables into following file:
<List>
<ListItem>
	custom.tables.mapping.xml
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Text Fields</Bold>

Text fields are handled and managed in a different way in the LN Tools as compared to the source application. So, the migration of text data requires a different approach. 
Via this utility, text data is exported from source database into txt files and xml files. Using special session in LN “Data Migration: Pre/Post Migration Functions” (pdadm8161m00), the text data is imported into the target application. 

In this tab, system lists the fields of standard target application for which there is source data. 
If customers have additional text fields (in target application) for which there is source data which also needs to be migrated, then customers need to define corresponding entries for the same.

Details of text fields and corresponding  queries to pull its data is maintained in following table:
<List>
<ListItem>
	MIG_TEXT_FIELDS_QUERIES
</ListItem>
</List>

Following stored procedure is used to create entries in this table:
<List>
<ListItem>
	MIG_CREATE_ENTRIES_IN_TEXT_FIELDS_QUERIES_Sp
</ListItem>
</List>

<Bold>Primary DataGrid (Text Fields)</Bold>
Lists the text fields of target application, whose data is being migrated. 
It has following columns:
<List>
<ListItem>
	Target Table – Name of the target table.
</ListItem>
<ListItem>
	Target Field – Name of the target field.
</ListItem>
</List>

The records in this DataGrid are listed based on the “text.fields.queries.xml” file.

<Bold>SQL Query</Bold>
To view the SQL Query of the selected record.

<Bold>(Button) Generate Text Fields Queries List</Bold>
To populate the table MIG_TEXT_FIELDS_QUERIES based on stored procedure MIG_CREATE_ENTRIES_IN_TEXT_FIELDS_QUERIES_Sp.

<Bold>(Button) Export Text Fields Queries (As XML)</Bold>
To export the list of queries of text fields (from table MIG_TEXT_FIELDS_QUERIES) to following file:
<List>
<ListItem>
	text.fields.queries.xml
</ListItem>
</List>

<Bold>To Export/Import Text Data</Bold>
<List>
<ListItem>
	Use the button “Export (Text Data)” under “Export (XML/Images)” Tab for exporting the text data of these fields into xml and txt files.
	Text data is exported for the fields listed under the “text.fields.queries.xml” file.
</ListItem>
<ListItem>
	Use the command “Import (Text Data)” (in LN Session “PLM Data Migration: Pre/Post Operations” – pdadm8161m00) for importing the text data from these files.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Meta-data</Bold>
Use this command to store the metadata information stored in xml files into the database tables. This command is performed after provisional mapping information for tables and fields have been specified.

<Bold>(Button) Save Meta-data to Tables</Bold>
Use this command to store the meta-data into tables. This command is also available in the "Database/Custom" Tab. For more details refer to the details of this command.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Vaults</Bold>
Use this tab to generate the list of vaults details.

The utility maintains the vaults information in following table:
<List>
<ListItem>
	MIG_SITE
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_SITE_Sp
</ListItem>
</List>

<Bold>Primary DataGrid (Users)</Bold>
Lists the vaults from MIG_SITE table. 
It has following columns:
<List>
<ListItem>
	Vault – Name of the vault
</ListItem>
<ListItem>
	Description – Vault description
</ListItem>
<ListItem>
	Default – Indicates if this is a preferred vault
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_SITE based on standard table SITE.
For every entry in SITE table, a corresponding entry is created in MIG_SITE table.

<Bold>(Button) Load</Bold>
To view the data from MIG_SITE table.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I</Bold> 
Certain tables contains data which requires to be given new values before migrating. Under this group, all such cases have been listed. The data migration user needs to verify this data and specify new values wherever needed.
<List>
<ListItem>
	Users
</ListItem>
<ListItem>
	Document Types
</ListItem>
<ListItem>
	Folder Types
</ListItem>
<ListItem>
	Route System Command Text
</ListItem>
<ListItem>
	EO Route System Command Text
</ListItem>
<ListItem>
	Route Step Data
</ListItem>
<ListItem>
	EO Route Step Data
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/Users</Bold>
If the username in source application does not correspond to the employee code of target application, it requires changing the same.
Use this tab to view the list of users and specify the target employee code.

It may be noted that in the source application, one can create users with user-id upto 20 characters; whereas in target application, the length is restricted to 9 characters.

The utility maintains the usernames mapping information in following table:
<List>
<ListItem>
	MIG_USERS
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_USERS_Sp
</ListItem>
</List>

<Bold>Primary DataGrid (Users)</Bold>
Lists the data from MIG_USERS table. 
It has following columns:
<List>
<ListItem>
	User-ID – User-ID in the source application.
</ListItem>
<ListItem>
	Full name– Full name of the user.
</ListItem>
<ListItem>
	Employee-ID – New User-ID of the user as per target application.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_USERS based on standard table USERS.
For every entry in USERS table, a corresponding entry is created in MIG_USERS table.

<Bold>(Button) Load</Bold>
To view the data from MIG_USERS table.

<Bold>(Button) Save</Bold>
To save the changes (new user-id’s, if any specified) to the MIG_USERS table.

<Bold>(Button) Auto-Generate</Bold>
This is only to generally temporary id's (for sample testing).

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/Document Types</Bold>

Length of Document Types cannot be more than 30 characters in "pd". Use this to specify new values for such cases.

The utility maintains the document types information in following table:
<List>
<ListItem>
	MIG_DOC_TYPE
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_DOC_TYPE_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_DOC_TYPE table. 
It has following columns:
<List>
<ListItem>
	Value-ID – User-ID in the source application.
</ListItem>
<ListItem>
	Description – Description of the value.
</ListItem>
<ListItem>
	Target Document Type – Value for the target application
</ListItem>
<ListItem>
	Is Master Data – Indicates if the source document type is a standard master data and a corresponding value for it is shipped in target as master data.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_DOC_TYPE based on document types available in source application.
For every document type in source (based on ZZ_UDCDTYPE.TYPE_NAME = "DOC_TYPE"), a corresponding entry is created in table MIG_DOC_TYPE table.

<Bold>(Button) Load</Bold>
To view the data from MIG_DOC_TYPE table.

<Bold>(Button) Save</Bold>
To save the changes (if any) to the MIG_DOC_TYPE table.

<Bold>(Button) Auto-Generate</Bold>
This is only to generally temporary id's (for sample testing).

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/Folder Types</Bold>

Length of Folder Types can not be more than 30 characters in "pd". Use this to specify new values for such cases.

The utility maintains the folder types information in following table:
<List>
<ListItem>
	MIG_FOLDER_TYPE
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_FOLDER_TYPE_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_FOLDER_TYPE table. 
It has following columns:
<List>
<ListItem>
	Value-ID – User-ID in the source application.
</ListItem>
<ListItem>
	Description – Description of the value.
</ListItem>
<ListItem>
	Target Folder Type – Value for the target application
</ListItem>
<ListItem>
	Is Master Data – Indicates if the source folder type is a standard master data and corresponding value for it is shipped in target as master data.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_FOLDER_TYPE based on folder types available in source application.
For every document type in source (based on ZZ_UDCDTYPE.TYPE_NAME = "FOLDER_TYPE"), a corresponding entry is created in table MIG_FOLDER_TYPE table.

<Bold>(Button) Load</Bold>
To view the data from MIG_FOLDER_TYPE table.

<Bold>(Button) Save</Bold>
To save the changes (if any) to the MIG_FOLDER_TYPE table.

<Bold>(Button) Auto-Generate</Bold>
This is only to generally temporary id's (for sample testing).

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/Route System Command Text</Bold>
In the source application, the System Command step takes executables as input. Whereas in target application, these are dll methods. Use this tab to specify the corresponding target dll method names.

The utility maintains the Workflow Template's system command information in following table:
<List>
<ListItem>
	MIG_CORRECT_RT_SYS_CMD
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_CORRECT_RT_SYS_CMD_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_CORRECT_RT_SYS_CMD table. 
It has following columns:
<List>
<ListItem>
	Workflow – Workflow Template ID.
</ListItem>
<ListItem>
	Name – Workflow Template description.
</ListItem>
<ListItem>
	Command – System command (executable as in source application).
</ListItem>
<ListItem>
	New Command – New command name (as per target application).
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_CORRECT_RT_SYS_CMD based on Workflow Templates available in source application.

<Bold>(Button) Load</Bold>
To view the data from MIG_CORRECT_RT_SYS_CMD table.

<Bold>(Button) Save</Bold>
To save the changes to the MIG_CORRECT_RT_SYS_CMD table.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/EO Route System Command Text</Bold>
In the source application, the System Command step takes executables as input. Whereas in target application, these are dll methods. Use this tab to specify the corresponding target dll method names.

The utility maintains the system command information for Business Process steps in following table:
<List>
<ListItem>
	MIG_CORRECT_EO_RT_SYS_CMD
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_CORRECT_EO_RT_SYS_CMD_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_CORRECT_EO_RT_SYS_CMD table. 
It has following columns:
<List>
<ListItem>
	Workflow – Workflow Template ID
</ListItem>
<ListItem>
	Name – Workflow Template description.
</ListItem>
<ListItem>
	Command – System command (executable as in source application).
</ListItem>
<ListItem>
	New Command – New command name (as per target application).
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_CORRECT_EO_RT_SYS_CMD based on Business Process System Command Steps available in source application.

<Bold>(Button) Load</Bold>
To view the data from MIG_CORRECT_EO_RT_SYS_CMD table.

<Bold>(Button) Save</Bold>
To save the changes to the MIG_CORRECT_RT_SYS_CMD table.
<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/Route Step Data</Bold>
Source application allowed case sensitive step-id's. This can result into duplication in target. Use this tab to specify the unique step id's for the target application for such cases.

The utility maintains the Workflow Steps information in following table:
<List>
<ListItem>
	MIG_CORRECT_ROUTE_STEP
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_CORRECT_ROUTE_STEP_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_CORRECT_ROUTE_STEP table. 
It has following columns:
<List>
<ListItem>
	Workflow – Workflow Template ID.
</ListItem>
<ListItem>
	Step/Task – Old Step-ID
</ListItem>
<ListItem>
	New Step/Task – New Step-ID
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_CORRECT_ROUTE_STEP based on Workflow Templates available in source application.

<Bold>(Button) Load</Bold>
To view the data from MIG_CORRECT_ROUTE_STEP table.

<Bold>(Button) Save</Bold>
To save the changes to the MIG_CORRECT_ROUTE_STEP table.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections I/EO Route Step Data</Bold>
Source application allowed case sensitive step-id's. This can result into duplication in target. Use this tab to specify the unique step id's for the target application for such cases.

The utility maintains the Business Process Steps information in following table:
<List>
<ListItem>
	MIG_CORRECT_EO_ROUTE_STEP
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_CORRECT_EO_ROUTE_STEP_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_CORRECT_EO_ROUTE_STEP table. 
It has following columns:
<List>
<ListItem>
	Workflow – Workflow Template ID.
</ListItem>
<ListItem>
	Step/Task – Old Step-ID
</ListItem>
<ListItem>
	New Step/Task – New Step-ID
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_CORRECT_EO_ROUTE_STEP based on Business Processes available in source application.

<Bold>(Button) Load</Bold>
To view the data from MIG_CORRECT_EO_ROUTE_STEP table.

<Bold>(Button) Save</Bold>
To save the changes to the MIG_CORRECT_EO_ROUTE_STEP table.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections II</Bold> 
As explained under Provisional Mapping section, certain tables have data which contains field name in it. These tables are complicated to migrate, and needs verification and correction (if required) by data migration user. Following tables have data that contains field names in it:
<List>
<ListItem>
	Mapping Rules
</ListItem>
<ListItem>
	Mask Rules
</ListItem>
<ListItem>
	Sync Rules
</ListItem>
<ListItem>
	Security Rules
</ListItem>
</List>

Under this group, all such cases have been listed. The migration user needs to verify this data and make the corrections (if needed).
Once the verification/correction is done, user can proceed to next step of exporting this data.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections II/Mapping Rules</Bold>
Mapping Rules contain field names in it, which needs to be corrected to match the target field name. Theis utility uses the data specified under “Provisional Mapping”, however there can be cases where system may not be able to correctly evaluate the target field name. 
Use this tab to view such generated data and verify and correct the same if needed.

The utility maintains the generated mapping rules information in following table:
<List>
<ListItem>
	MIG_MAPPING_RULES 
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_GENERATE_MAPPING_RULES_Sp
</ListItem>
</List>

<Bold>Primary DataGrid</Bold>
Lists the data from MIG_MAPPING_RULES table. 
It has following columns:
<List>
<ListItem>
	Template – Mapping Template.
</ListItem>
<ListItem>
	Source - PLM Object – Name of PLM Object in the Source Application.
</ListItem>
<ListItem>
	Source - PLM Object Label – Label of PLM Object in the Source Application.
</ListItem>
<ListItem>
	Source - PLM Attribute – Name of PLM Object Attribute in the Source Application.
</ListItem>
<ListItem>
	Source - PLM Field Name – Names of PLM Field in the Source Application.
</ListItem>
<ListItem>
	Source - PLM Attribute Label – Label of PLM Field in the Source Application.
</ListItem>
<ListItem>
	Target - PLM Object – Name of PLM Object as per Target Application.
</ListItem>
<ListItem>
	Target - PLM Object Label – Label of PLM Object as per Target Application.
</ListItem>
<ListItem>
	Target - PLM Attribute – Name of PLM Object Attribute as per Target Application.
</ListItem>
<ListItem>
	Target - PLM Attribute Label – Label of PLM Object Attribute as per Target Application.
</ListItem>
<ListItem>
	Target - PLM Attribute Descriptive Name – Descriptive Name of PLM Object Attribute as per Target Application.
</ListItem>
<ListItem>
	Direction – Mapping Rule Direction
</ListItem>
<ListItem>
	CAD Object – Name of CAD Object.
</ListItem>
<ListItem>
	CAD Object Label – Label of CAD Object.
</ListItem>
<ListItem>
	CAD Attribute – Name of CAD Object Attribute.
</ListItem>
<ListItem>
	CAD Attribute Label – Label of CAD Object Attribute.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_MAPPING_RULES based on standard table MAPPING_RULES.
For every entry in MIG_MAPPING_RULES table, a corresponding entry is created in table MIG_MAPPING_RULES table.

Note
<List>
<ListItem>
	Provisional mapping information is used in guessing the target table/field name; user can further make the corrections required (if any).
</ListItem>
<ListItem>
	In the target application, the value of field “PLM Attribute” (pdcad100.pfld) is expected to be descriptive name of the target field. In this dialog, one only needs to specify the field name as per target application. The Import operation on target side will take care of using the descriptive name based on the data from table “PLM Metadata” (pdcad201). 
</ListItem>
</List>


<Bold>(Button) Load</Bold>
To view the data from MIG_MAPPING_RULES table.

<Bold>(Button) Commit</Bold>
To save the changes (new values) to the MIG_MAPPING_RULES table.


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections II/Masks</Bold>

Masks Management has undergone considerable data-model change in target application. Data has been split into multiple tables/columns.
Masks definitions contains table field name, which needs to be corrected to the target field name. Also, Mask Rules too contains field names in the mask conditions.
The utility uses the data specified under “Provisional Mapping”, however there can be cases where system could not correctly evaluate the target field name. 

To manage this complexity, the utility has provision to pre-generate the data pertaining to Mask Management as per the target application. Data Migration user can verify the generated data and make the required corrections (wherever needed).

Use this tab to view the generated data; verify and the correct the same if needed.

The utility maintains the generated information in following tables:
<List>
<ListItem>
	MIG_MASKS
</ListItem>
<ListItem>
	MIG_MASKS_SEGMENTS
</ListItem>
<ListItem>
	MIG_MASK_CONDITIONS
</ListItem>
<ListItem>
	MIG_MASKS_SEQ_CACHE
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_MASKS_Sp
</ListItem>
</List>

<Bold>Masks as in Source Application (Primary DataGrid)</Bold>
Lists the masks under the source application (ZZ_MASK table), which needs to be migrated. 
It has following columns:
<List>
<ListItem>
	Mask ID
</ListItem>
<ListItem>
	Class Name
</ListItem>
<ListItem>
	Key Name
</ListItem>
<ListItem>
	Default Sign
</ListItem>
<ListItem>
	Primary Sign
</ListItem>
<ListItem>
	Pattern
</ListItem>
<ListItem>
	Key Length
</ListItem>
<ListItem>
	Minimum Value
</ListItem>
<ListItem>
	Maximum Value
</ListItem>
<ListItem>
	Current Value
</ListItem>
<ListItem>
	Ref Mask ID
</ListItem>
<ListItem>
	Ready Flag
</ListItem>
<ListItem>
	User Max Mask
</ListItem>
</List>

<Bold>(Text Box) DB Query (Condition)</Bold>
Represents the Mask Rules (if any) in the source application for the selected mask.
The data from “Mask Rules” table (MASK_RULES.DB_QUERY) is shown.

<Bold>Masks as per Target Application Format</Bold>
Display the Masks information as per target application (for the selected Mask of source application). 
It contains following details:
<List>
<ListItem>
	Mask
</ListItem>
<ListItem>
	Segments
</ListItem>
<ListItem>
	Conditions
</ListItem>
<ListItem>
	PLM Projects
</ListItem>
<ListItem>
	Next Keys
</ListItem>
</List>

<Bold>Mask (Satellite DataGrid)</Bold>
Display the Masks information as per target application for the selected Mask of source application. 
It has following columns:
<List>
<ListItem>
	Ignore – Mark as True, if this mask needs to be skipped during migration.
</ListItem>
<ListItem>
	Mask
</ListItem>
<ListItem>
	Table
</ListItem>
<ListItem>
	Field
</ListItem>
<ListItem>
	Length
</ListItem>
<ListItem>
	Order Number
</ListItem>
<ListItem>
	Preferred
</ListItem>
<ListItem>
	Zero Padding
</ListItem>
<ListItem>
	Initial Value
</ListItem>
<ListItem>
	Alternate Mask
</ListItem>
</List>

<Bold>Segments (Satellite DataGrid)</Bold>
Displays the equivalent segments as per target application for the selected mask. 
It has following columns:
<List>
<ListItem>
	Segment Number
</ListItem>
<ListItem>
	Segment Type
</ListItem>
<ListItem>
	Field Name
</ListItem>
<ListItem>
	Segment Value 
</ListItem>
<ListItem>
	Pattern
</ListItem>
<ListItem>
	Increment Rule
</ListItem>
<ListItem>
	Minimum Value
</ListItem>
<ListItem>
	Maximum Value
</ListItem>
</List>

Note
<List>
<ListItem>
	User can modify the mask segments. 
</ListItem>
<ListItem>
	User can also add/delete mask segments.
</ListItem>
</List>

<Bold>Conditions (Satellite DataGrid)</Bold>
Display the equivalent mask conditions as per target application for the selected mask. 
It has following columns:
<List>
<ListItem>
	Condition Number
</ListItem>
<ListItem>
	And/Or
</ListItem>
<ListItem>
	Opening Brace
</ListItem>
<ListItem>
	Key name
</ListItem>
<ListItem>
	Operator
</ListItem>
<ListItem>
	Value 
</ListItem>
<ListItem>
	Closing Brace
</ListItem>
</List>

Note
<List>
<ListItem>
	User can modify the mask conditions.
</ListItem>
<ListItem>
	User can also add/delete mask conditions.
</ListItem>
</List>

<Bold>PLM Projects (Satellite DataGrid)</Bold>
Display the project(s) for which the selected mask is applicable. The information of this tab is for information only, no provision is given in this tab for adding/deleting the data. 
It has following columns:
<List>
<ListItem>
	Project
</ListItem>
<ListItem>
	Description 
</ListItem>
</List>

<Bold>Next Keys (Satellite DataGrid)</Bold>
Displays the equivalent next sequence information as per target application for the selected mask. 
It has following columns:
<List>
<ListItem>
	Prefix
</ListItem>
<ListItem>
	Next Sequence
</ListItem>
<ListItem>
	Is Full
</ListItem>
<ListItem>
	Next Key
</ListItem>
</List>

Note
<List>
<ListItem>
	User can modify the next sequence data.
</ListItem>
<ListItem>
	User can also add/delete next key records.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
Based on the data of standard tables ZZ_MASK and MASK_RULES, system generates the data into following interim tables.
<List>
<ListItem>
	MIG_MASKS
</ListItem>
<ListItem>
	MIG_MASKS_SEGMENTS
</ListItem>
<ListItem>
	MIG_MASK_CONDITIONS
</ListItem>
<ListItem>
	MIG_MASKS_SEQ_CACHE
</ListItem>
</List>

Note
<List>
<ListItem>
	Provisional mapping information is used in guessing the target table/field name; user can further make the corrections required (if any).
</ListItem>
<ListItem>
	Masks Conditions has condition values, which needs verification/correction by user.
</ListItem>
</List>

<Bold>(Button) Load</Bold>
To view the data from interim tables for migrating masks.

<Bold>(Button) Commit</Bold>
To save the changes into the interim tables for migrating masks.


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections II/Sync Rules</Bold>

Sync Rules contain field names in it, which needs to be corrected to the target field name. The utility uses the data specified under “Provisional Mapping”, however there can be cases where system could not correctly evaluate the target field name. Use this tab to view and correct (wherever required). 
Also the mask condition values too may need corrections by data migration user to match as per target application.

The source application uses separate records to indicate if two sync rules conditions are joined with And/Or condition. In target application, instead of maintaining separate records, and/or condition indicator is made part of the sync rule conditions itself.

Use this tab 
<List>
<ListItem>
	To view the sync rules of  source application 
</ListItem>
<ListItem>
	To view the generated data as per target application; and verify and correct the same if needed.
</ListItem>
</List>

The utility maintains the generated synchronization rules information in following table:
<List>
<ListItem>
	MIG_SYNC_RULES
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_SYNC_RULES_Sp
</ListItem>
</List>

<Bold>Rules as in Source Application</Bold>
Lists the data from SYNC_RULES table. 
It has following columns:
<List>
<ListItem>
	ZZ_ID
</ListItem>
<ListItem>
	Site
</ListItem>
<ListItem>
	Condition Number
</ListItem>
<ListItem>
	Condition Relation
</ListItem>
<ListItem>
	Object
</ListItem>
<ListItem>
	Attribute
</ListItem>
<ListItem>
	Operator
</ListItem>
<ListItem>
	Value
</ListItem>
</List>

<Bold>Rules as per Target Application</Bold>
Lists the data from MIG_SYNC_RULES table. 
It has following columns:
<List>
<ListItem>
	ZZ_ID
</ListItem>
<ListItem>
	Vault
</ListItem>
<ListItem>
	Condition Number
</ListItem>
<ListItem>
	And/Or
</ListItem>
<ListItem>
	Opening Brace
</ListItem>
<ListItem>
	Key Name
</ListItem>
<ListItem>
	Operator
</ListItem>
<ListItem>
	Value
</ListItem>
<ListItem>
	Closing Brace
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
The data is generated in table MIG_SYNC_RULES based on standard table SYNC_RULES.
The data us generated as per the format needed in target application; user will see less number of records in the generated table as compared to the standard table.

Note
<List>
<ListItem>
	Provisional mapping information is used in guessing the target table/field name; user can further make the corrections required (if any).
</ListItem>
<ListItem>
	The condition value too needs correction (if required) as per target application.
</ListItem>
<ListItem>
	User can also add/delete the generated rules.
</ListItem>
</List>

<Bold>(Button) Load</Bold>
To view the data from SYNC_RULES and MIG_SYNC_RULES table.

<Bold>(Button) Commit</Bold>
To save the changes to the MIG_ SYNC_RULES table.


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Corrections II/Security Rules - Conditions</Bold>

Security Rules are similar to Mask Conditions; these too contains field names in it, which needs to be corrected to the target field name. The utility uses the data specified under “Provisional Mapping”, however there can be cases where system could not correctly evaluate the target field name. 

The condition value too needs correction (if required) as per target application.

Use this tab 
<List>
<ListItem>
	To view the security rules of  source application 
</ListItem>
<ListItem>
	To view the generated data as per target application; and verify and correct the same if needed.
</ListItem>
</List>

The utility maintains the generated synchronization rules information in following table:
<List>
<ListItem>
	MIG_SEC_RULES
</ListItem>
<ListItem>
	MIG_SEC_RULES_CONDITIONS
</ListItem>
</List>

Following stored procedure is used to create entries in this table
<List>
<ListItem>
	MIG_SEC_RULES
</ListItem>
<ListItem>
	MIG_SEC_RULES_CONDITIONS_Sp
</ListItem>
</List>

<Bold>Rules as in Source Application</Bold>
Lists the data from SEC_RULES table. 
It has following columns:
<List>
<ListItem>
	Rule ID
</ListItem>
<ListItem>
	Description
</ListItem>
<ListItem>
	Object ID
</ListItem>
<ListItem>
	Link ID
</ListItem>
<ListItem>
	Target Table
</ListItem>
</List>

<Bold>Rules as per Target Application</Bold>
Display the equivalent security rules conditions as per target application for the selected security rule. 
Lists the data from MIG_SEC_RULES_CONDITIONS table. 
It has following columns:
<List>
<ListItem>
	Condition Number
</ListItem>
<ListItem>
	And/Or
</ListItem>
<ListItem>
	Opening Brace
</ListItem>
<ListItem>
	Key Name
</ListItem>
<ListItem>
	Operator
</ListItem>
<ListItem>
	Value
</ListItem>
<ListItem>
	Closing Brace
</ListItem>
</List>

Note
<List>
<ListItem>
	User can modify the security rules conditions.
</ListItem>
<ListItem>
	User can also add/delete security rules conditions.
</ListItem>
</List>

<Bold>(Button) Generate</Bold>
Based on the data of standard tables SEC_RULES, system generates the data into following interim tables.
<List>
<ListItem>
	MIG_SEC_RULES
</ListItem>
<ListItem>
	MIG_SEC_RULES_CONDITIONS
</ListItem>
</List>

Note
<List>
<ListItem>
	Provisional mapping information is used in guessing the target table/field name; user can further make the corrections required (if any).
</ListItem>
<ListItem>
	Security Rules Conditions has condition values, which needs verification/correction by user.
</ListItem>
</List>

<Bold>(Button) Load</Bold>
To view the data from interim tables for migrating security rules.

<Bold>(Button) Commit</Bold>
To save the changes into the interim tables for migrating security rules.


<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Checks</Bold>

Prior to performing Data Migration, pre-checks can be made on existing data. In this tab are listed certain pre-checks the utility performs. If required, customers can also add pre-checks. 

To perform these checks, this utility requires certain SQL Components (tables, stored procedures and functions) to be created in the customer’s database. 

The data is maintained in following file:
<List>
<ListItem>
	pre.checks.xml
</ListItem>
</List>

<Bold>(Button) New</Bold> 
To add a new entry in the DataGrid.

<Bold>(Button) Undo</Bold> 
To undo any modifications made in the DataGrid.

<Bold>(Button) Save</Bold> 
To save changes (if any) in the DataGrid.

<Bold>(Button) Perform</Bold> 
To perform the pre-checks.

<Bold>(Button) Reset</Bold> 
To reset the value of Status column.

<Bold>DataGrid</Bold> 
The data-grid lists the details of all the pre-checks and their corresponding stored procedure name.
It has following columns:
<List>
<ListItem>
	Order – Use this to indicate the sequence number of pre-checks.
</ListItem>
<ListItem>
	Check – Name of the pre-check.
</ListItem>
<ListItem>
	Details – Short description of the pre-check.
</ListItem>
<ListItem>
	Stored Procedure – Name of the corresponding stored procedure.
</ListItem>
<ListItem>
	Status – Status of pre-check operation.
</ListItem>
<ListItem>
	Message – Validation error message in case the pre-check fails.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Pre-Conversion</Bold>
Data migration logic of certain tables requires pre-processing of data where-in the data is generated into interim tables. 
In this tab are listed the pre-conversion operations for generating data into interim tables. If required, customers can also add new entries.

The data is maintained in following file:
<List>
<ListItem>
	pre.conv.operation.xml
</ListItem>
</List>

<Bold>(Button) New</Bold>
To add a new entry in the DataGrid.

<Bold>(Button) Undo</Bold> 
To undo any modifications made in the DataGrid.

<Bold>(Button) Save</Bold>
To save changes (if any) in the DataGrid.

<Bold>(Button) Perform</Bold>
To perform/execute the pre-conversion operations.

<Bold>(Button) Reset</Bold> 
To reset the value of Status column.

<Bold>DataGrid</Bold> 
The primary DataGrid lists the details of all the SQL Components.
It has following columns:
<List>
<ListItem>
	Order – Use this to indicate the sequence number of pre-conversion operation.
</ListItem>
<ListItem>
	Operation – Name of the pre-conversion operation.
</ListItem>
<ListItem>
	Details – Short description of the pre-conversion operation.
</ListItem>
<ListItem>
	Status – Status of pre-conversion operation.
</ListItem>
<ListItem>
	Stored Procedure – Name of the corresponding stored procedure.
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>Export (XML/Images)</Bold>

Major part of data is migrated via the DCA Engine. However, data for following functionalities are migrated separately and imported via LN Session “PLM Data Migration: Pre/Post Operations” (pdadm8161m00). 
<List>
<ListItem>
	Roles Data
</ListItem>
<ListItem>
	Permission Flags for Preferences
</ListItem>
<ListItem>
	Preferred Masks Information
</ListItem>
<ListItem>
	Text Data
</ListItem>
<ListItem>
	Thumbnail Images
</ListItem>
</List>

<Bold>Export Roles Data</Bold>
On click of this button, roles data from tables “ROLE” and “ROLE_ACTIONS” are exported to following files:
<List>
<ListItem>
	$\EXPORT_DATA_DUMPS\roles.xml
</ListItem>
</List>

<Bold>Export Permission Flags for Preferences</Bold>
On click of this button, permissions information of preferences from “SYS_PROPS” table is exported to following file:
<List>
<ListItem>
	preferences.permissions.xml
</ListItem>
</List>

<Bold>Export Preferred Masks Information</Bold>
On click of this button, names of masks that are marked as preferred are exported to following file:
<List>
<ListItem>
	$\EXPORT_DATA_DUMPS\preferred.masks.xml
</ListItem>
</List>

<Bold>Export Text Data</Bold>
On click of this button, text data for the various text fields is exported as txt files and xml files into following directory
<List>
<ListItem>
	$\TEXT_DATA\
</ListItem>
</List>

<Bold>Export Thumbnail Images</Bold>
On click of this button, thumbnail images from table “FILE_IMAGES” is exported as image files into following directory
<List>
<ListItem>
	$\Thumbnail_Images\
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>tc - tables</Bold>

Data related to "tc" tables are not migrated as a part of migrating PLM Data. Reason being that, in most cases the data comes from ERP to PLM. So, this data is expected to be already available in target application. Use this to view the data of "tc" tables available in source application. 
(Note that the name of the "tc" tables listed in this tab is not complete; only some of the basic tables are listed.).

<Bold>(Button) Load</Bold>
On click of this button, data is loaded from database and shown in the grids.

<Bold>Primary DataGrid (Tables)</Bold>
To view the list of tc based entities.

<Bold>Secondary DataGrid (Records)</Bold>
To view the records pertaining to tc entities.

<Line Stretch="Fill" Stroke="Red" X2="1"/>

<Bold>PLM Data Migration: Pre/Post Operations (Session – pdadm8161m000)</Bold>

<Bold>Introduction</Bold>

Major part of Data Migration is handled via the DCA Engine and its corresponding loader. 
There are additional operations which user needs to be performed in the target application. These operations are grouped into 3 categories:

<List>
<ListItem>
	<Bold>Meta-data</Bold>
	Used to export meta-data information into xml files, which are required by DCA Utility for PLM.
	Following actions are available under this category:
	- Export Tables and Domains Definitions
	- Export Descriptive Names Information
</ListItem>
<ListItem>
	<Bold>Pre-Load</Bold>
	These actions should be performed prior to loading the data in target.
	Following actions are available under this category:
	- (Pre-Load) Delete Standard Vaults/Areas (pdadm110-112)
	- (Pre-Load) Delete Units Management Data (pdadm510-512)
	- (Pre-Load) Delete Standard Category Data (pdadm500)
	- (Pre-Load) Delete All Users Preferences (pdadm002, pdcad001-011)
	- (Pre-Load) Delete Projects (pdadm300-301)
</ListItem>
<ListItem>
	<Bold>Post-Load</Bold>
	These actions should be performed after loading the data in target.
	Following actions are available under this category:
	- (Post-Load) Update Permissions for Preferences (pdadm001)
	- (Post-Load) Update Preferred Masks Information (pdadm601)
	- (Post-Load) Import Roles and Role Actions (pdadm400-401)
	- (Post-Load) Import Text Data
	- (Post-Load) Import Thumbnail Images (pdpdm502)
</ListItem>
</List>

<Bold>Export Tables and Domain Definitions</Bold>
Use this to export the tables and enumerated domains information of the customized application in the target.
This information is used for defining the list types mapping information for the new/customized list type and for defining the provisional tables mapping information for the customized tables/fields in the target application.
Data is exported to following files:
<List>
<ListItem>
	custom.target.table.fields.xml
</ListItem>
<ListItem>
	custom.target.used.domains.xml
</ListItem>
</List>

<Bold>Export Descriptive Names Information</Bold>
Use this to export the descriptive names of the field. This information is used in migrating the Mapping Rules (pdcad102) table.
Data is exported to following files:
<List>
<ListItem>
	custom.target.table.fields.descriptive.names.xml
</ListItem>
</List>

<Bold>(Pre-Load) Delete Standard Vaults/Areas (pdadm110-112)</Bold>
For tables pertaining to Vaults and Areas, master data is shipped along with the standard application. This will intervene (in terms of data duplication/case-sensitive issues/preferred vault indicator etc.) with the data been migrated from source application. To ensure consistency, it is required to delete the master data of following tables prior to loading the data (via DCA Tool) into the target application:
<List>
<ListItem>
	Vaults (pdadm110)
</ListItem>
<ListItem>
	Areas (pdadm111)
</ListItem>
<ListItem>
	Areas by Vault (pdadm112)
</ListItem>
</List>

<Bold>(Pre-Load) Delete Units Management (pdadm510-512)</Bold>
For tables pertaining to Units Management, master data is shipped along with the standard application. This will intervene (in terms of data duplication) with the Data been migrated from source application. To ensure consistency, it is required to delete the data of following tables prior to loading the data (via DCA Tool) into the target application:
<List>
<ListItem>
	Unit Groups (pdadm510)
</ListItem>
<ListItem>
	Units (pdadm511)
</ListItem>
<ListItem>
	Unit Conversion Class (pdadm512)
</ListItem>
</List>

<Bold>(Pre-Load) Delete Standard Category Data (pdadm500)</Bold>
For tables pertaining to Category Management, master data is shipped along with the standard application. This will intervene (in terms of data duplication) with the Data been migrated from source application. To ensure consistency, it is required to delete the data of following table prior to loading the data (via DCA Tool) into the target application:
<List>
<ListItem>
	Category Tree (pdadm500)
</ListItem>
</List>

<Bold>(Pre-Load) Delete All Users Preferences (pdadm002, pdcad001-011)</Bold>
Preferences for “pdadm002, “pdcad001 to pdcad011”are shipped as part of master data. However, the data of these tables is also migrated from source application as well. 
Use this to delete the existing data (if any) in these tables.

<Bold>(Pre-Load) Delete Projects (pdadm300-001)</Bold>
Projects (pdadm300) and Project configuration (pdadm301) data is shipped as part of master data. In certain cases, it can clash with the data migrated from source application. 
Use this to delete the existing data (if any) from these tables.

<Bold>(Post-Load) Update Permissions for  Preferences (pdadm001)</Bold>
The Data for “Preferences Metadata” table (pdadm001) is shipped as master data. The value of the “Permission” column needs to be updated to match the settings as per source application.
As the data for the tables for maintaining users preferences (pdadm002, pdcad001 - pdcad011) are migrated via DCA Tool, it is required that its values are inline/consistent as per the permissions defined under the “Preferences Metadata” table (pdadm001). 

When user clicks on this button, 
<List>
<ListItem>
	User is prompted to select following file (exported via “DCA Utility for PLM”):
	- preferences.premissions.xml
</ListItem>
<ListItem>
	Permission flag for preferences are updated in the “Preferences Metadata” table (pdadm001).
</ListItem>
</List>

<Bold>(Post-Load) Update Preferred Masks Information (pdadm601)</Bold>
Masks are shipped with master data, which are already marked as preferred. Use this button to set the preferred masks information matching the source application.

When user clicks on this button, 
<List>
<ListItem>
	User is prompted to select following file (exported via “DCA Utility for PLM”):
	- preferred.masks.xml
</ListItem>
<ListItem>
	Preferred flag value for masks is updated in “Masks” table (pdadm601).
</ListItem>
</List>


<Bold>(Post-Load) Import Roles and Role Actions (pdadm400-401)</Bold>
Data pertaining to Roles Management are not imported via DCA Tool, instead it is exported via the “DCA Utility for PLM” (PLM.DCA.Utility.exe) and imported via this session. 
This approach take care of evaluating the labels for Roles and Role Actions correctly. Since there can be additional role actions in target application, using this approach ensures that new role actions of target are also available for the migrated roles as well.

It shall be noted that following 6 standard Roles and Role Actions are shipped along with the master data:
<List>
<ListItem>
	Design Engineer
</ListItem>
<ListItem>
	General Administrator
</ListItem>
<ListItem>
	None
</ListItem>
<ListItem>
	Observer
</ListItem>
<ListItem>
	Project Administrator
</ListItem>
<ListItem>
	Project Manager
</ListItem>
</List>

It is required that during Data Migration, one should not delete these 6 standard roles. 
When user clicks on this button, 
<List>
<ListItem>
	User is prompted to select following file (exported via “DCA Utility for PLM”):
	- roles.xml
</ListItem>
<ListItem>
	New roles are created by duplicating (based on the value of (ROLE.USER_TYPE) the standard roles. 
</ListItem>
<ListItem>
	Permissions values for role actions are updated based on the xml input from source application.
</ListItem>
</List>


<Bold>(Post-Load) Import Text Data</Bold>
Text Data is not migrated via DCA Tool, instead it is exported via the “DCA Utility for PLM” as xml files, and imported via this session.
The reason for this approach is that, Text Data are stored in tables of LN Tools and its ID (number) is assigned to the various text fields in “pd” tables.
Before performing this operation, user needs to place the exported files for text data into following directory in LN Application Server. 

<List>
<ListItem>
	$BSE/tmp/MIGRATION/PLM_TEXT_DATA/
</ListItem>
</List>

When user clicks on this button, 
<List>
<ListItem>
	System reads the contents from the temporary directory.
</ListItem>
<ListItem>
	Text Data is set for the migrated records and records are saved.
</ListItem>
</List>


<Bold>(Post-Load) Import Thumbnail Images (pdpdm502)</Bold>
Thumbnail Images are not migrated via DCA Tool, instead these are exported via the “DCA Utility for PLM” as image files (.png/.jpeg), and imported via this session.
The reason for this approach is that, Thumbnails Images are stored as files under LN Tools; a compact GUID is used as reference for this in the “File Images” (pdpdm502) table.
Before performing this operation, user needs to place the exported image files into following directory in LN Application Server.
<List>
<ListItem>
	$BSE/tmp/MIGRATION/PLM_FILE_IMAGES/
</ListItem>
</List>

When user clicks on this button, 
<List>
<ListItem>
	System reads the contents from the temporary directory.
</ListItem>
<ListItem>
	Thumbnail Images are copied from temp location to the File Images directory of LN Tool.
</ListItem>
<ListItem>
	The value of field “Thumbnail” is updated in the “File Images” table (pdpdm502).
</ListItem>
</List>

<Line Stretch="Fill" Stroke="Red" X2="1"/>


