Import Process

Click OK to check the fields in the window for validity:

• Is the storage location valid?

• Is there a valid input file?

• Do we need to convert the file across platforms?

• Are the Profile and Material mapping files valid for the Source Package as identified in the Header of the input file?

After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not even exist. You are asked if you want to carry on waiting for another time unit.

Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.

You are alerted to unsuccessful runs by the external program displaying an error message, after which the process exits.

If the external program successfully completes, the processed SDNF file is imported into MODEL. Any reference data which may have been retained is deleted.

The status line informs you of the progress on importing the data. As a rough guide, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members is about 7500 lines long.

Note:
This calculation can be useful when considering the maximum input file size, the size applies to this file, and not the original SDNF source file.

After the Import of everything, the material properties are reconciled with the :SDNFMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database.

At this point, if you have chosen to be asked whether to Merge after the Compare operation, a Confirm window displays.

Click Yes to continue with the Merge process.

Click No and the Import process skips the Merge process, you are then given a chance to store the Merging commands in a file for use later only in the current session. You cannot use a file from a previous SDNF session as the Import data may be incorrect.

You can save the Merge command file and then be prompted whether to view the Import log file. The Merge command file may then be used in the Merge from File option on the AVEVA SDNF - Import window. The latter option needs the reference model from this run to be kept. Therefore, some other options become unavailable.

If you have merged the models, you are then asked if you want to keep the reference model, verifying the option selected on the Run Information window.

This reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.

Finally, you are then asked whether to view the log file, if you have chosen that option on the Run Information window.

If you want to inspect the log file, you can save it with the File > Save as option in the SDNF File Viewer window which displays a File Browser, or click Save as to the suggested filename. If the file exists, you are asked if you want to overwrite it. The log file window can then be closed, click Cancel.

If you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. To save the log file, however, all messages are be retained in the file.

If you click a line containing an application reference number, the chosen item displays in all graphical views. The interface also navigates to the item in the database, allowing you to perform further queries or operations.

Error and Log File Messages