...
- Inventory Item Import Error: Tag#xxxxxx, Row xxxx Beginning Depreciation Date must be in MMYYYY format
- An item's Beginning Depreciation Date must be MMYYYY format in Classic's ITMSCN containing a valid date. If the date is not valid (i.e. 00/2008, 01-APR, etc), the date item will not migrate correctly and will over (regardless of the depreciation method). This may affect Depreciation/Book amounts causing balancing issues between the EIS104/EIS305 reports and their Redesign counterpart reports.
- 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. If you have several items with invalid dates
- An item's Beginning Depreciation Date must be MMYYYY format in Classic's ITMSCN containing a valid date. If the date is not valid (i.e. 00/2008, 01-APR, etc), the date item will not migrate correctly and will over (regardless of the depreciation method). This may affect Depreciation/Book amounts causing balancing issues between the EIS104/EIS305 reports and their Redesign counterpart reports.
- 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
- This could be due to a wrapping issue on the ITEMS_EXP.TXT extract file caused by a hidden tab/space issue. Please create a helpdesk ticket to SSDT for further assistance.
Locations
- Location Code Import Error - row xxxx: Invalid Category or Number - No blank values allowed
- Missing part of the location: The location code is made up of a location category and a location number. The location will not import in Core>Locations if a location's category or number is missing. Any item records that contain the partial location will import in Transactions>Items without however the location (thus leaving the location field will be blank on the item). Any partial location codes that do not have an associated item record records may be ignored. As indicated above, those partial codes will not import into Core>Locations.
- 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: After If you choose not to fix in Classic before final import, you may use can fix in Redesign after final import. Using the Transaction>Items grid, extract the desired items with blank locations into an EXCEL spreadsheet. Add the correct location_category and location_number and save the spreadsheet in CSV format. Use System>Import's Item Import type creating a spreadsheet to mass change items with partial location codes to a valid, complete location codes ensuring 'update records' is checked and import the updated locations. If a the location code is a new one, you will need to manually add the code in Codes>Locations as well.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.
Transfers
- 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.
...