Using .vpmuuid_lst Files with CoexistenceBatch

This task describes the use and contents of vpmuuid_lst files.

If, after launching the CoexistenceBatch batch, you select a .vpmuuid_lst file as the input file type, the result will be the transfer of all the references listed in the file and all their first-level children:

Let's take the following Product Structure:

If the .vpmuuid_lst file contains the VPMUUIDs of references P0, P1, P2 and P3, the corresponding objects created in 3DEXPERIENCE will be:

i.e. references P0, P1, P2, P3, P1.1, P2.1, P3.1 and the instance between the references. If you want to include the representation as well, the VPMUUIDs of references P1.1, P2.1 and P3 must be added to the .vpmuuid_lst file.

The new extension vpmuuid_lst makes it easier to differentiate between the file types. The vpmuuid_lst file uses the XML format as a core with specific tags and attribute names:

The first line contains the XML header <?xml version="1.0" encoding="UTF-8"?> and enoviavpm_transfer is the root tag name.

Each reference is represented by a node named enoviavpm_object containing two attributes:

  • the attribute name containing the identifier of the reference provided as input, to be used for debugging purposes for quick retrieval of the failed reference.
  • the attribute uuid containing the VPMUUID with the following format:
    • the CATCON must be 8 characters: "CATCONxx"
    • the ENOVIAvpm environment must be 8 characters: "VPMENVxx"
    • the ENOVIAvpm table must be 18 characters: "PART_LISTxxxxxxxxx"
    • the COID must be 16 characters: "3D3DA9867FAC7EDC"
    • the COMPID must be 16 characters: "3030303030303030"
Important: It is your responsibility to provide the CoexistenceBatch batch with a file with the right format.