trados = fnDiagnosis Data for customer &V1& that is to be changed in Collections Managementhas been transferred from company code &V2& in Accounts ReceivableAccounting to Collections Management. However, the information to bechanged does not exist in Collections Management. Example The information about the clearing of an invoice arrives in CollectionsManagement before the invoice. System Response As a result of this inconsistency, the posting of data in CollectionsManagement is terminated. Procedure
- If the data is transferred to Collections Management from Accounts
Receivable Accounting by ALE, you have to ensure the order (time basis)of the posting of the IDocs if you use periodic data transfer (deltaprocedure). Determine the IDoc that is to be posted before this IDoc. If you cannot determine the cause quickly, you have to recreate all datafrom Accounts Receivable Accounting to Collections Management bystarting the report FDM_COLL_SEND_ITEMS with the option DataTransfer According to Selection> for all customers in all companycodes affected.
- If Accounts Receivable Accounting and Collections Management are in the
same system, you only need to recreate the data for customer &V1& incompany code &V2& in Accounts Receivable Accounting by starting reportFDM_COLL_SEND_ITEMS with the option Data Transfer According toSelection>. Then run the report again with the option PeriodicData Transfer> to transfer the data for the remaining customers.
|