Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP forum
Answered

error exist in batch

Posted on by 55

I posted a batch and it shows error exist in batch

the documents have been posted and are in open status 

i recovered the batch and it show this one transactiobut when i click on transaction noting shows up and when i post again it show like this

0755.Untitled.png

and when printing the file it shows 

this transaction has been posted.

this transaction  contains errors. It won't be posted.

Any help?

  • Verified answer
    Hokuminaria Profile Picture
    Hokuminaria 2,950 on at
    RE: error exist in batch

    Hello ICH BIN ICH,

    I am Brandon from the Dynamics GP support team and will address your question below.

    With the message on the Edit List stating that the transaction has already been posted, tells us that there is a duplicate between the work and open tables.

    As I cannot seethe complete batch window, I am unable to determine what module this is for. My assumption is this is an RM or a PM Batch based on what I can see.

    For this issue, we first wan to verify where all the records sit and verify the PM00400 (Keys) Records reflect where the transaction sits.

    Once we determine this and verify the GL was update (Bank Rec as well if this is a check) you can determine how to correct this. Likely, the work record needs to be removed as this has already been posted.

    How to determine this.

    In the Keys Table, check the DCSTATUS.

    1. RM00401 (Receivables Key)

    2. PM00400 (Payables Keys)

    DCSTATUS

    1 = Work

    2= Open

    3= History.

    Then you can verify what tables the Transaction Record sits in.

    PM

    PM10000 = Transaction work.

    PM10300 = Computer Checks Work.

    PM10400 = Manual Checks work

    PM20000 = Transaction Open.

    PM30200 = Transaction History.

    RM

    RM10201 = Cash Receipt Work.

    RM10301 = Transaction Work.

    RM20101 = Transaction Open.

    RM30101 = Transaction History.

    Once you verify where this sits and if the GL is updated, you can remove the record that should not be there. Lastly, delete the batch from SQL and verify the issue is resolved.

    This information is provided to you as is: I highly recommended any testing be done in a test company with a copy of live to verify the end results.

    If you would like us to take a look at the data and provide steps to correct the issue, please create a support case.

    Thank you!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,552 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,552 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Product updates

Dynamics 365 release plans