A physical column maps to a specific column in the input CSV file. There may be cases where a value that is required for a mapping is either not available in the physical file or the physical data supplied needs to be reformatted. In such cases, a computed column can be set up. For example, you may need to create a specific type of SPO/E engineering document depending upon the document type class definition provided in the CSV file.
-
We recommend that all mappings are prefixed.
-
If an object, property, or relationship in the target system already exists in the staging area, then you must rename the object, property, or relationship when saving the respective mapping. For example, when mapping the Area column header to the SPFFunctionalArea classification, you must modify the class definition name by adding a prefix such as SDV. You would then type SDVSPFFunctionalArea in the Maps to Object box.
-
The Relationship Mapping option is not enabled until at least two objects have been mapped.
-
You can use the SmartPlant Foundation SmartConverter to hotspot drawings. For more information, see Configuring the SmartConverter for Graphical Navigation.
-
When creating a job for exporting the SPO/E documents to the target system, you must suppress the ENS. Otherwise, the documents you are exporting will be assigned ENS generated names in the target system and the relationship between the tags you are exporting and these documents may not be established. To suppress the ENS, in Data Validator Job Management, select the Suppress ENS checkbox in the Create New Job dialog box.
Use the following illustration and tables to create your own document mapping.
