You cannot reverse a check payment in Bank Management after you reject a check in a payment journal in Microsoft Dynamics AX 2009

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

This article applies to Microsoft Dynamics AX for all regions.

Symptoms

Consider the following scenario in Microsoft Dynamics AX 2009. You create a payment journal for two vendors. Then, you issue two checks. Next, you reject a check in the payment journal and then reissue a new check to the vendor. In this scenario, you cannot reverse the check payment in Bank Management.

Resolution

Hotfix Information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics AX 2009 service pack or the next version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Installation information

Before you install this hotfix, verify that the Microsoft Dynamics AX client users are logged off the system. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

Note We recommend that the user account in the Windows Logins window or in the Database Logins window be a member of the Administrators User group in Microsoft Dynamics AX.

Code changes

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. Always test code fixes in a controlled environment before you apply the fixes to your production computers.

To resolve this problem, change the code in the updateBankCheque method in the LedgerJournalCheckPost class as follows:

Existing code

...
        select firstonly forupdate bankChequeTable
            where bankChequeTable.Voucher   == _oldVoucher &&
                  bankChequeTable.TransDate == _ledgerJournalTrans.TransDate &&
                  bankChequeTable.RecipientAccountNum == _ledgerJournalTrans.AccountNum;
...

Replacement code

...
        select firstonly forupdate bankChequeTable
            where bankChequeTable.Voucher   == _oldVoucher &&
                  bankChequeTable.TransDate == _ledgerJournalTrans.TransDate &&
                  bankChequeTable.RecipientAccountNum == _ledgerJournalTrans.AccountNum &&
                  bankChequeTable.ChequeStatus != ChequeStatus::Rejected;
...

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.