Posted entries are incorrect in the Reversal Entry table (179) when reversing an unapplied payment in the Italian version of Microsoft Dynamics NAV 2009. This issue still occurs after implementing hotfix 2802054. Follow the steps in the code changes section to solve this issue. This problem occurs in the following products:
-
The Italian version of Microsoft Dynamics NAV 2009 R2
-
The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
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 NAV 2009 service pack or the next Microsoft Dynamics NAV 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
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.
Note Before you install this hotfix, verify that all Microsoft Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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.
We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
-
The Modify permission for the object that you will be changing.
-
The Execute permission for the System Object ID 5210 object and for the System Object ID 9015
object.
Note You do not have to have rights to the data stores unless you have to perform data repair.
Code changes
Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, follow these steps:
-
Change the code in Global Variables in the Reversal Entry table (179) as follows:
Existing code...
PostApplied@1029 : Boolean;
Text012@1028 : TextConst 'ENU=You cannot reverse register No. %1 because it contains customer or vendor ledger entries that have been posted and applied in the same transaction.\\You must reverse each transaction in register No. %1 separately.;ITA=Impossibile stornare il registro Nr. %1 perch‚ contiene movimenti contabili clienti o fornitori che sono stati registrati e collegati nella stessa transazione.\\Ô necessario stornare separatamente ogni transazione nel registro Nr. %1.';
PROCEDURE ReverseTransaction@8(TransactionNo@1000 : Integer);
...Replacement code
...
PostApplied@1029 : Boolean;
Text012@1028 : TextConst 'ENU=You cannot reverse register No. %1 because it contains customer or vendor ledger entries that have been posted and applied in the same transaction.\\You must reverse each transaction in register No. %1 separately.;ITA=Impossibile stornare il registro Nr. %1 perch‚ contiene movimenti contabili clienti o fornitori che sono stati registrati e collegati nella stessa transazione.\\Ô necessario stornare separatamente ogni transazione nel registro Nr. %1.';
// Add the following line.
Text013@1039 : TextConst 'ENU=You cannot reverse %1 No. %2 because the entry has an associated Realized Gain/Loss entry.';
PROCEDURE ReverseTransaction@8(TransactionNo@1000 : Integer);
... -
Change the code in the InsertReversalEntry function in the Reversal Entry table (179) as follows:
Existing code 1...
DtldCustLedgEntry.SETFILTER(
DtldCustLedgEntry."Entry Type",'<>%1',DtldCustLedgEntry."Entry Type"::"Initial Entry");
// Delete the following lines.
IF DtldCustLedgEntry.FIND('-') THEN BEGIN
IF RevType = RevType::Register THEN
ERROR(Text012,Number);
CLEAR(DtldCustLedgEntry);
DtldCustLedgEntry.SETCURRENTKEY("Cust. Ledger Entry No.");
DtldCustLedgEntry.SETRANGE("Cust. Ledger Entry No.",CustLedgEntry."Entry No.");
DtldCustLedgEntry.SETRANGE(Unapplied,TRUE);
IF DtldCustLedgEntry.FIND('-') THEN BEGIN
REPEAT
TempRevertTransactionNo.Number := DtldCustLedgEntry."Transaction No.";
IF TempRevertTransactionNo.INSERT THEN;
UNTIL DtldCustLedgEntry.NEXT = 0;
END;
END;
// End of the deleted lines.
UNTIL CustLedgEntry.NEXT = 0;
...Replacement code 1
...
DtldCustLedgEntry.SETFILTER(
DtldCustLedgEntry."Entry Type",'<>%1',DtldCustLedgEntry."Entry Type"::"Initial Entry");
// Add the following lines.
IF NOT DtldCustLedgEntry.ISEMPTY THEN
IF RevType = RevType::Register THEN
ERROR(Text012,Number);
CheckDtldCustLedgEntry(CustLedgEntry);
// End of the added lines.
UNTIL CustLedgEntry.NEXT = 0;
...Existing code 2
...
DtldVendLedgEntry.SETFILTER(
DtldVendLedgEntry."Entry Type",'<>%1',DtldVendLedgEntry."Entry Type"::"Initial Entry");
// Delete the following lines.
IF DtldVendLedgEntry.FIND('-') THEN BEGIN
IF RevType = RevType::Register THEN
ERROR(Text012,Number);
CLEAR(DtldVendLedgEntry);
DtldVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.");
DtldVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",VendLedgEntry."Entry No.");
DtldVendLedgEntry.SETRANGE(Unapplied,TRUE);
IF DtldVendLedgEntry.FIND('-') THEN BEGIN
REPEAT
TempRevertTransactionNo.Number := DtldVendLedgEntry."Transaction No.";
IF TempRevertTransactionNo.INSERT THEN;
UNTIL DtldVendLedgEntry.NEXT = 0;
END;
END;
// End of the deleted lines.
UNTIL VendLedgEntry.NEXT = 0;
...Replacement code 2
...
DtldVendLedgEntry.SETFILTER(
DtldVendLedgEntry."Entry Type",'<>%1',DtldVendLedgEntry."Entry Type"::"Initial Entry");
// Add the following lines.
IF NOT DtldVendLedgEntry.ISEMPTY THEN
IF RevType = RevType::Register THEN
ERROR(Text012,Number);
CheckDtldVendLedgEntry(VendLedgEntry);
// End of the added lines.
UNTIL VendLedgEntry.NEXT = 0;
... -
Change the code in the CheckDtldCustLedgEntry function in the Reversal Entry table (179) as follows:
Existing code...
DtldCustLedgEntry@1001 : Record 379;
BEGIN
// Delete the following lines.
DtldCustLedgEntry.SETCURRENTKEY("Cust. Ledger Entry No.");
DtldCustLedgEntry.SETRANGE("Cust. Ledger Entry No.",CustLedgEntry."Entry No.");
IF DtldCustLedgEntry.FIND('-') THEN
REPEAT
IF (DtldCustLedgEntry."Entry Type" <> DtldCustLedgEntry."Entry Type"::"Initial Entry") AND
(NOT DtldCustLedgEntry.Unapplied)
THEN
ERROR(
Text000,CustLedgEntry.TABLECAPTION,CustLedgEntry."Entry No.");
UNTIL DtldCustLedgEntry.NEXT = 0;
// End of the deleted lines.
END;
...Replacement code
...
DtldCustLedgEntry@1001 : Record 379;
BEGIN
// Add the following lines.
DtldCustLedgEntry.SETCURRENTKEY("Cust. Ledger Entry No.","Entry Type");
DtldCustLedgEntry.SETRANGE("Cust. Ledger Entry No.",CustLedgEntry."Entry No.");
DtldCustLedgEntry.SETFILTER("Entry Type",'<>%1',DtldCustLedgEntry."Entry Type"::"Initial Entry");
DtldCustLedgEntry.SETRANGE(Unapplied,FALSE);
IF NOT DtldCustLedgEntry.ISEMPTY THEN
ERROR(Text000,CustLedgEntry.TABLECAPTION,CustLedgEntry."Entry No.");
DtldCustLedgEntry.SETRANGE(Unapplied);
DtldCustLedgEntry.SETFILTER("Entry Type",'%1|%2',
DtldCustLedgEntry."Entry Type"::"Realized Gain",DtldCustLedgEntry."Entry Type"::"Realized Loss");
IF NOT DtldCustLedgEntry.ISEMPTY THEN
ERROR(Text013,CustLedgEntry.TABLECAPTION,CustLedgEntry."Entry No.");
// End of the added lines.
END;
... -
Change the code in the CheckDtldVendLedgEntry function in the Reversal Entry table (179) as follows:
Existing code...
DtldVendLedgEntry@1001 : Record 380;
BEGIN
// Delete the following lines.
DtldVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.");
DtldVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",VendLedgEntry."Entry No.");
IF DtldVendLedgEntry.FIND('-') THEN
REPEAT
IF (DtldVendLedgEntry."Entry Type" <> DtldVendLedgEntry."Entry Type"::"Initial Entry") AND
(NOT DtldVendLedgEntry.Unapplied)
THEN
ERROR(
Text000,VendLedgEntry.TABLECAPTION,VendLedgEntry."Entry No.");
UNTIL DtldVendLedgEntry.NEXT = 0;
// End of the deleted lines.
END;
...Replacement code
...
DtldVendLedgEntry@1001 : Record 380;
BEGIN
// Add the following lines.
DtldVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type");
DtldVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",VendLedgEntry."Entry No.");
DtldVendLedgEntry.SETFILTER("Entry Type",'<>%1',DtldVendLedgEntry."Entry Type"::"Initial Entry");
DtldVendLedgEntry.SETRANGE(Unapplied,FALSE);
IF NOT DtldVendLedgEntry.ISEMPTY THEN
ERROR(Text000,VendLedgEntry.TABLECAPTION,VendLedgEntry."Entry No.");
DtldVendLedgEntry.SETRANGE(Unapplied);
DtldVendLedgEntry.SETFILTER("Entry Type",'%1|%2',
DtldVendLedgEntry."Entry Type"::"Realized Gain",DtldVendLedgEntry."Entry Type"::"Realized Loss");
IF NOT DtldVendLedgEntry.ISEMPTY THEN
ERROR(Text013,VendLedgEntry.TABLECAPTION,VendLedgEntry."Entry No.");
// End of the added lines.
END;
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Italian version of Microsoft Dynamics NAV 2009 R2
-
The Italian version of Microsoft Dynamics NAV 2009 SP1
Removal information
You cannot remove this hotfix.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Usefor other considerations.
