Versions Compared

Version Old Version 18 New Version 19
Changes made by

Michelle Drewes

Michelle Drewes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.  


Note

With INV-240 to be released with version 1.7 of Inventory, we are improving the importer by changing some errors to warnings, which will allow the following data to migrate:

  • Invalid beginning depreciation dates: Items with invalid beginning depreciation will import into Tranactions>Items however the beginning depreciation will be blank
  • Partial Location Codes:  Allow partial location codes to import into Core>Locations and Transaction>Items. Any partial location codes on an item that do not currently exist in Core>Locations, will be automatically added to Core>Locations
  • Missing disposition method on disposition transactions:  Disposition transactions without a method will import into Transactions>Dispositions.

Districts may then clean up their existing data after migration using System>Import to update blank beginning depreciation dates, partial locations on Items and missing deposition methods on Disposition transaction. 


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 #. 

...

  • Inventory Item Import Error: Tag#xxxxxx, Row xxxx Beginning Depreciation Date must be in MMYYYY format
    • An item's Beginning Depreciation Date must be MMYYYY format in Classic's ITMSCN containing a valid date.   If the date is not valid invalid (i.e. 00/2008, 01-APR, etc), the item will not migrate over (regardless of the depreciation method).  This may affect Depreciation/Book amounts causing balancing issues between the EIS104/EIS305 reports and their Redesign counterpart reports.
      • 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.  If you have several items with invalid dates  


  • 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.

...