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 DTA Suggest Vendor Payment report (3010546) and the LSV Suggest Collection report (3010831) suggest incorrect lines in the Swiss version of Microsoft Dynamics NAV


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • French (Switzerland) (fr-ch)
  • German (Switzerland) (gr-ch)
  • Italian (Switzerland) (it-ch)

↑ Back to the top


Symptoms

Assume that you post a purchase invoice or a sales invoice in the Swiss version of Microsoft Dynamics NAV. When you run the DTA Suggest Vendor Payment report (3010546) on the payment journal or the LSV Suggest Collection report (3010831) on the LSV journal list by using a posting date that is earlier than the posting date of the invoice, incorrect lines are suggested. Therefore, the posting date is incorrect in the detailed customer ledger entries or the detailed vendor leger entries after you post the lines. Sometimes you even cannot post the lines and receive a consistent error message.
This problem occurs in the following products:
  • The Swiss version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Swiss version of Microsoft Dynamics NAV 2009
  • The Swiss version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • The Swiss version of Microsoft Dynamics NAV 5.0

↑ Back to the top


Cause

This problem occurs because a check is missing in the DTA Suggest Vendor Payment report (3010546) and in the LSV Suggest Collection report (3010831). The check is introduced to avoid generating a payment line that has a posting date earlier that is than the posting date of the invoice.

↑ 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 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. Add a new global variable in the DTA Suggest Vendor Payment report (3010546), and then specify the variable as follows:
    • Name: VendorLedgEntryTemp@1150058
    • DataTypeRecord
    • SubtypeVendor Ledger Entry
    • Temporary: Yes
  2. Add a new text constant in the DTA Suggest Vendor Payment report (3010546), and then specify the constant as follows: 
    • Name: Text50000@1150064
    • Constant value: ENU=There are one or more entries for which no payment suggestions have been made because the posting dates of the entries are later than the posting date in the DTA Suggest Vendor Payments batch job request window. Do you want to see the entries?
  3. Add the following code in the OnPreReport trigger in the DTA Suggest Vendor Payment report (3010546):
    VendorLedgEntryTemp.DELETEALL;
  4. Add the following code in the OnPostReport trigger in the DTA Suggest Vendor Payment report (3010546):
    COMMIT;
    IF NOT VendorLedgEntryTemp.ISEMPTY THEN
    IF CONFIRM(Text50000) THEN
    FORM.RUNMODAL(0,VendorLedgEntryTemp);
  5. Change the code in the Vendor - OnPostDataItem trigger in the DTA Suggest Vendor Payment report (3010546) as follow:
    Existing code
    d.CLOSE;
    IF NoOfLinesInserted > 0 THEN BEGIN
    WriteBalAccountLine(ToGlLine);
    MESSAGE(Text011,NoOfLinesInserted,GlSetup."LCY Code",TotalAmtLCY);
    IF NoOfVendorsWithCM > 0 THEN
    MESSAGE(Text013 + Text014 + Text017,NoOfVendorsWithCM,VendWithCmTxt)
    END ELSE
    MESSAGE(Text018,FromDueDate,ToDueDate);
    Replacement code
    d.CLOSE;
    IF VendorLedgEntryTemp.ISEMPTY THEN BEGIN
    IF NoOfLinesInserted > 0 THEN BEGIN
    WriteBalAccountLine(ToGlLine);
    MESSAGE(Text011,NoOfLinesInserted,GlSetup."LCY Code",TotalAmtLCY);
    IF NoOfVendorsWithCM > 0 THEN
    MESSAGE(Text013 + Text014 + Text017,NoOfVendorsWithCM,VendWithCmTxt)
    END ELSE
    MESSAGE(Text018,FromDueDate,ToDueDate);
    END;
  6. Change the code in the WritePmtSuggestLines function in the DTA Suggest Vendor Payment report (3010546) as follows:
    Existing code 1
    // CH2316.begin
    VendorLedgerEntryNo := VendEntry."Entry No.";
    // CH2316.end
    WITH ToGlLine DO BEGIN
    INIT;
    ...
    Replacement code 1
    IF VendEntry."Posting Date" <= PostDate THEN BEGIN // CH0001
    // CH2316.begin
    VendorLedgerEntryNo := VendEntry."Entry No.";
    // CH2316.end
    WITH ToGlLine DO BEGIN
    INIT;
    ...
    Existing code 2
    ...
    VendorLedgerEntry2.GET(VendorLedgerEntryNo);
    VendorLedgerEntry2."On Hold" := 'DTA';
    VendorLedgerEntry2."Accepted Payment Tolerance" := 0;
    VendorLedgerEntry2.MODIFY;
    // CH2316.END
    Replacement code 2
    ...
    VendorLedgerEntry2.GET(VendorLedgerEntryNo);
    VendorLedgerEntry2."On Hold" := 'DTA';
    VendorLedgerEntry2."Accepted Payment Tolerance" := 0;
    VendorLedgerEntry2.MODIFY;
    // CH2316.END
    END ELSE BEGIN
    VendorLedgEntryTemp := VendEntry;
    VendorLedgEntryTemp.INSERT;
    END;
  7. Add a new global variable in the LSV Suggest Collection report (3010831), and then specify the variable as follows:
    • Name: TempCustLedgEntry@1150042
    • DataType: Record
    • SubtypeCustomer Ledger Entry
    • TemporaryYes
  8. Add a new text constant in the LSV Suggest Collection report (3010831), and then specify the constant as follows:
    • Name: Text50000@1150064
    • Constant value: ENU=There are one or more entries for which no collection suggestions have been made because the posting dates of the entries are later than the collection date in the LSV Collect Suggestions batch job request window. Do you want to see the entries?
  9. Change the code in the OnPreReport trigger in the the LSV Suggest Collection report (3010831) as follow:
    Existing code
    IF LsvJournal."LSV Bank Code" = '' THEN
    ERROR(Text020);
    Replacement code
    IF LsvJournal."LSV Bank Code" = '' THEN
    ERROR(Text020);
    TempCustLedgEntry.DELETEALL;
  10. Add the following code in the OnPostReport trigger in the LSV Suggest Collection report (3010831):
    COMMIT;
    IF NOT TempCustLedgEntry.ISEMPTY THEN
    IF CONFIRM(Text50000) THEN
    FORM.RUNMODAL(0,TempCustLedgEntry);
  11. Change the code in the Customer - OnPostDataItem trigger in the LSV Suggest Collection report (3010831) as follow:
    Existing code
    d.CLOSE;
    IF NoOfLinesInserted > 0 THEN BEGIN
    MESSAGE(Text007,NoOfLinesInserted,LsvSetup."LSV Currency Code",TotalAmt);
    IF LsvJournal."LSV Journal Description" = '' THEN BEGIN
    LsvJournal."LSV Journal Description" :=
    FORMAT(STRSUBSTNO(Text021,LsvSetup."LSV Currency Code",FromDueDate,ToDueDate,Customer.GETFILTERS)
    ,-MAXSTRLEN(LsvJournal."LSV Journal Description"));
    END;
    LsvJournal."Credit Date" := CollectionDate;
    LsvJournal.MODIFY;
    // CH2813.BEGIN
    IF NoOfCustWithCreditMemo > 0 THEN
    IF NOT CONFIRM(Text009 + Text010 + Text012 + Text013,TRUE,NoOfCustWithCreditMemo,CustCreditMemoTxt) THEN
    ERROR(Text014);
    // CH2813.END
    END ELSE
    MESSAGE(Text015,FromDueDate,ToDueDate);
    Replacement code
    d.CLOSE;
    IF TempCustLedgEntry.ISEMPTY THEN BEGIN // CH0001
    IF NoOfLinesInserted > 0 THEN BEGIN
    MESSAGE(Text007,NoOfLinesInserted,LsvSetup."LSV Currency Code",TotalAmt);
    IF LsvJournal."LSV Journal Description" = '' THEN BEGIN
    LsvJournal."LSV Journal Description" :=
    FORMAT(STRSUBSTNO(Text021,LsvSetup."LSV Currency Code",FromDueDate,ToDueDate,Customer.GETFILTERS)
    ,-MAXSTRLEN(LsvJournal."LSV Journal Description"));
    END;
    LsvJournal."Credit Date" := CollectionDate;
    LsvJournal.MODIFY;
    // CH2813.BEGIN
    IF NoOfCustWithCreditMemo > 0 THEN
    IF NOT CONFIRM(Text009 + Text010 + Text012 + Text013,TRUE,NoOfCustWithCreditMemo,CustCreditMemoTxt) THEN
    ERROR(Text014);
    // CH2813.END
    END ELSE
    MESSAGE(Text015,FromDueDate,ToDueDate);
    END;
  12. Change the code in the WritePmtSuggestLines function in the LSV Suggest Collection report (3010831) as follows:
    Existing code 1
    // Collection amt: Cust. Entry amount - Cash disc. possible
    WITH ToLSVJourLine DO BEGIN
    // Ensure, that the Entry is only once in the LSV Journal Line
    LSVJourLineCheck.SETCURRENTKEY("Applies-to Doc. No.");
    LSVJourLineCheck.SETRANGE("Applies-to Doc. No.",ActCustLedgEntry."Document No.");
    ...
    Replacement code 1
    // Collection amt: Cust. Entry amount - Cash disc. possible
    WITH ToLSVJourLine DO BEGIN
    IF CustLedgEntry."Posting Date" <= CollectionDate THEN BEGIN
    // Ensure, that the Entry is only once in the LSV Journal Line
    LSVJourLineCheck.SETCURRENTKEY("Applies-to Doc. No.");
    LSVJourLineCheck.SETRANGE("Applies-to Doc. No.",ActCustLedgEntry."Document No.");
    ...
    Existing code 2
    ...
    TotalAmt := TotalAmt + "Collection Amount";
    d.UPDATE(3,TotalAmt);
    // CH2813.BEGIN
    EntriesPerCust := EntriesPerCust + 1;
    // CH2813.END
    END;
    Replacement code 2
    ...
    TotalAmt := TotalAmt + "Collection Amount";
    d.UPDATE(3,TotalAmt);
    // CH2813.BEGIN
    EntriesPerCust := EntriesPerCust + 1;
    // CH2813.END

    //Add the follong lines.
    END ELSE BEGIN
    TempCustLedgEntry := CustLedgEntry;
    TempCustLedgEntry.INSERT;
    END;
    //End of the lines.

    END;


Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Swiss version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Swiss version of Microsoft Dynamics NAV 2009
  • The Swiss version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • The Swiss version of Microsoft Dynamics NAV 5.0

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: kb, kbqfe, kbmbspartner, kbmbsquickpub, kbmbsmigrate, kbsurveynew, kbnoloc, kbmbscodefix

↑ Back to the top

Article Info
Article ID : 2472115
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 308