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

...