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.  

Acquisitions

• Acquisition Import Error - tag #xxxxxx, row xxxx: Inventory Item Not found for tag #xxxxxx
  • The associated item record is not on file thereby not allowing the associated acquisition record to be imported.  Please review the import log to see if there is an 'inventory item import error' for the related tag #. 

Dispositions

• Disposition Import Error - row xxxxDispositionImportImpl: Warning: Invalid Disposition Code: for Tag# Item #: xxxxxx
  • Missing Disposition Method: The entire disposition transaction will not import if there is a missing import with the missing or invalid 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. 
    • Fix in Redesign: Using the Transaction>Dispositions grid, extract the desired dispositions into an EXCEL spreadsheet.  Add the correct disposition code and save the spreadsheet in CSV format. Use System>Import's Dispositions Import type ensuring 'update records' is checked and import the updated disposition transactions.  If the disposition code is new and not currently in Core>Dispositions, it will be automatically added when the spreadsheet is imported and the new disposition also noted on the import results report.  

Items:

• Inventory Item Import 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.
  Inventory Item Import Error: Tag#xxxxxx, Row xxxx Beginning Depreciation Date must be in MMYYYY formatAn item's Beginning Depreciation Date must be

• InventoryItemImportImpl: Warning: Capitalized Item #: xxxxxxx has no fund (function or asset class).
  • Regardless of the status of the item, if the fund, function or asset class is blank, a warning will be generated but the item will migrate over with the missing code.

• InventoryItemImportImpl: Warning: Item #: xxxxxx has a depreciation method of: Straight_Line with an invalid date: 000000
  
  • If an item is marked for depreciation, the beginning depreciation date must be in a valid MMYYYY format in Classic's ITMSCN containing a valid date.   If the date is blank or invalid (i.e. 00/2008, 01-APR, etc), the item will not migrate over (regardless of but the depreciation method).  This may affect Depreciation/Book amounts causing balancing issues between the EIS104/EIS305 reports and their Redesign counterpart reportsbeginning depreciation date will be blank in redesign.
    • Fix in Classic: The offending tag numbers are listed on the import log.  Access the tag in EISSCN>ITMSCN and modify the Beginning Date field under 'Depreciation Information' with the correct MMYYYY format.  . 
    • Fix in Redesign: Using the Transaction>Items grid, extract the desired items into an EXCEL spreadsheet. Enter valid beginning depreciation dates and save the spreadsheet in CSV format.  Use System>Import's Item Import Type ensuring 'update records' is checked and import the updated beginning depreciation dates for those existing items. 

• Inventory Item Import Error: ERROR [main] o.h.i.ExceptionMapperStandardImpl HHH000346: Error during managed flush [Validation failed for classes [org.ssdt_ohio.usas.inventory.model.AssetClass] during persist time for groups [javax.validation.groups.Default,]List of constraint violations:[ConstraintViolationImpl{interpolatedMessage='Code must be max 4 characters long.', propertyPath=code, rootBeanClass=class
  • This could be due to a wrapping issue on the ITEMS_EXP.TXT extract file caused by a hidden tab/space issue.  Please create a helpdesk ticket to SSDT for further assistance.

Locations

• Location Code Import Error - row xxxx: Invalid Category or Number - No blank values allowedLocationCodeImportImpl: Warning: Location Number: CUMC has a blank category.
• LocationCodeImportImpl: Warning: Location Category: 001 has a blank number.
  
  • Missing part of the location:  The location code is made up of a location category and a location number.  The partial location will not import in Core>Locations if a location's category or number is missing. Any item records that and any item contain the partial location will import in Transactions>Items however the location will be blank on the item.  Any partial location codes that do not have associated item records may be ignored. As indicated above, those partial codes will not import into Core>Locations.
  • 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: If you choose not to fix in Classic before final import, you can fix in Redesign after final import.  Using the Transaction>Items grid, extract the desired items with blank partial locations into an EXCEL spreadsheet.  Add the correct location_category and or location_number and save the spreadsheet in CSV format. Use System>Import's Item Import type ensuring 'update records' is checked and import the updated locations.  If the location code is new and not currently in Core>Location, it will be automatically added when the spreadsheet is imported and the new location also noted on the import results report.  

...