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