Content Comparison

...

• InventoryItemImportImpl: Warning: Capitalized Item #: xxxxxxx has no fund (function or asset class).
  • Regardless of the status (active, etc.) of the item, if the fund, function or asset class is blank, a warning will be generated but the item will migrate over with the missing code.  If you want to update the fund/function/asset class, 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.  Create TRNTRNs to assign the missing fund, function and/or asset class.
    • Fix in Redesign:
      • Using Transactions>Transfers, create a transfer transaction to change the blank fund, function or asset class to a valid fund, function or asset class.  The associated item's fund, function or asset class will be automatically updated as well to reflect the new value.
      • If you have several items with an empty fund, function or asset class, you may use the Transaction>Items grid
      ,
      • to extract the desired items into an EXCEL spreadsheet. Enter missing fund, function or asset class and save the spreadsheet in CSV format.  Use System>Import's Item Import Type ensuring 'update records' is checked and 'create Transfers' is checked.  The missing fund/function/asset class will be updated on the item record and a transfer transaction will be created with the new value.  Please refer to the System>Import chapter for more information on required fields and formatting of the spreadsheet.

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

...