Importing Transfers (Transactions)
Transfers are not imported into PI tags, nor are they a direct part of cases. Transfers are stored instead within the Sigmafine AFDatabase and are collected into cases. You can import material transfers into the Sigmafine AFDatabase by these ways:
Load data that is available in the file into the AFDatabase.
Use a control table to modify or insert data if it is missing.
The control table is an AF Table in the Sigmafine AFDatabase that is used in the import operation. The control table can do operations on the data that include validation and calculation of values. See section "Using a Control Table" for a definition of this table.
The command line syntax and a table of parameters are given below.
Importing without a Control Table
DataLoader.exe -Filename=file name –afserver=Server name –AFDatabase=AF database name –template=Transfer template name -format=Sigmafine version -Type=Transfer -Debug=Yes or No –ChkDuplicates=Yes or No
Importing with a Control Table
DataLoader.exe -Filename=file name –afserver=Server name –AFDatabase=AF database name –template=Transfer template name -format=Sigmafine version -ControlTable=AF Table Name -StartTime=”Timestamp” -EndTime=”Timestamp” -StartatRow=RowNumber -Type=Transfer -Debug=Yes or No –ChkDuplicates=Yes or No
Command Line Parameters – Transfers (No Control Table)
| Parameter | Required | Description |
|---|---|---|
| Filename = Drive:\Path\Filename | Yes | Full path name of the data file. Relative file paths are not supported. |
| AFServer = AFServerName | Yes | Name of the PI server that hosts the AF Database. |
| AFDatabase = AFDatabaseName | Yes | Name of AF database that contains the elements used for the imported data. |
| Template = TemplateName | Yes | The name of the transfer template used to create the transfers. For example, if using the default naming of the Sigmafine template, this argument is: Template = SF_TransferTemplate |
| ControlTable = AFTableName | No | Name of the control table that describes the column names and formula expressions. This is described in sections “Sigmafine 3 Format for Transfer Data (With Control Table) and Sigmafine 4 Format for Transfer Data (With Control Table).” |
| Format = Sigmafine4 | Yes | Use the Sigmafine4 keyword to indicate the file has a Sigmafine 4.x format, respectively. |
| Type | Yes | To import transfer data use the Transfer keyword. |
| StartTime = “timestamp” | No (Used with Control Table) | When using a control table, this argument forces the transfer start time if not defined in the data file. The format of the time stamp depends on the Windows regional settings.For example, for English US time stamp is:12/24/2010 2:00:00 PMfor the date: December 24, 2010 at 14:00:00. |
| EndTime = “timestamp” | No (Used with Control Table) | When using a control table, this argument forces the transfer end time if not defined in the data file. The format of the time stamp depends on the Windows regional settings.For example, for English US time stamp is:12/24/2010 2:00:00 PMfor the date: December 24, 2010 at 14:00:00. |
| StartAtRow = X | No (Used with Control Table) | When you use a control table, this argument specifies the starting row of the data. If not supplied, the first row is used as the starting row. Rows start with row 1. |
| Debug = YesorDebug = No | No | Use the keyword “Yes” to enable debugging messaging to the log file. Use “No” to disable debugging. If not present, debugging is off. |
| ChkDuplicates = Yes or ChkDuplicates =No | No | Use this option to check for duplicate transfers by name stored in the AF database. Use Yes to check for duplicates. Use No to disable duplicate checking. If not supplied, the check for duplicates is off (Default = No). |