...

• Requisition header and items:  You may see messages that requisition headers and items were not created because the related purchase order was not found.  When requisitions are converted to POs, and then the PO is deleted, the import will not post the associated requisition.
  
  • Requisition #XXXXXX not created, no related purchase order found.
  • Requisition header not found for XXXXXX

...

• Suspicious Invoices:  We're seeing a lot of partial invoices with invoices dates after full invoices.  This is a problem in the Redesign because it is date driven.  In most cases these invoices will need to be cleaned up so they don't cause problems with carryover encumbrances.
  • Suspicious Invoice# XXXXXXXXX contains full invoice items with date prior to partial invoice item dates
    Image Added

Users

• Users:  You may see a message stating "Unable to find ord.ssdt_ohio.usas.model.user.User with id "some string of characters".  This means that a user record was created during a transaction import (created by user) but when the user import ran that user was not found in the import file.  This user was most likely deleted in Classic but was still referenced via the created by user field on various transactions.