Share
Report
20One of my accounting users has been having an issue with recurring batches/transactions for a couple of months now.
Part of this may be a process issue, but I wanted to rule out any thing I can try on the technical or database side.
She uses Integration Manager to bring over cash receipts. As files are loaded, she then sees where the source file is corrupted by the transactions that error out in Dynamics. She then fixes the source file, deletes the batches out of Dynamics and reruns the Integration.
She says she's been doing this for years without any issues. Now, it seems that when she reloads the Integration, all those batches that she thought she deleted show up as "work", but there are no transactions behind them. She can manually delete the batches, but whenever she loads a new batch or manually adds one, Those ghost batches show up again.
I can see all the batches sitting out in the work tables RM10201,etc... If I delete them, and then have her delete the batches from the application one last time, they stay gone.
Our question is, why is this happening just now? Is there something she should or should not be doing in this process. If she continues to import/delete/fix/import, should she be running a check links or reconcile before the second import? Or am I going to have to delete them from SQL before she reimports.
Thanks,
Robin
*This post is locked for comments
All responses (
Answers (
