When addresses and contacts are created during the conversion, Service/Support End User Detail (eud_det) records with a Name (eud_sort) field exceeding 24 characters are truncated.

This file contains a log of truncated records.

This file contains a log of AP Invoices which contained some invalid data, but were processed during the conversion. Examples of such invalid data are AP invoices in which the company, currency, or daybook information was invalid or referenced a nonexistent record. The AP Invoice record is still fully converted, but post-conversion action could be required.

This file contains a log of AP Payments which contained invalid data, but were processed during the conversion. Examples of such invalid data would be AP payments in which the company, currency, or supplier information was invalid or referenced a nonexistent record. The AP Payment record is still fully converted, but post-conversion action could be required.

This file contains a log of any AR Invoices which contained some invalid data, but were processed during the conversion. Examples of such invalid data would be AR invoices in which the company, currency, or daybook information was invalid or referenced a nonexistent record. The AR Invoice record is still fully converted, but post-conversion action could be required.

This file contains a log of AR payments which contained some invalid data, but were processed during the conversion. Examples of such invalid data are any AR payments in which the company, customer, or daybook information is invalid or references a nonexistent record. The AR Payment record is still fully converted, but post-conversion action could be required.

This file contains a log of errors encountered when determining the bank format details for a customer or supplier bank. An example of such data is an invalid BankNumber and payment format combination. The record is still fully converted, but post-conversion action could be required.

This file contains a log of any PIP (Payment in Process) accounts that were defined with an incorrect GL account type.

This file contains a log if there are any postings against the control account of a customer, or supplier, but against the mirror of the transaction account.

This file contains a log of any records in which it was necessary to default the bank details for AR transactions. One of two methods can be used to default the values:

1. The bank details associated with ar_bank are used instead of ar_acct. This default is used if ar_acct is not defined as a valid bank.

2. A default bank number based on the customer and customer bank number. This default is used if both ar_acct and ar_bank fail to provide a valid bank.

This file contains a log of any errors encountered when determining the supplier bank details. An example of such invalid data would be blank pay format data for a supplier.

This file contains a log of any invalid data encountered when converting GL History (gltr_hist) records. Examples of such invalid data are an invalid GL Entity (gltr_hist.gltr_entity) or GL Account (gltr_acct).

This file contains details of any additional posting that the conversion had to make to ensure a GL Transaction Posting balances. This log entry provides traceability for these newly created records.

During the pre-conversion process, you might need to specify replacement Payment in Process (PIP) accounts and replacement Drafts Payable accounts within the GL Account Type Utility. The system prompts you for these accounts when bank records exist that contain the same Domain code (where applicable), Entity code, and Cash account, but where the PIP accounts or Drafts Payable accounts differ. The account entered is used going forward.

Therefore, any transactions that were posted against the original PIP or Drafts Payable account are converted using the replacement account. This log file contains a record of such transactions where the PIP or Drafts Payable account were replaced with the new PIP or Drafts Payable account.