...

• 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
• Acquisition Import Error - tag #xxxxxx, row 2: Index 1 out of bounds for length 1xxxx: Date '06010019' is not in year range 1753-9999
  • This error usually indicates the extract files does not contain 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.

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.
  • If there are category codes in Classic (and on the extract file), on the inventory import results file, find the number of 'records loaded'. Review   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.

Condition Codes (EIS_IRN#_LOCAT_EXP.TXT)

• 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. Review Next, review the condition codes via 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
    • please ignore this error.
    • If a condition code did not import, please add it manually via Core>Condition Codes.

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 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'. Review   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.

Dispositions (EIS_IRN#_DISP_EXP.TXT)

...

• 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'. Review Next, review the migrated disposition 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.

Fund Codes (EIS_IRN#_FUND_EXP.TXT)

• 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'. Review Next, review the migrated disposition 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
    code.
    • fund code did not import, please add it manually via Core>Funds

Items (EIS_IRN#_ITEMS_EXP.TXT)

...

• 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

        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.

        Note
        NOTE: The import option is not currently available to update items blank fund/function/asset class fields to a value. Jira Issue INV-448 is set to address this on an upcoming release.

        
        

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

        Note

        Invalid beginning depreciation dates (i.e. 00/2019) may cause balancing issues on the YTD (aka FTD) Depreciation amounts when comparing the EIS104 vs. Schedule of Change in Depreciation and/or EIS305 vs Book Value and/or EIS102 vs Fixed Asset by Function/Class if items for active items containing a straight-line method that have not been fully depreciated and contain an invalid beginning depreciation date.  The recommended way to fix this is in Classic.  Please create a ticket to SSDT for assistancerefer to the Life-To-Date Depreciation Discrepancies documentation for further details.

        
        

• InventoryItemImportImpl:  error: Inventory Item Import Error - tag #xxxxxx, row xxx: Index 7 out of bounds for length 7
  • This error may indicate it encountered an invalid character in the item extract.  Examples could include accent mark or special character. .  It's likely the import stopped at this line and did not continue importing the remaining items.  You can confirm by comparing the 'records loaded' on the import log to the number of lines on the extract file.  If there are substantially more lines on the extract file, than what was loaded, the items import did not complete.  
    
    • Fix in Classic: The offending tag numbers are listed on the import log.  Access the tag in EISSCN>ITEMSCN and remove the invalid character.

...

• • 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
  • On the inventory import results file, please review how many location codes loaded. Review Next, review the location codes via Core>Locations to confirm the same number were loaded and compare back to the Classic location codes to confirm all location codes migrated.  If you can confirm all Classic location codes migrated to Inventory, the 'out of bounds' error may be due to a blank where the importer thinks there should be a location code.  If all location codes migrated, please ignore this error.all location codes migrated. 
    • If you can confirm all Classic location codes migrated to Inventory, the 'out of bounds' error may be due to a blank where the importer thinks there should be a location code.  If all location codes migrated, please ignore this error.
    • If you have some location codes that did not import, you may enter them manually via Core>Location Codes.  If you several, you may also create a spreadsheet and import them via System>Import's Location Code import type.  Please refer to the Import documentation for further details as well as a template location code spreadsheet.

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. 
  • If there are organization codes in Classic, on the inventory import results file, please review how many organization codes loaded. Review the find the number of 'records loaded'. Next, review the migrated organization codes via Core>Organization to confirm the same number were loaded and compare back to the Classic organization codes (EISMNT>ORGSCN) to confirm all organization codes migrated. 
    • If you can confirm all Classic organization codes migrated to Inventory, please ignore the error.  The 'out of bounds' error may be due to a blank where the importer thinks there should
    be
    • have been a code. 
    • If
    all organization codes migrated, please ignore this error.
    • a organization code did not import, please add it manually via Core>Organization Codes

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