Open Forum

Expand all | Collapse all

Unable to sae to the batch activity table

  • 1.  Unable to sae to the batch activity table

    Posted May 10, 2018 04:51 PM
    We had a user that was trying to post her EFT Remittance and received the error that said
    "Unable to save to the batch activity table.  You will not be able to use this batch"
    After looking into it, the payments were showing on the vendor card as "work"

    I went into the Process Payables Remittance screen with my user id and I was able to post the batch just fine.  We cant see any other issues as of now and everything seemed to process like normal but my question is if it did something behind the scene we should be worried about.

    Katie Pieczynski
    Accounts Receivable Manager
    Champaign IL
    Academy - Online Interactive Learning from Experts

  • 2.  RE: Unable to sae to the batch activity table

    Posted May 10, 2018 05:01 PM
    ​Hi @Katie Pieczynski

    There is not necessarily any reason to worry with just one instance that seems like it was easily recoverable.

    If it happens again or if you see any other warnings or errors like that I would contact your partner.

    These things happen, and often, with no tragic underlying causes.  It's only if it happens regularly that there may be something to worry about.

    Kindest Regards,

    Jo deRuiter
    "That GP Red Head"
    Advanced Credentialed Professional-Dynamics GP
    Member, GPUG GP Credentialing Exam Committee
    Chairman, GPUG Partner Advisory Board
    "......what isn't she up to?"
    Heartland Business Systems, LLC
    Senior Financial Systems Consultant
    Milwaukee, WI
    770-906-4504 (Cell)

    Academy - Online Interactive Learning from Experts

  • 3.  RE: Unable to sae to the batch activity table

    Posted Nov 10, 2020 07:20 PM
    Just to add to Jo's response, when you see this message, take a look at the SY00800 table in Dynamics.  You'll see two records with the same batch, but the WINTYPE on one of them will be "0" (zero), which is not valid.  If the user were to close GP and open it again, that would remove the bad record.  Or, since this is a temp table, you can delete that row, and the user will be able to save the transaction and/or the batch.  See an explanation of the different wintype's in

    Merri Gorrell
    Business Applications Support
    Heska Corporation
    Loveland CO

    Academy - Online Interactive Learning from Experts

If you've found this thread useful, dive deeper into User Group community content by role