Use this screen in conjunction with the Asset Location Preprocessor screen.
The Asset Location Preprocessor screen imports an ASCII file produced by reading property bar code labels with a bar code scanner. In 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, Maintain 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 "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (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.
Once you have edited the exceptions in this screen and selected the rows for processing, you can go back and re-run the import process again from the Asset Location Preprocessor screen. When 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.
You can delete the duplicate row.
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 in this screen at any time, providing exceptions data has been previously written to the Exceptions table (by running the process from the Asset Location Preprocessor screen).
You cannot add new lines, insert lines, or repeat lines in this table window. You can, however, delete and/or undelete rows, edit data, and select or place rows on hold in the table window.
Rows display in this table window until they are corrected and uploaded from the Asset Location Preprocessor screen or until you manually delete them. Each time you run the process from the Asset Location Preprocessor screen, additional exceptions, as applicable, are inserted into the table and display in this screen.
The system automatically inserts data that fails validation(s) into this screen during the Asset Location Preprocessor screen import process.
Each row in this screen initially displays a status code of "H" (On Hold). You can change the status code to "S" (Selected) when you have corrected all errors to signify that the row is ready to be processed from the Asset Location Preprocessor screen, using the Exceptions Table as the input file.
When you run the process from the Asset Location Preprocessor screen, you can import only rows with an "S" (Selected) status code from the Exceptions Table.
This non-editable column displays the date and time that the row was inserted into the Exceptions Table when you ran the process from the Maintain Asset Location Preprocessor screen using a file as the input source.
This field does not display the date of the bar code label scan.
This non-editable column displays the ID of the user who ran the process from the Asset Location Preprocessor screen using a file as the input source.
The user ID in this column is not necessarily the ID of the user who performed the bar code label scan.
When you import a file containing scanned data via the Asset Location Preprocessor screen, the system automatically assigns a "behind-the-scenes" sequential line number for each line of data for reference purposes. The system-assigned input line number automatically displays in this column and cannot be edited.
This required editable column displays the company ID of logon used in the scan.
When you ran the process from the Asset Location Preprocessor screen using an input file, you were required to select whether to read the input file by asset/item number or by tag number. Your selection was based on whether you had coded the asset number or the tag number, if different, onto the printed bar code label.
You must assign each Asset Master record a unique asset/item number before you save it, but tag number data is optional for each Asset Master record and may be missing or duplicated among different Asset Master records.
If you enter data in the file by asset/item number in the Asset Location Preprocessor screen, the system validates each asset number scanned before upload. The validation must also include the item number, but if a bar code label contains the asset number and no item number, the input file must supply the related item number.
If the system cannot validate both the asset number and the associated item number from a scanned record, it will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
You should refer to the Columns in Which Data Errors Exist column to determine whether the Asset No column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
The Asset No column may be blank as a result of a data error. If this happens, you must enter a valid asset number or use Lookup to select one. Because this is a standard Lookup to the ASSET table, you may find that you have selected asset/item numbers that are inappropriate for the scanned data.
This type of error could occur if you enter the file by tag number in the Asset Location Preprocessor screen and the system cannot find the associated asset number in the Asset Master table.
If you enter the file by tag number in the Asset Location Preprocessor screen, the system must still associate the tag number with, and validate against, the related asset and item number.
You must assign each Asset Master record a unique asset/item number before you save it, but tag number data is optional for each Asset Master record and may be missing or duplicated among different Asset Master records.
When you ran the process from the Asset Location Preprocessor screen using an input file, you were required to determine whether to read the input file by asset/item number or by tag number. Your selection was based on whether you had coded the asset number (and optionally the item number) or the tag number (if different) onto the printed bar code label.
If the system cannot validate both the asset number and the associated item number from a scanned record, it will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
Refer to the Columns in Which Data Errors Exist column to determine if the Item No column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
The Item No column may be blank as a result of a data error. If this happens, you must enter, or use Lookup to select, a valid item number. Because this is a standard lookup to the ASSET table, you may find that you have selected asset/item numbers from the lookup that are inappropriate for the scanned data.
This type of error could occur if you enter the file by tag number in the Asset Location Preprocessor screen and the system cannot find the associated asset/item number in the Asset Master table.
When you ran the process from the Asset Location Preprocessor screen using an input file, you were required to determine whether to read the input file by asset/item number or by tag number. Your selection was based on whether you had coded the asset number (and optionally the item number) or the tag number (if different) onto the printed bar code label.
If you enter data in the file by tag number in the Asset Location Preprocessor screen, the system must still associate the tag number with, and validate against, the related asset and item number.
Each Asset Master record must be assigned a unique asset/item number before you save it, but tag number data is optional for each Asset Master record and may be missing or duplicated among different Asset Master records.
If the system cannot validate both the asset number and the associated item number from a scanned record, it will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
Refer to the Columns in Which Data Errors Exist column to determine if the Tag No column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
If you have used the location group code as part of your bar code label, the label may display an invalid location group code. This could occur if you made a typographical error when printing the bar code label or inadvertently printed an invalid location group code on the bar code label.
The location group code may not have been included in the bar code data printed on the property label, and there is no system requirement for one. Location group code data is always optional in an Asset Master record but, if entered, the location group code must have been previously entered in the Location Groups screen.
If there is a location group code and it cannot be validated, however, the system will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
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 whether the Loc Grp Cd column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
To correct the error condition, enter, or use Lookup to select, a valid location group code or blank out the invalid location group code in this column. Because this is a standard Lookup to the FA_LOCATION_GRP table, you may find that you have selected location groups that are inappropriate for the scanned data.
If you have used Location Code 1 as part of your bar code label, the label may display an invalid location code. This could occur if you made a typographical error when printing the bar code label or inadvertently printed an invalid location 1 code on the bar code label.
The location code may not have been included in the bar code data printed on the property label, and there is no system requirement for one. Location code data is always optional in an Asset Master record, but if entered, the location code must have been previously entered in the Location 1 Codes screen.
If there is a location code and it cannot be validated, however, the system will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
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 whether the Loc Cd 1 column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
To correct the error condition, enter, or use Lookup to select, a valid location 1code or blank out the invalid location code in this column. Because this is a standard Lookup to the FA_LOCATION table, you may find that you have selected location codes that are inappropriate for the scanned data.
If you have used Location Code 2 as part of your bar code label, it the label may display an invalid location code. This could occur if you made a typographical error when printing the bar code label or inadvertently printed an invalid location 2 code on the bar code label.
The location code may not have been included in the bar code data printed on the property label, and there is no system requirement for one. Location code data is always optional in an Asset Master record, but if entered, the location code must have been previously entered in the Location 2 Codes screen.
If there is a location code and it cannot be validated, however, the system will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
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 whether the Loc Cd 2 column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
To correct the error condition, enter, or use Lookup to select, a valid location 2 code or blank out the invalid location code in this column. Because this is a standard Lookup to the FA_LOCATION table, you may find that you have selected location codes that are inappropriate for the scanned data.
If you have used Location Code 3 as part of your bar code label, the label may display an invalid location code. This could occur if you made a typographical error when printing the bar code label or inadvertently printed an invalid location 3 code on the bar code label.
The location code may not have been included in the bar code data printed on the property label, and there is no system requirement for one. Location code data is always optional in an Asset Master record, but if entered, the location code must have been previously entered in the Location 3 Codes screen.
If there is a location code and it cannot be validated, however, the system will reject the record from the upload, write it to the Exceptions table, and display it in this table window.
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 whether the Loc Cd 3 column displays as an error condition. You can save a row with error conditions as long as its status is "H" (On Hold). You must correct all error conditions before you can successfully save a row with an "S" (Selected) status (for subsequent upload from the Exceptions table).
To correct the error condition, enter, or use Lookup to select, a valid location 3 code or blank out the invalid location code in this column. Because this is a standard Lookup to the FA_LOCATION table, you may find that you have selected location codes from the lookup that are inappropriate for the scanned data.
This non-editable column displays the name of each column in which data errors exist. Because the system displays ALL data scanned for the row, whether the data is valid or invalid, the purpose of this column is to list the data error conditions.
Note that the system does not update the display of error conditions in this column 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 in this column.
Once you have corrected the error condition(s), placed the record on "S" status, and attempted to save the table window, the system will automatically perform validations for each data column in the row before saving. You cannot save if any error condition exists for the row.
This required and editable column displays a "Scan By" option code that you selected when you logged into your Intermec bar code scanner (prior to the actual bar code scan). These codes determine how the location validation rules are applied during the update portion of the Asset Location Preprocessor routine.
The following six option codes are available:
Code "A" = All location data (includes location group code and all three location codes)
If you are scanning by "A" (All) and the Location Group Code is subsequently updated in the Asset Master record, the system retrieves all location data related to the Location Group Code (including Location Codes 1, 2, and 3, as applicable) and updates the Asset Master record with that data as well.
Code "G" = Location Group Code data (excludes Location Codes 1, 2, and 3)
If you are scanning by "G" (All) and the Location Group Code is subsequently updated in the Asset Master record, the system retrieves all location data related to the Location Group Code (excluding Location Codes 1, 2, and 3, as applicable) and updates the Asset Master record with that data as well. (In this circumstance, data for Location Codes 1, 2, and 3 will be supplied by the input file.)
Code "L" = Location 1, 2, and 3 Codes only, as applicable
If you are scanning by "L," the system compares/updates only Location Codes 1, 2, and 3, as applicable.
Code "1" = Location 1 Codes only
If you are scanning by "1," the system compares/updates only Location 1 Codes.
Code "2" = Location 2 Codes only
If you are scanning by "2," the system compares/updates only Location 2 Codes.
Code "3" = Location 2 Codes only
If you are scanning by "3," the system compares/updates only Location 3 Codes.
Use these pushbuttons to set the status of each row to "Selected" or "Hold." "Selected" selects a row for processing and "Hold" places the row on hold. You can process only "Selected" rows if you select the Exceptions table as the input file source when you run the process from the Asset Location Preprocessor screen.
The FA Location Exceptions (FA_LOC_EXCEPTNS) table stores scanned asset and location data that is invalid when compared to asset and location data in the Asset Master record. For example, if a room number scanned for an asset has been misprinted on a bar code label and has not been subsequently set up as a location code, the scanned data cannot be validated and will therefore be written to the Asset Location Exceptions table. In this event, you can manually correct the invalid data, as desired, in this screen (the Maintain Asset Location Exceptions screen) and then run the Asset Location Preprocessor again using the Exceptions Table as the input file.
Validations access the following tables:
Asset/item number validations are performed against the ASSET (Asset) table.
Tag numbers are associated with asset/item numbers via the ASSET (Asset) table.
Location labels are read from the FA_LABELS (Fixed Assets Labels) table.
Location group code validations are performed against the FA_LOCATION_GRP (Location Group) table.
Location 1, 2, and 3 code data validations are performed against the FA_LOCATION (Location) table.