web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AP Open Payment Journal Post and Transfer never finishes

(0) ShareShare
ReportReport
Posted on by 804

After over six months live we have a AP Open Payment journal with checks printed that will not finish posting. It gets down to 5 seconds left and then seems to recycle through entries it has already been through. The journal validates normally and the checks printed fine.  No error messages.

The journal prints fine without a problem, totals balance.

Any idea of what could be the problem?

Thanks

Konrad

*This post is locked for comments

I have the same question (0)
  • Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Konrad,

    Did you already have a developer looking into this?

    Have you tried using the post and transfer posting option? Does this make any difference?

    Best regards,

    Ludwig

  • Konrad U Profile Picture
    804 on at

    Ludwig,

    Yep, I am the "developer". It was using the post and transfer. Assuming it is near the end with the under 5 seconds remaining, all the transactions look fine and the report and checks were fine.  Tough to diagnose errors without an error to break at. They all have AP CD voucher numbers as well.

    Thanks

    Konrad

  • Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Konrad,

    To be honest, I have not seen or heard something similar before. I also have not found a hotfix or at least a hint on LCS. So you possibly have to get the MS support involved here.

    The only thing I can help you with is a workaround how to create the postings manually outside of the journal that you created to get the transactions posted and settled. Yet, I believe that your finance people have already done that if this happened already some months ago.

    Best regards,

    Ludwig

  • Konrad U Profile Picture
    804 on at

    Ludwig,

    The work around would help if you would be so kind as to supply it. This is the first time it has happened. The processing message shows the voucher numbers counting up and then as it gets near the end they reset and start over again. Maybe be a bad transaction but the validate does not seem to pick up the problem.

    Would be nice to get it posted since it has 230 transactions.

    Thanks!

    Konrad

  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Konrad,

    I assume that your finance people already paid the invoices manually - that is outside of AX - that are pending unposted in the journal. (Please double check that). Otherwise, you would probably be in trouble with your vendors.

    If the invoices are already paid then you just have to create another payment journal where you post the payments made. That is, you debit the vendor and credit a payment account just as you see it in the journal that cannot be posted.

    Doing that will leave an open invoice and unsettled payment transaction in the vendor transactions.

    Now the question is what you plan to do with the open journal and the settlement marks that have been made there.

    If you do not try to post the journal again but just leave it as it is or possibly delete the journal header, then you can remove the settlement marks and settle the payment and invoice transactions in the vendor master settle open transaction form.

    If you are still trying to post the journal, then you can't do the settlement of payments and invoices because posting the journal will automatically do that.

    Hope this helps.

    Best regards,

    Ludwig

  • Verified answer
    Konrad U Profile Picture
    804 on at

    Thanks for the assistance. Finally we have found the problem. The issue was the commit cycle surrounding the update to VendTransOpen.  The commit failed on trying to update the record twice for the same transaction. This failure was not trapped at a high enough level to alert Dynamics and since it was underneath one post cycle for the LedgerJournalTrans record it had the effect of resetting the cursor so the post started all over again.

    The payment with the problem had two credits showing in the settlement marking form with exactly the same information. The extra credit did not exist in the VendTransOpen table.

    The settlements display is driven by the SpecTrans table which had the duplicate record.

    Deleting the extra SpecTrans record stopped the double update and allowed the payment batch to post normally.

  • Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Konrad U,

    Would be great if you could verify the solution you found to let also other community members know in case they run into a similar issue.

    Many thanks,

    Ludwig

  • Konrad U Profile Picture
    804 on at

    Further note this was a problem in AX 2009 in Accounts Receivable in trying to apply checks or cash to invoices noted with the little red hand while posting.  Since some of this code has been shared it probably exists in AX 2012 as well. Try hard enough and you can select something for settlement twice or more!

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Ali Zaidi Profile Picture

Ali Zaidi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans