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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Reverse Transaction Co...
Microsoft Dynamics NAV (Archived)

Reverse Transaction Code changes NAV 2013 R2 CU 16/CU 17

(0) ShareShare
ReportReport
Posted on by Bianca 693

Hello,

following szenario:

Posting a payment with discount amount and applied an invoice in Cronus NAV 2013 R2 CU12 (also in CU16)

Select the posted payment and press “unapply Entries”  (example: Detailed Customer Ledger Entries)

Select the posted payment and press “Reverse Transaction”. After it you get the message that it isn’t allowed.

 reverse.jpg

Error: You cannot reverse Cust. Ledger Entry No. xy because the entry has an associated Payment Discount entry.

reverse2.jpg

This error is solved in CU 17, but in the changes of the version CU17 or in all KB Articles I don’t find information about the changes which are necessary.

Our Customer has the problem in CU12 and we are searching for the necessary Codefix or KB Articles.

Thank you in advance!

Regards,
Bianca

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    As CU17 does not contain such information, better you debug the solution, compare your CU12 relevant Codeunit object with CU 17 and merge the relevant changes.

    https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;3039826

    As we do not see such documentations, this is the best possible way to move forward..

  • Suggested answer
    Jens Glathe Profile Picture
    Jens Glathe 6,092 on at

    Hi Bianca,

    the changes are in CU17 only, with "CU" meaning "Cumulative Update", as far as I can see. The object that contains the "fix" is table 179 "Reversal Entry". The check and insert logic has been refactored in CU17. There are no major changes between CU12 and CU17 for this table, and the refactoring is all local functions for the table. With this refactoring the check against the payment discount detailed entries was removed.

    My suggestion would be to use table 179 and codeunit 17 from the CU17 build of the database. These should fit into a CU12 database without trouble, and you have the matching reversal codeunit  build level for the reversal entries.

    with best regards

    Jens

  • Suggested answer
    Jens Glathe Profile Picture
    Jens Glathe 6,092 on at

    Hi Bianca,

    regarding why is there no documentation for a fix: It probably isn't. The functionality was refactored, and the offending check was simply removed. So... either it was found to be no longer necessary, or it was forgotten and it's a bug now. I didn't check ;-)

    with best regards

    Jens

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans