Page Comparison

...

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

• 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 Image Addedor special character. Image Added.  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.

• 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 error: Inventory Item Import Error - tag ##xxxxxx, row # xxx:
  • 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 and could involve several tags.  Please review the extract file in NOTEPAD++ to determine if each item is on its own line, lined up at the left margin.  If you see wrapping similar to snippet below (Lines 5-7), 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 snippet below, tags #000001 and #000002 are lined up corectly.  Starting with line 5, you no longer see tag numbers line up at the left. The next tag #000003 should be listed at the left margin of line 5.  Instead, that tag is near the end of line 4 due to a possible hidden/tab space issue. 

...