...

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

...

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 24: Index 2 out of bounds for length 12
  • This error usually indicates the extract files does not contain any disposition condition code records.  Please review their Classic EISMNT>DSPSCN EISMNT>CNDSCN to confirm there are no disposition 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 the condition codes via 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.

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

...

• 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 caseThis 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 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, the 'out of bounds' error may be due to a blank where the importer thinks there should be a code.  If all organization codes migrated, please ignore this error.

...