Import Data Load |
The Import Data Load tab enables you to define and process an upload from an external system and display a count of the number of transactions accepted and rejected during the processing.
You can arrange for the external system to transmit as many files to the software as is convenient, from any number of locations. This software does not poll the external system. You must arrange for the system to transmit to and store the files on the hard disk of a computer running this system. You can also process files stored on diskette.
When you load files from an external computer or system into the application, you must use a communications program that allows you to capture incoming data into a file. Examples include Crosstalk (MicroStuf), Smartcom (Hayes), ProComm (available as shareware on most bulletin boards), and ProCommPlus (Datastorm). When you use one of these programs, be sure to set them so that they do not filter out any control characters sent from the external system. For example, in Crosstalk, set the program defaults so that INFILTER is OFF.
The application bypasses any preliminary characters in the input file prior to the first fuel ticket. You do not need to edit the input file prior to the time you process it.
This system charges the amount and cost represented by each transaction to the equipment unit identified on the transaction.
Retention information for functional areas is specified on the Retention Levels tab of the System Mgmt -> Setup -> Table Management screen. Obsolete entries are purged when you use the System Mgmt -> End of Period screen to execute the Purge obsolete database entries feature if there is a check in the Processing completed field
Tip: To limit the display of information in the grid and maximize performance, use the filter. You can sort on run ID, import ID, import file name and path name, and import start date and time, among other values.
The field in the top section of this tab defines the data that displays.
Run ID
Identifier assigned to each upload. The run description displays to the right of the ID. This field has a list box. Data in the fields in the bottom section of the tab define the upload of transactions and display the results of the processing of the upload. Unless otherwise indicated, these fields are required.
Run description
Description of the upload, typically used to distinguish it from other uploads. It can include the date and other identifying information. Use hyphens, not slashes, to separate the date elements. Required.
User ID uploading
Identifier of the user performing the upload. This field has a list box. The user name displays to the right of the ID.
Import file name and path
Name of the file to load into the database, including the drive (if the file is not on the current drive) and directory path (if the file is not in the current directory). Required.
The files are processed one at a time, as you instruct. Although you cannot process a group of files together using wild card characters in the file name, you can concatenate (merge) a group of files into a single file before you process them. There are no restrictions on the names that you can use for these files, except that none of the names can be the same as a file name that the system uses. To ensure that there is no name conflict, you might use an extension (after the dot) of EXS for all such files; the name portion might identify the source location and the date (such as AB0315.EXS).
Import start date and time
Date and time (in MM/DD/YYYY HH:MM format) that the user began the upload. This field is display only.
Processing started
If this field has a check, processing has begun on the data in this upload. This field is display only.
Processing completed
If this field has a check, the data in this import run has been processed. This field is display only.
If this field has a check, the entries made by the run ID are deleted when you use the System Mgmt -> End of Period screen to purge obsolete database entries.
Accepted transactions
Number of transactions accepted during the processing. Display only.
Rejected transactions
Number of transactions rejected during the processing. Display only.
Special action
Action to take to resolve processing errors. Available only during Update mode, this field has a list box:
NONE
CONTINUE PROCESSING: Select this option if the initial processing of all transactions has not been completed (i.e., the Processing completed field does not have a check).
REPROCESS REJECTED: Reprocesses rejected transactions.