Importing V5 Data by using Mapping Tables

This task describes how to import V5 Data in Asynchronous Mode.

1. Select PLM Access > Import > CATIA File... to open FBDI. For more information, please refer to Running FBDI Interactively.

2. Check Use Mapping Tables in the Execution Mode section.

   In the following example we will import an Assembly containing already imported data (Wheel2.CATPart for example).

   
   
   

3. Click OK to import Wheel2.CATPart.

4. Select PLM Access > Import > CATIA File...

5. Select Car2.CATProduct in the Select File window and click Open. The File-based Design Import window is displayed. The element already present in the database is Wheel.CATPart:

   	Selected element	Migration status
   Parent	Car2	Not yet
   Sub-elements (1rst level)	Board2	Not yet
   	AxleAssembly2	Not yet
   	Wheel2	Migrated

6. Check the Use Mapping Tables options:
   
   

7. Click OK and the Files to Process window is displayed:
   
   

   Note: Wheel2 does not need to be imported ("no Import") since it has already been imported in V6 in Asynchronous Mode. It will only be reopened in V6. And the other elements will be imported in V6.

8. Click Import. The Report appears and the car is edited in V6 and it is automatically saved in database.

   If you close the editor, you no longer need to re-import it, since it has been saved in the database (you can find it back via Search). For information, it is possible to run the FBDI in Asynchronous Mode via the FBDI Batch, please refer to Running the FBDI Batch.

This functionality is directly linked to the Asynchronous mode of FBDI as Mapping Tables as a prerequisite to identify the files already imported.

1. Check the Mapping Tables option in the Select the files to import window:
   
   If this button is not activated, the Update and No re-import options will not be available.

2. Before executing the FBDI Check or Import command, choose the behavior for Newer, Identical, or Older files: Update or No-reimport mode in Similar Documents options section of the Select the files to import window:
   
   

   If you do not select the Use Mapping Table check box, these options will not be available. By default, the No re-import option is selected for Identical and Older Files option. Update is selected for Newer files option. The selected option is used during the dependency bundle computation

   Using Mapping Tables, FBDI can identify documents that were already imported. For more information about the criteria used in this operation, please refer to V5 Data Supported by FBDI.

   Depending on the selected option (Update / No re-import), and the comparison result (Identical / Similar / New), the dependency bundle computation associates one of the following actions to each file pointed directly or indirectly by the files selected by the user
   

   • Import: if no corresponding data exists in the database or the user chooses not to use the Mapping Tables, the file will be imported.
   • No Import: the file has already been imported. It will not be re-imported. There is no update of data.
   • Update: a similar document has already been imported; its result will be updated with this new version of the file.

   The following tables list the action taken on each file depending on the selected option (Update / No re-import) and comparison result (Identical / Similar / New):

   Newer files option	FBDI Option
   	No-Reimport	Update
   Similar (Newer) file status	No Import	Update

   Identical files option	FBDI Option
   	No-Reimport	Update
   Identical files statuses	No Import	Update

   Older files option	FBDI Option
   	No-Reimport	Update
   Similar (older) file status	No Import	Update

   Note: The new files, not referenced in the FBDI mapping, always have an "Import" status.

   About the dependency bundle: if you select the Update option for similar or identical documents, all the pointed files will be introspected and their statuses computed, even those pointed by an already imported file, to Update the whole structure. The only exception is for the similar files which are not updated; in this case, the pointed files are not added to the dependency bundle.

3. Select Update to update existing data with this version of the file. Using the 'Update' mode will import the data by updating the PLM Components created in the previous import. The existing PLM components are opened and their content overwritten. The following conditions must be met for saving the PLMComponent: for Similar files.

   
   

   • The component must not be versioned in V6
   • The component must not be locked by another user
   • The maturity of the component must authorize modifications

4. Select No re-import for similar files.

   Already existing data will be used. The mapping tables corresponding to the similar files won't be updated as existing data are not modified.

   Warning: About Security and Maturity: The Update action can be impacted by the security environment (P&O) and the maturity of the already imported PLM Component. If the user does not have the rights to overwrite data or if the object's maturity prevents the overwrite of data, it will not be possible to use FBDI in Update mode. A message explains the problem in the HTML report. The links pointing a Technological Representation or another Representation migrated Ex Situ will be broken after a migration with the Update mode, as the internal identifiers of the data and of the containers are not kept. When using the 'update' mode, the PLM Component are overwritten in the database. The modifications done in CATIA V6 are lost by using this mode To be able to update a component, it has to be loaded. If the component has been deleted in V6, or if the user don't have the right access to open it, FBDI Replace will fail. It is recommended that the data imported with FBDI should not be modified in CATIA V6 if they can be modified in CATIA V5 and imported again in update mode. No warning messages are displayed before the PLM Components are overwritten. If these PLM Components were modified in CATIA V6 after the previous import, the modifications done on the data will be lost. It is however possible to modify the imported data in V6 in some ways (example: adding an instance, a Port or a Connection to the data). FBDI in Update mode won't remove those kinds of PLM components. The user must be careful as the naming of those components could prevent the creation of a Component with the same name coming from FBDI in update mode. This mode should only be used if the data are still edited in CATIA V5 and not in CATIA V6.

   Note: Some application does not deploy the full support of the FBDI Update mode. Using the Update option on the corresponding data will create new PLM Components and remove the previously created one each time the command is used on those files.