Manage Asset Location Exceptions

Use this screen in conjunction with the Import Asset Locations screen.

The Import Asset Locations screen imports an ASCII file produced by reading property bar code labels with a bar code scanner. On that screen, you can import either a specific file or you can select the Exceptions Table as the input source.

During the import process, the system automatically compares the results of the scanned location data with the location data already residing in the Asset Master record and writes the exceptions to an Exceptions table. This screen, Manage Asset Location Exceptions, displays and identifies each exception found, such as an invalid asset/item number, invalid location group, invalid location code, and so on.

This screen automatically displays all data scanned for the row, whether the data is valid or invalid. Refer to the Columns in Which Data Errors Exist column to determine which field(s) displays as an error condition.

You can save a row with error conditions as long as its status is On Hold. You must correct all error conditions before you can successfully save a row with a Selected status (for subsequent upload from the Exceptions table).

The system does not update the display of error conditions in the Columns in Which Data Errors Exist on a real-time basis as you make corrections. This column will always display the original error condition(s), even after corrections are saved, unless you make manual edits to the displayed error conditions.

Note: Once you have corrected the error condition(s), placed the record on Selected status, and attempted to save the table window, the system automatically performs validations for each data column in the row before saving.

Once you have edited the exceptions on this screen and selected the rows for processing, you can go back and re-run the import process again from the Import Asset Locations screen.  hen you re-run the process, upload only the corrected data from the Exceptions Table to the Asset Master records rather than the originally scanned data.

Because there is no system validation for duplicate records, rows may be duplicated in this table window for the same error condition. This type of error could occur if you inadvertently scanned the same bar code label more than once. Two remedies are available:

• You can delete the duplicate row; OR
• You can leave the duplicate row, making sure that all error conditions are corrected identically in each duplicate row.

Because the system processes rows sequentially from this screen, to avoid unexpected results, use caution when making corrections for duplicate rows.

Edit data on this screen at any time, provided that exceptions data have been previously written to the Exceptions table (by running the process from the Import Asset Location screen).