Payments in cash for redrawn bills should be declared in the year of the original invoice and not based on the year of the redrawn bill in the 347 Declaration in the Spanish version of Microsoft Dynamics NAV 2009. This problem occurs in the following products:
-
The Spanish version of Microsoft Dynamics NAV 2009 R2
-
The Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
Cause
This issue occurs because incorrect date is taken from exporting 347 declaration in case of redrawn bills
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. Before applying the change, please import all SEPA updates.
To resolve this problem, follow these steps:
-
Change the code in the IdentifyCashPayments function in the Make 347 Declaration report (10707) as follows:
Existing code 1...
LOCAL PROCEDURE IdentifyCashPayments@1100010(CustomerNo@1100000 : Code[20];VATRegistrationNo@1100002 : Text[20]);
VAR
CustLedgerEntry@1100001 : Record 21;
BEGIN
// es0020.begin
CustLedgerEntry.SETCURRENTKEY("Document Type","Customer No.","Posting Date","Currency Code");
CustLedgerEntry.SETRANGE("Document Type",CustLedgerEntry."Document Type"::Payment);
...Replacement code 1
...
LOCAL PROCEDURE IdentifyCashPayments@1100010(CustomerNo@1100000 : Code[20];VATRegistrationNo@1100002 : Text[20]);
VAR
CustLedgerEntry@1100001 : Record 21;
// Add the following line.
DocumentPostingDate@1170000000 : Date;
BEGIN
// es0020.begin
CustLedgerEntry.SETCURRENTKEY("Document Type","Customer No.","Posting Date","Currency Code");
CustLedgerEntry.SETRANGE("Document Type",CustLedgerEntry."Document Type"::Payment);
...Existing code 2
...
CustLedgerEntry.SETCURRENTKEY("Document Type","Customer No.","Posting Date","Currency Code");
CustLedgerEntry.SETRANGE("Document Type",CustLedgerEntry."Document Type"::Payment);
CustLedgerEntry.SETRANGE("Customer No.",CustomerNo);
// Delete the following lines.
CustLedgerEntry.SETRANGE("Posting Date",FromDate,ToDate);
IF CustLedgerEntry.FINDSET THEN
REPEAT
IF (CustLedgerEntry."Bal. Account Type" = CustLedgerEntry."Bal. Account Type"::"G/L Account") AND
(CustLedgerEntry."Bal. Account No." <> '')
THEN BEGIN
IF IsCashAccount(CustLedgerEntry."Bal. Account No.") THEN
CreateCashTotals(CustLedgerEntry."Entry No.",VATRegistrationNo);
END ELSE
IF ((CustLedgerEntry."Bal. Account No." = '') OR
(CustLedgerEntry."Bal. Account Type" <> CustLedgerEntry."Bal. Account Type"::"G/L Account"))
THEN BEGIN
IF IdentifyCashPaymentsFromGL(CustLedgerEntry) THEN
CreateCashTotals(CustLedgerEntry."Entry No.",VATRegistrationNo);
END;
// End of the deleted lines.
UNTIL CustLedgerEntry.NEXT = 0;
// es0020.end
END;
...Replacement code 2
...
CustLedgerEntry.SETCURRENTKEY("Document Type","Customer No.","Posting Date","Currency Code");
CustLedgerEntry.SETRANGE("Document Type",CustLedgerEntry."Document Type"::Payment);
CustLedgerEntry.SETRANGE("Customer No.",CustomerNo);
// Add the following lines.
// we need payments made in future.
// CustLedgerEntry.SETRANGE("Posting Date",FromDate,ToDate);
IF CustLedgerEntry.FINDSET THEN
REPEAT
DocumentPostingDate := GetPaymentDocumentPostingDate(CustLedgerEntry);
IF (CheckCashTotalsPossibility(CustLedgerEntry,DocumentPostingDate)) THEN
CreateCashTotals(CustLedgerEntry."Entry No.",VATRegistrationNo,DocumentPostingDate);
// End of the added lines.
UNTIL CustLedgerEntry.NEXT = 0;
// es0020.end
END;
... -
Change the code in the CreateCashTotals function in the Make 347 Declaration report (10707) as follows:
Existing code 1...
UNTIL CustLedgerEntry.NEXT = 0;
// es0020.end
END;
// Delete the following line.
LOCAL PROCEDURE CreateCashTotals@2(CustLedgerEntryNo@1100000 : Integer;VATRegistrationNo@1100001 : Text[20]) : Boolean;
VAR
CustLedgerEntry@1100091 : Record 21;
DtldCustLedgEntry@1100094 : Record 379;
DtldCustLedgEntry2@1100095 : Record 379;
...Replacement code 1
...
UNTIL CustLedgerEntry.NEXT = 0;
// es0020.end
END;
// Add the following line.
LOCAL PROCEDURE CreateCashTotals@2(CustLedgerEntryNo@1100000 : Integer;VATRegistrationNo@1100001 : Text[20];DocumentPostingDate@1170000000 : Date) : Boolean;
VAR
CustLedgerEntry@1100091 : Record 21;
DtldCustLedgEntry@1100094 : Record 379;
DtldCustLedgEntry2@1100095 : Record 379;
...Existing code 2
...
THEN BEGIN
IF CustLedgerEntry.GET(DtldCustLedgEntry2."Cust. Ledger Entry No.") THEN
UpdateCustomerCashBuffer(VATRegistrationNo,
// Delete the following line.
DATE2DMY(CustLedgerEntry."Posting Date",3),-(DtldCustLedgEntry2."Amount (LCY)"));
END;
UNTIL DtldCustLedgEntry2.NEXT = 0;
END ELSE BEGIN
...Replacement code 2
...
THEN BEGIN
IF CustLedgerEntry.GET(DtldCustLedgEntry2."Cust. Ledger Entry No.") THEN
UpdateCustomerCashBuffer(VATRegistrationNo,
// Add the following line.
DATE2DMY(DocumentPostingDate,3),-(DtldCustLedgEntry2."Amount (LCY)"));
END;
UNTIL DtldCustLedgEntry2.NEXT = 0;
END ELSE BEGIN
...Existing code 3
...
END ELSE BEGIN
IF CustLedgerEntry.GET(DtldCustLedgEntry."Applied Cust. Ledger Entry No.") THEN
UpdateCustomerCashBuffer(VATRegistrationNo,
// Delete the following line.
DATE2DMY(CustLedgerEntry."Posting Date",3),DtldCustLedgEntry."Amount (LCY)");
END;
UNTIL DtldCustLedgEntry.NEXT = 0;
// es0020.end
...Replacement code 3
...
END ELSE BEGIN
IF CustLedgerEntry.GET(DtldCustLedgEntry."Applied Cust. Ledger Entry No.") THEN
UpdateCustomerCashBuffer(VATRegistrationNo,
// Add the following line.
DATE2DMY(DocumentPostingDate,3),DtldCustLedgEntry."Amount (LCY)");
END;
UNTIL DtldCustLedgEntry.NEXT = 0;
// es0020.end
... -
Change the code in the GetPaymentDocumentPostingDate function in the Make 347 Declaration report (10707) as follows:
Existing code...
IF Vendor."Country/Region Code" = CountryCode THEN
FromJournal := TRUE;
END;
...Replacement code
...
IF Vendor."Country/Region Code" = CountryCode THEN
FromJournal := TRUE;
END;
// Add the following lines.
LOCAL PROCEDURE GetPaymentDocumentPostingDate@1170000000(CustLedgerEntry@1170000000 : Record 21) PostingDate : Date;
VAR
CustLedgerEntryRelated@1170000001 : Record 21;
BEGIN
WITH CustLedgerEntry DO BEGIN;
TESTFIELD("Document Type","Document Type"::Payment);
PostingDate := "Posting Date";
END;
// If payment for Bill then we need get Posting Date of the Document related to the Bill
WITH CustLedgerEntryRelated DO BEGIN
SETRANGE("Closed by Entry No.",CustLedgerEntry."Entry No.");
SETRANGE("Document Type","Document Type"::Bill);
IF FINDFIRST THEN BEGIN
RESET;
SETRANGE("Document No.","Document No.");
SETFILTER("Document Type",'%1|%2',"Document Type"::Invoice,"Document Type"::"Credit Memo");
FINDFIRST;
PostingDate := "Posting Date";
END
END;
EXIT(PostingDate);
END;
PROCEDURE CheckCashTotalsPossibility@1170000008(CustLedgerEntry@1170000000 : Record 21;DocumentPostingDate@1170000001 : Date) : Boolean;
BEGIN
IF (DocumentPostingDate < FromDate) OR (DocumentPostingDate > ToDate) THEN
EXIT(FALSE);
WITH CustLedgerEntry DO
IF ("Bal. Account Type" = "Bal. Account Type"::"G/L Account") AND ("Bal. Account No." <> '') THEN BEGIN
IF IsCashAccount("Bal. Account No.") THEN
EXIT(TRUE);
END ELSE
IF ("Bal. Account No." = '') OR ("Bal. Account Type" <> "Bal. Account Type"::"G/L Account") THEN
IF IdentifyCashPaymentsFromGL(CustLedgerEntry) THEN
EXIT(TRUE);
EXIT(FALSE);
END;
// End of the added lines.
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Spanish version of Microsoft Dynamics NAV 2009 R2
-
The Spanish 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.
