Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 33 Next »

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.  

Acquisitions (EIS_IRN#_ACQ_EXP.TXT)

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

Category Codes (EIS_IRN#_ITMCT_EXP.TXT)

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

Disposition Codes (EIS_IRN#_DSPCD_EXP.TXT)

  • DispositionCodeImportImpl:  error: Disposition Code Import Error - row 2: Index 2 out of bounds for length 1
    • This error usually indicates 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.


Dispositions (EIS_IRN#_DISP_EXP.TXT)

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

Items (EIS_IRN#_ITEMS_EXP.TXT)

  • 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.   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, a warning will be generated but the item will migrate over with the missing code.  If you want to update the fund/function/asset class, 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.  Create TRNTRNs to assign the missing fund, function and/or asset class.
      • Fix in Redesign:
        • Using Transactions>Transfers, 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 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 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.
    • NOTE: Invalid beginning depreciation dates (i.e. 00/22) may cause balancing issues on the YTD Depreciation amounts when comparing the EIS104 vs. Schedule of Change in Depreciation and/or EIS305 vs Book Value.


  • 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 org.ssdt_ohio.usas.inventory.model.AssetClass, messageTemplate='Code must be max 4 characters long.'}
  • InventoryItemImportImpl: error: Inventory Item Import Error - tag #, row #
    • These type of errors could be due to a wrapping issue on the ITEMS_EXP.TXT extract file caused by a hidden tab/space issue.  Please review the extract file in NOTEPAD++ to determine if each item is displayed on its on row starting at the left margin.  If you see wrapping similar to (snippet below), it's a very good indication there are hidden spaces/tabs in the data causing the formatting to wrap and resulting in the error messages above.  In the screenshot example, tags #001657, #001658 & #001659 are in the correct format.  The row below it, you no longer see tags numbers line up to the left after that (red area).  The next tag #001660 should be listed at the left margin of row 1601.  Instead, it's still on row 1600 due to a possible hidden/tab space issue.  Please create a helpdesk ticket to SSDT attaching both the inventory import results file as well as the items extract file.

Locations (EIS_IRN#_LOCAT_EXP.TXT)

  • LocationCodeImportImpl: 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 import in Core>Locations and any items containing the partial location will import as is in Transactions>Items. If you want to update the location codes, 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: 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:  Using the Transaction>Items grid, extract the desired items with partial locations into an EXCEL spreadsheet.  Add the correct location_category 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.  
  • 16:10:47.433 ERROR [  main] o.h.engine.jdbc.spi.SqlExceptionHelper   ERROR: duplicate key value violates unique constraint "uk_locationcode_number" Detail: Key (number, category)=(1, 201) already exists.

Error: LocationCodeImportImpl:  error: Location Code Import Error - row 77: could not execute statement; SQL [n/a]; constraint [uk_locationcode_number]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement

    • Duplicate location on file: This could be possible if the location category or location number includes a blank space.   The one with the blank space will import first (the importer drops the space) thus resulting in the duplicate location to not import.
      • Fix in Classic: If it is a true duplicate, the district can delete the duplicate location in EISMNT>LOCSCN.  
  • LocationCodeImportImpl:  error: Location Code Import Error - row 4: Index 2 out of bounds for length 2

Organization Codes (EIS_IRN#_LOCAT_EXP.TXT)

  • OrganizationCodeImportImpl:  error: Organization Code Import Error - row 4: Index 2 out of bounds for length 2
    • This error usually indicates the extract files does not contain any organization code records.  Please review their Classic EISMNT>ORGSCN to confirm there are no organization codes on file in Classic.  If that's the case, please ignore this error.

Transfers (EIS_IRN#_TRANS_EXP.TXT)

  • 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.
  • Transfer Import Error: tag #xxxx, row xxxx: Item for tag #xxxx could not be found.  
    • The associated item record is not on file thereby not allowing any associated transfer transaction records to be imported.  Please review the import log to see if there is an 'inventory item import error' for the related tag #.   


  • No labels