Integration Manager Pulling in Data from a Duplicate Batch

(0) Share

Report

Posted on by Community Member

Hello:

This GP 2015 R2 end user ran a journal entry import through Integration Manager. The integration prompted the end user to enter a Batch ID.

She entered a Batch ID that was the same ID as one previously posted.

That previously posted Batch ID was from 12/31/2017, and this "new" Batch ID was dated 04/28/2018.

She says, therefore, that Integration Manager pulled data from a previously posted batch into a new batch, all because both batches have the same Batch ID.

Is that possible? Or, is it more likely that the other batch ID was in fact not posted and Integration Manager simply imported into a batch already out there?

Thanks!

John

*This post is locked for comments

All responses (2)

Answers (0)

Suggested answer

L Vail 65,271 on at

Like (0)

Report

RE: Integration Manager Pulling in Data from a Duplicate Batch

John,

If the batch was, in fact, not posted it would behave as you've described. I've never experienced a case where the batch ID picked up a date from a previously posted batch. Where would it get the Batch date? I don't think the GL Batch ID is stored anywhere.

Kind regards,

Leslie
Heather Roggeveen 9,144 on at

Like (0)

Report

RE: Integration Manager Pulling in Data from a Duplicate Batch

What makes the user say that that is the case? Is there a report she is running that shows it? You can do queries via e.g. SmartList by batch ID. If you did that, it would show both lots of transactions, but that doesn't mean it came in twice - just that the batch id was the same.