Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Customer Bills List report (12117) does not display dishonored transactions as expected in the Italian version of Microsoft Dynamics NAV


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Italian (it) language locale.

↑ Back to the top


Symptoms

Assume that you apply hotfix 955348, hotfix 957356, hotfix 2664436, hotfix 2496071 and hotfix 2479692 in the Italian version of Microsoft Dynamics NAV. When you run the Customer Bills List report (12117), dishonored transactions are displayed incorrectly. The dishonored transactions are not linked to the corresponding payments. Additionally, you may not understand which bank receipts are applied to the dishonored transactions from the report.
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)
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
For more information about hotfix 955348, click the following article number to view the article in the Microsoft Knowledge Base:
955348 The Vendor Bill List report (12116) and the Customer Bill List report (12117) do not show unapplied payments in the Italian version of Microsoft Dynamics NAV
For more information about hotfix 957356, click the following article number to view the article in the Microsoft Knowledge Base:
957356 The Vendor Bill List report (12116) and the Customer Bill List report (12117) displays an incorrect vendor balance in the Italian version of Microsoft Dynamics NAV 5.0
For more information about hotfix 2664436, click the following article number to view the article in the Microsoft Knowledge Base:
2664436 The balance in the Vendor Account Bills List report and the Customer Bills List report is incorrect after you perform the Closing Bank Receipts process in the Italian version of Microsoft Dynamics NAV
For more information about hotfix 2496071, click the following article number to view the article in the Microsoft Knowledge Base:
2496071 The Customer Bills List report and the Vendor Account Bills List report print a credit memos applied to invoice two times unexpectedly in the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
For more information about hotfix 2479692, click the following article number to view the article in the Microsoft Knowledge Base:
2479692 The Customer Bill List report (12117) does not show the corresponding bank receipt for each invoice installment in the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1

↑ Back to the top


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.

↑ Back to the top




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, but 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 Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. 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:
  1. Change the code in the Data Item Number 2 in the Customer Bills List report (12117) as follows:
    Existing code
    ...
    END;

    OnAfterGetRecord=BEGIN
    IF ("Document Type" = "Document Type"::Payment) OR ("Document Type" = "Document Type"::" ") THEN
    CurrReport.SKIP;
    ...
    Replacement code
    ...
    END;

    OnAfterGetRecord=BEGIN

    // Add the following line.
    PrintCustLedgEntry2 := FALSE;

    IF ("Document Type" = "Document Type"::Payment) OR ("Document Type" = "Document Type"::" ") THEN
    CurrReport.SKIP;
    ...
  2. Change the code in the Data Item Number 3 in the Customer Bills List report (12117) as follows:
    Existing code
    ...
    ClosedByAmountLCY := "Closed by Amount (LCY)";
    TotalForCustomer += "Amount (LCY)";
    TotalClosedByAmntLCY += "Amount (LCY)";
    END;

    DataItemLink=Document No. to Close=FIELD(Document No.);
    ...
    Replacement code
    ...
    ClosedByAmountLCY := "Closed by Amount (LCY)";
    TotalForCustomer += "Amount (LCY)";
    TotalClosedByAmntLCY += "Amount (LCY)";

    // Add the following line.
    PrintCustLedgEntry2 := TRUE;

    END;

    DataItemLink=Document No. to Close=FIELD(Document No.);
    ...
  3. Change the code in the Data Item Number 4 in the Customer Bills List report (12117) as follows:
    Existing code
    ...
    END;

    OnAfterGetRecord=BEGIN
    CustLedgEntry3.GET("Applied Cust. Ledger Entry No.");
    CustLedgEntry3.CALCFIELDS("Original Amt. (LCY)");
    ClosedByAmountLCY := "Amount (LCY)";
    ...
    Replacement code
    ...
    END;

    OnAfterGetRecord=BEGIN

    // Add the following lines.
    IF PrintCustLedgEntry2 THEN
    CurrReport.SKIP;
    // End of the lines.

    CustLedgEntry3.GET("Applied Cust. Ledger Entry No.");
    CustLedgEntry3.CALCFIELDS("Original Amt. (LCY)");
    ClosedByAmountLCY := "Amount (LCY)";
    ...
  4. Change the code in the Global Variables in the Customer Bills List report (12117) as follows:
    Existing code
    ...
    BalanceDue@1130012 : Decimal;
    NULL@1130013 : DateFormula;
    CustLedgEntry3@1130130 : Record 21;

    BEGIN
    ...
    Replacement code
    ...
    BalanceDue@1130012 : Decimal;
    NULL@1130013 : DateFormula;
    CustLedgEntry3@1130130 : Record 21;

    // Add the following line.
    PrintCustLedgEntry2@1130014 : Boolean;

    BEGIN
    ...
  5. Change the code in the Data Item Number 2 in the Closing Bank Receipts report (12171) as follows:
    Existing code
    ...
    COMMIT;

    CustEntryApplyPostedEntries.SetCheckDim(CheckDim);
    CustEntryApplyPostedEntries.RUN(CustLedgEntry);
    END;
    ...
    Replacement code
    ...
    COMMIT;

    CustEntryApplyPostedEntries.SetCheckDim(CheckDim);

    // Add the following line.
    CustLedgEntry.GET(CustEntry1."Entry No.");

    CustEntryApplyPostedEntries.RUN(CustLedgEntry);
    END;
    ...
  6. Change the code in the ApplyCustLedgEntry function in the Gen. Jnl.-Post Line" codeunit (12) as follows:
    Existing code
    ...
    TempOldCustLedgEntry.SETCURRENTKEY("Customer No.","Applies-to ID",Open,Positive,"Due Date");
    OldCustLedgEntry.SETRANGE("Customer No.",NewCVLedgEntryBuf."CV No.");
    OldCustLedgEntry.SETRANGE(Open,TRUE);

    // Delete the following line.
    OldCustLedgEntry.SETRANGE("Bank Receipt Issued", FALSE);

    OldCustLedgEntry.SETFILTER("Entry No.",'<>%1',NewCVLedgEntryBuf."Entry No.");
    OldCustLedgEntry.SETRANGE("Applies-to ID",GenJnlLine."Applies-to ID");
    IF NOT(Cust."Application Method" = Cust."Application Method"::"Apply to Oldest") THEN
    ...
    Replacement code
    ...
    TempOldCustLedgEntry.SETCURRENTKEY("Customer No.","Applies-to ID",Open,Positive,"Due Date");
    OldCustLedgEntry.SETRANGE("Customer No.",NewCVLedgEntryBuf."CV No.");
    OldCustLedgEntry.SETRANGE(Open,TRUE);

    // Add the following line.
    OldCustLedgEntry.SETRANGE("Bank Receipt Issued", TRUE);

    OldCustLedgEntry.SETFILTER("Entry No.",'<>%1',NewCVLedgEntryBuf."Entry No.");
    OldCustLedgEntry.SETRANGE("Applies-to ID",GenJnlLine."Applies-to ID");
    IF NOT(Cust."Application Method" = Cust."Application Method"::"Apply to Oldest") THEN
    ...

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 Service Pack 1
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1

Removal information

You cannot remove this hotfix.

↑ Back to the top


Status

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

↑ Back to the top


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 Use for other considerations.

↑ Back to the top


Keywords: kbmbscodefix, kbnoloc, kbsurveynew, kbqfe, kbmbspartner, kbmbsquickpub, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2664438
Revision : 1
Created on : 1/7/2017
Published on : 2/11/2012
Exists online : False
Views : 310