How Does the VPLMPosExport Tool Work?

You can extract P&O data from an ENOVIA V6 repository to text export files containing the definition of this data by using the VPLMPosExport tool. The tool allows you to export one or all specific P&O object(s).

Note: Information about casual licenses is not supported in P&O import batch VPLMPosExport.

Data Consistency

Export files are complete in terms of inter-object dependencies: when exporting a particular object (e.g. a person), all its direct dependencies (e.g. the parent organization of the person) are also exported, as well as the dependencies of these dependencies (e.g. the parent of the parent organization, etc.).

As a consequence, any export file created can be imported into an ENOVIA V6 repository without encountering errors due to missing dependencies.

Furthermore, the export mechanism removes possible redundancies, should objects be referenced several times (for example, a context object will be exported only once even though it is assigned to several users).

Data Completeness

In addition to data consistency, the export mechanism also ensures data completeness so that, when exporting an object, all possible information involved in the definition of that object and that might be relevant when using it, is also exported.

For instance, when exporting a person, his/her parent organization is also exported, as well as his/her working contexts, so that the resulting export file contains all relevant information associated to the person.

Note: These dependencies are different from those described above; for example, from a pure syntactic point of view, an export file would still be consistent without a person's business attributes - but it would not be consistent from a global point of view since the information concerning the person wouldn't be complete.

Security Data

In this release, security data can be browsed or extracted using standard ENOVIA V6 tools such as the Business application or the MQL interpreter: no support for this type of data is provided by the VPLMPosExport tool.

Please note that MQL commands do not produce results using MQL syntax (even though they bear resemblance) so they may not be imported as is (as is the case for files generated by VPLMPosExport).

The VPLM administrator may also take advantage of standard ENOVIA V6 import/export programs, even though these tools are more dedicated to replication than administration.