Below is a list of the more common warning and 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.  

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

• Acquisition Import Error - tag #xxxxxx, row xxxx: Date '06010019' is not in year range 1753-9999

  • This error indicates the date on the acquisition record is invalid date and the acquisition record will not import.  The acquisition date must be fixed in classic in order for the acquisition to import.  Please create a support ticket to SSDT on how to fix invalid acquisition dates on the acquisition record.

• CategoryCodeImportImpl:  error: Category Code Import Error - row 2: Index 1 out of bounds for length 1

  • This error usually indicates the extract files does not contain any category code records.  Please review their Classic EISMNT>CATSCN to confirm there are no item category codes on file.  If that's the case, please ignore this error.

  • If there are category codes in Classic (and on the extract file), on the inventory import results file, find the number of 'records loaded'.  Next, review the migrated category codes via Core>Categories to confirm the same number were loaded and compare back to the Classic category codes (EISMNT>CATSCN) to confirm all category codes migrated. 

    • If you can confirm all Classic category codes migrated to Inventory, please ignore this error.  The 'out of bounds' error may be due to a blank where the importer thinks there should have been a code.

    • IF a category code did not import, please add it manually via Core>Category Codes.

• ConditionCodeImportImpl:  error: Condition Code Import Error - row 3: Index 5 out of bounds for length 4

• ConditionCodeImportImpl:  error: Condition Code Import Error - row 4: Index 2 out of bounds for length 2

  • This error may indicate the extract files does not contain any condition code records.  Please review their Classic EISMNT>CNDSCN to confirm there are no condition codes on file in Classic.  If that's the case, please ignore this error. 

  • If there are condition codes in Classic, on the inventory import results file, please review how many condition codes loaded. Next, review the condition codes in Core>Conditions to confirm the same number were loaded and compare back to the Classic condition codes (EISMNT>CNDSCN) to confirm all condition codes migrated. 

    • If you can confirm all Classic condition codes migrated to Inventory, the 'out of bounds' error may be due to a blank where the importer thinks there should be a code.  If all condition codes migrated, please ignore this error.

    • If a condition code did not import, please add it manually via Core>Condition Codes.

• DispositionCodeImportImpl:  error: Disposition Code Import Error - row 2: Index 2 out of bounds for length 1

  • This error may indicate the extract files does not contain any disposition code records.  Please review their Classic EISMNT>DSPSCN to confirm there are no disposition codes on file.  If that's the case, please ignore this error.

  • If there are disposition codes in Classic (and on the extract file), on the inventory import results file, find the number of 'records loaded'.  Next, review the migrated disposition codes via Core>Dispositions to confirm the same number were loaded and compare back to the Classic disposition codes (EISMNT>DSPSCN) to confirm all disposition codes migrated. 

    • If you can confirm all Classic disposition codes migrated to Inventory, please ignore this error.  The 'out of bounds' error may be due to a blank where the importer thinks there should have been a code.

    • If a disposition code did not import, please add it manually via Core>Disposition Codes.

• DispositionImportImpl: Warning: Invalid Disposition Code: for Item #: xxxxxx

  • Missing Disposition Method: The disposition transaction will import with the missing or invalid disposition method.  If you want to update the disposition method, you may fix it in Classic prior to extract or wait until the data has been migrated to fix it in Redesign using one of the steps provided below. 

    • Fix in Classic: Please review the tag in EISSCN>DSPTRN and update it by adding a disposition method. 

    • Fix in Redesign

      • Using Transactions>Disposition, edit the disposition correcting the missing/invalid disposition method. 

      • If you have several dispositions with missing disposition methods, 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.  

• DispositionImportImpl:  error: Disposition Import Error - tag #, row 2: Index 1 out of bounds for length 1
  
  

  • This error usually indicates the extract files does not contain disposition transactions.  Please review their Classic EISSCN>DSPTRN to confirm there are no disposition transactions on file.  If that's the case, please ignore this error.

• FunctionCodeImportImpl:  error: Function Code Import Error - row xx: Index 3 out of bounds for length 1
  
  

  • If there are function codes in Classic (and on the extract file), on the inventory import results file, find the number of 'records loaded'. Next, review the migrated function codes via Core>Functions to confirm the same number were loaded and compare back to the Classic function codes (EISMNT>FNCSCN) to confirm all function codes migrated. 

    • If you can confirm all Classic function codes migrated to Inventory, please ignore this error.  The 'out of bounds' error may be due to a blank where the importer thinks there should have been a code.

    • If a function code did not import, please add it manually via Core>Functions.

• FundImportImpl:  error: Fund Import Error - row x: Index 3 out of bounds for length 1
  
  

  • If there are fund codes in Classic (and on the extract file), on the inventory import results file, find the number of 'records loaded'. Next, review the migrated fund codes via Core>Funds to confirm the same number were loaded and compare back to the Classic fund codes (EISMNT>FNDSCN) to confirm all fund codes migrated. 

    • If you can confirm all Classic fund codes migrated to Inventory, please ignore this error.  The 'out of bounds' error may be due to a blank where the importer thinks there should have been a code.

    • If a fund code did not import, please add it manually via Core>Funds

• 17:29:46.193 ERROR [ main] o.h.engine.jdbc.spi.SqlExceptionHelper   ERROR: duplicate key value violates unique constraint "uk_inventoryitem_tagnumber" Detail: Key (tagnumber)=(11202) already exists.

  17:29:46.195 ERROR [  main] o.h.i.ExceptionMapperStandardImpl        HHH000346: Error during managed flush [org.hibernate.exception.ConstraintViolationException: could not execute statement]

  • Duplicate tag on file: This could be possible if one of the tag numbers includes a blank space as part of the number.

    Open

    

      The one with the blank space will import first (the importer drops the space) 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.

• InventoryItemImportImpl: Warning: Capitalized Item #: xxxxxxx has no fund (function or asset class).

  • Regardless of the status (active, etc.) of the item, if the fund, function or asset class is blank on the item record or if the fund, function or asset class is not listed as a valid code in EISMNT in Classic, a warning will be generated.  The item will migrate over but the fund, function or asset class will be blank on the item record.  If you want to update the fund/function/asset class for active items, you may fix it in Classic prior to extract or wait until the data has been migrated to fix it in Redesign using one of the steps provided below

    • Fix in Classic: The offending tag numbers are listed on the import log. 

      • If the fund, function or asset class is blank on an active tag in EISSCN>ITMSCN, create TRNTRNs to assign a valid fund, function and/or asset class. 

      • If the fund, function or asset class is on an active tag in EISSCN>ITMSCN but the code is not listed in EISMNT's FNDSCN (fund), FNCSCN (function) or CLASSCN (asset class), please add the missing codes to its respective program in EISMNT.

    • Fix in Redesign:

      • Using Transactions>Transfers, for active items, create a transfer transaction to change the blank fund, function or asset class to a valid fund, function or asset class.  The associated item's fund, function or asset class will be automatically updated as well to reflect the new value.

      • If you have several active items with an empty fund, function or asset class, you may use the Transaction>Items grid to extract the desired items into an EXCEL spreadsheet. Enter missing fund, function or asset class and save the spreadsheet in CSV format.  Use System>Import's Item Import Type ensuring 'update records' is checked and 'create Transfers' is checked.  The missing fund/function/asset class will be updated on the item record and a transfer transaction will be created with the new value.  Please refer to the System>Import chapter for more information on required fields and formatting of the spreadsheet.

• 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.   If the date is blank or invalid (i.e. 00/2008, 01-APR, etc.), the item will migrate over but the beginning depreciation date will be blank in redesign.  If you want to update the invalid beginning depreciation date, you may fix it in Classic prior to extract or wait until the data has been migrated to fix it in Redesign using one of the steps provided below  

    • 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 Transactions>Items, query the specific tag number and click edit to enter a valid beginning depreciation date and save your changes.

      • If you have several active items with an invalid or blank beginning depreciation date, 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.  Please refer to the System>Import chapter for more information on required fields and formatting of the spreadsheet.