Below is a list of the more common error messages you may see in the import logs. This is not an exhaustive list of all possible messages, but addresses the most common ones, provides an explanation of what they mean and gives the user additional context on how to determine if further action is required. Each Error shows the line number associated with the record in the corresponding import file. The line number can be helpful in locating the record. Some of the errors may require clean up to be made in Classic prior to extract so it's imperative to do a test import of the inventory data in order to review possible import errors and clean them up in Classic prior to the final production import.
Dispositions
- DispositionImportImpl: error: Disposition Import Error - row xxxx: Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while committing the transaction
- Missing Disposition Method: The entire disposition transaction will not import if there is a missing disposition method.
- Fix in Classic: Please review the tag in EISSCN>DSPTRN and update it by adding a disposition method to allow the disposition transaction to import.
- Missing Disposition Method: The entire disposition transaction will not import if there is a missing disposition method.
Items:
- InventoryItemImportImpl: error: Duplicate Tag Number found on row: xxxx
- Duplicate tag on file: This could be possible if one of the tag numbers includes a blank space as part of the number.
The one with the blank space will import first thus resulting in the duplicate number to not import.- Fix in Classic: If it is a true duplicate, the district needs to delete the duplicate tag in EISSCN>ITMSCN. If it's not a duplicate, they need to change the tag number with the blank space in EISSCN>ITMSCN in order to allow both tags to import.
- Duplicate tag on file: This could be possible if one of the tag numbers includes a blank space as part of the number.
Locations
- LocationCodeImportImpl: error: Location Code Import Error - row xxxx: Invalid Category or Number - No blank values allowed
- Missing part of the location: The location code is made up of a location category and a location number. The location will not import if the location category or the location number is missing. Any item records that contain the partial location will import without the location (thus leaving the location field blank on the item).
- Fix in Classic: You may use EISCHG>Mass Change Location Codes to mass change all items that contain the partial location code to a valid, complete location code. When doing so, all items will be updated with the valid code and if the location is a new code, the location will be automatically added to EISMNT>LOCSCN.
- Fix in Redesign: After final import, you may use System>Import's Item Import type creating a spreadsheet to mass change items with partial location codes to a valid, complete location codes. If a location code is a new one, you will need to manually add the code in Codes>Locations as well.
- Missing part of the location: The location code is made up of a location category and a location number. The location will not import if the location category or the location number is missing. Any item records that contain the partial location will import without the location (thus leaving the location field blank on the item).
Transfers
- TransferImportImpl: error: Transfer Import Error - row 2: Item for tag #Tag could not be found.
- Ignore Error: Transfer Header Row Column: Row 2 of the Transfer data extract contains header row information. It's trying to look for Transfer data in Row 2 and generates an error. Please ignore.