Professional Documents
Culture Documents
The documents, target, directory and report name can be selected in the PLMV4ToV5Migration window. This migration tool provides an interactive
interface working on a different application from CATIA Version 5.
You can have access to the read-only LCA and VPM databases.
4. Click on to select the file to be migrated. The File Selection dialog box is displayed.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 1/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
The options, Rename Criteria and Output Option are not taken in to account by PLMV4TOV5Migration batch. Also the option select by
modification date of Input options tab is not taken in to account because model doesnot have modification date like V5 document.
6. In the Selected Operation field, you can choose different settings:
Selection Mode:
Complete: you can migrate Sets, Solids and/or Layers As Result or As Spec.
In interactive mode, you have an user defined mode with the command Send To V4ToV5Migration.
In Complete mode, select a line, SOLID for instance, and choose a Format: by clicking one of these buttons:
.
Option:
Check: for simulation. For more information about this option, please refer to Checking V4 Model data before Copying
it to V5.
or Migrate: V4 To V5 Migration will be applied.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 2/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
or Migrate: V4 To V5 Migration will be applied.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 3/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
Structuring Element:
Depending on the combinations, you can select 0 or 1 or several boxes (Ditto). By this way, you define
a document per entity type. According to configurations, you can also explode Dittos.
But some combinations are not supported and a Warning appears if you have selected wrong
combinations. The following table shows you what is supported (X):
What is
supported LAYER SOLID SET DITTO
(X)
1 X
2 X
3 X
4 X
5 X X
6 X X
7 X X
8 X X X
9
10 X X
To have information about the following options, you can refer to the documentation Customizing
Migration Batch:
Conversion Mode,
Drawing Parameters,
7. Click Next again and the following dialog box appears as shown below.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 4/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 5/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
9. If you select the Run button in the PLMV4ToV5Migration window, the Check or Migrate operation is launched.
For information, if you have checked the Work with the cache system option (by default, the cache is not activated.) in Tools > Options >
Infrastructure > Product Structure, the Migration Batch will automatically download the V4 documents in Design Mode. Therefore, the first Report
information is: "Swapping in Design Mode"; double-click the line to have more details about the migration.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 6/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
If you had migrated by Copy / Paste you may not have the same result. Batch reduces the number of interactions and offers possibilities to make more
relevant migrations for complex V4 data structures. To understand the migration status you can Visualize the Report of Batch Execution.
According to its content, a model is migrated into several documents: a CATPart and / or a CATProduct and / or a CATDrawing. To separate the
treatment of SPACE data and DRAW data, click on the Options button and the Tools > Options > V4 / V5 Infrastructure window is displayed: you
can select Space And Draw, or Space or Draw.
For more information, refer to Customizing V4/V5 DRAW and Customizing V4/V5 SPACE in CATIA Infrastructure User's Guide.
When a model contains DRAW data, they are migrated as a unique document : a CATDrawing.
In the Batch Mode, like if you Copy / Paste a Draft or a View interactively, only details instantiated directly or not in the master are migrated.
If you have checked the setting Open in Light Mode: 2 Data is not taken into account in Tools > Options > V4/V5 Infrastructure, the batch
will not be able to migrate V4 Drawing data. Therefore, if you want to convert V4 drawing elements in CATIA V5, it is necessary to uncheck
this setting.
The targeted directory file path must point to a folder in which output files are saved. The strings such as .model or .session should not
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 7/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
appear in the whole file path or in the name of the folder.
The Tools / Options / Compatibility / Migration Batch tab options are not taken into account by the PLMV4ToV5Migration Batch.
The "V4 Part" definition is the Geometric Set: the subsets will be migrated into a V5 CATPart document.
The "V4 Part" definition can also be a Solid: the Solids will be migrated into CATParts and the non-solid elements (for instance: Wireframe) into a
CATPart as well.
1. Every Geometric Set contained in a model generates a CATPart (only Dittos are managed separately).
2. Every Workspace containing several Dittos or Set instances is converted as a CATProduct. Under this CATProduct, there are as many
components as Dittos (Part or Product instances) and Sets (Part instances only).
When you convert an .asm through the migration batch, you obtain a CATProduct. The result is the same when you read (File/Open) a .asm in CATIA
V5; for more information about Opening an .asm Document in CATIA V5, please refer to the CATIA - Assembly User's Guide.
This table shows you what you can get in CATIA V5 after the Batch conversion:
V4 V5
.asm Product
Take the example of the WAGON.model and look at the conversion results. The model has been
converted into a CATProduct containing two Dittos (of AXLE) plus a Geometric Set (the red
box). AXIS and WHEEL are two Details, the one contains two Dittos of WHEEL and the other
has a ditto of AXIS.
AXLE > CATProduct
AXLETREE > CATPart
WHEEL > CATPart
SET > CATPart
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 8/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 9/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
By setting CATV4V5ReportNew=1 environment variable in your CATIA session, you can generate a report using the enhanced template ( .xsl style
sheet) provided by Dassault Systems. The default template with .xsl style sheet provided to you can be customized to you needs.
When PLMV4ToV5Migration Batch is executed, the conversion report is generated which provides information about the conversion status for all the
models and of the features whose conversion has failed. It also displays the list of features which were successfully converted but the conversion
update has failed.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 10/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
The style sheet (used to customize .html file) in .xsl format
Html
Sample File
Report
XML
Report
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 11/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
The report consist of three part:
Some information about migration general option,
A tree representing all the converted elements with their status,
A short sum up.
In user define and batch conversion, the report files (.xml and .html) will provide you the following information:
Model name(s) and model conversion status,
Time and date stamp of the conversion,
V4 feature name (primary and secondary type) and feature conversion status for features that failed or succeeded conversion,
V4 feature name (primary and secondary type), V5 feature name, feature conversion status and feature update status for the features that
failed the update.
Regardless of the method of migration you choose, interactive (Copy/paste), User define or batch, you will get a report with the same information
format.
Note: It is not possible to generate the report in case if you use the batch with a specific migration like AEC or Electrical.
In both the methods of conversion (interactive and Batch conversion) the report files are stored in the folders as mentioned below,
The report (only .xml file) for interactive conversion (copy/ paste) will be saved in
C:\Documents and Settings\username\Local Settings\Application Data\DassaultSystemes\CATReport.
The report (.xml and .html files) for batch conversion (PLMV4ToV5Migration) will be stored in a location specified by the user.
By default, the .xsl file consisting of style sheet is stored in the installation. However, you can customize the default style sheet to view the
report in the required format and save it in the specified location. By setting CATV4V5ReportXSLPath =path of the customized XSL file,
environment variable in your CATIA session.
General Cases:
The entities being able to have a uuid are: by default, the workspaces are the only elements which have a uuid. Another element can have or
not a uuid, depending if they are published or not. The publishable elements are geometrical entities except dittos.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 12/13
10/25/13 Converting CATIA Version 4 Models into CATIA Version 5 with the PLMV4ToV5Migration Batch
During the check, it makes it possible to see the problems upstream, the generation of documents which could false.
But if the selected action is the migration, the user will also see the problems via the report, but the documents are nevertheless generated.
General information: The lists of the elements find for each UUID representing a problem.
Information for each element: unknown status propagated for the entities in conflict.
The Check of UUID does not solve these problems, it only gives information. However, there are solutions to solve the conflicts:
If the UUID in conflict are in distinct documents, the user migrates each document separately.
catiadoc.free.fr/online/intug_C2/intugbt0227.htm 13/13