Microsoft KB Archive Search

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.

  1. Home
  2. Application entries are not deleted as expected when you delete simulation entries that are applied to invoices for a vendor or a customer in the Greek version of Microsoft Dynamics NAV 2009

Application entries are not deleted as expected when you delete simulation entries that are applied to invoices for a vendor or a customer in the Greek version of Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Greek (gr) language locale.

↑ Back to the top

Symptoms

Assume that you delete a simulation entry that is applied to an invoice for a vendor or a customer in the Simulation Registers dialog box in the Greek version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). In this situation, the corresponding application entry is not deleted. Therefore, when you run a trial balance report for the vendor or the customer, the application entry is included in the calculation unexpectedly. Additionally, this problem also occurs when you run a ledger report for the vendor or the customer.
This problem occurs in the following products:
  • The Greek version of Microsoft Dynamics NAV 2009 R2
  • The Greek version of Microsoft Dynamics NAV 2009 Service Pack (SP1)

↑ 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. Create a new local variable in the DeleteReg function in the Simulation Management codeunit (16755) , and then specify the variable as follow:
    • Name: SimCust2
    • DataType: Record
    • Subtype: 16757
  2. Create a new local variable in the DeleteReg function in the Simulation Management codeunit (16755) , and then specify the variable as follow:
    • Name: SimVend2
    • DataType: Record
    • Subtype: 16759
  3. Create a new local variable in the DeleteReg function in the Simulation Management codeunit (16755) , and then specify the variable as follow:
    • Name: SimDtldCust2
    • DataType: Record
    • Subtype: 16758
  4. Create a new local variable in the DeleteReg function in the Simulation Management codeunit (16755) , and then specify the variable as follow:
    • Name: SimDtldVend2
    • DataType: Record
    • Subtype: 16760
  5. Change the code in the DeleteReg function in the Simulation Management codeunit (16755) as follows:
    Existing code 1
    ...
    IF SimCust.FIND('-') THEN BEGIN
    REPEAT
    WITH SimDtldCust DO BEGIN

    // Delete the following lines. 
    SimDtldCust.SETRANGE("Cust. Ledger Entry No.",SimCust."Entry No.");
    IF SimDtldCust.FIND('-') THEN BEGIN
    REPEAT
    SimDtldCust.DELETE;
    UNTIL SimDtldCust.NEXT = 0;
    END;
    // End of the lines. 

    END;
    WITH LedgEntryDim DO BEGIN
    LedgEntryDim.SETRANGE("Table ID",16757);
    ...
    Replacement code 1
    ...
    IF SimCust.FIND('-') THEN BEGIN
    REPEAT
    WITH SimDtldCust DO BEGIN

    // Add the following lines.
    RESET;
    SETCURRENTKEY("Cust. Ledger Entry No.","Entry Type","Posting Date");
    SETRANGE("Cust. Ledger Entry No.",SimCust."Entry No.");
    IF FINDSET THEN
    REPEAT
    IF "Entry Type" = "Entry Type"::"Initial Entry" THEN
    DELETE
    ELSE BEGIN
    SimDtldCust2.SETRANGE("Transaction No.","Transaction No.");
    SimDtldCust2.SETFILTER("Entry Type",'>%1',"Entry Type"::"Initial Entry");
    IF SimDtldCust2.FINDSET THEN
    REPEAT
    IF (SimDtldCust2."Cust. Ledger Entry No." <> SimCust."Entry No.") AND
    (SimDtldCust2."Entry Type" = SimDtldCust2."Entry Type"::Application) 
    THEN BEGIN
    SimCust2.GET(SimDtldCust2."Cust. Ledger Entry No.");
    SimCust2."Accepted Payment Tolerance" := 0;
    IF NOT SimCust2.Open THEN BEGIN
    SimCust2.Open := TRUE;
    SimCust2."Closed by Entry No." := 0;
    SimCust2."Closed at Date" := 0D;
    SimCust2."Closed by Amount" := 0;
    SimCust2."Closed by Amount (LCY)" := 0;
    SimCust2."Closed by Currency Code" := '';
    SimCust2."Closed by Currency Amount" := 0;
    SimCust2."Pmt. Disc. Given (LCY)" := 0;
    SimCust2."Pmt. Tolerance (LCY)" := 0;
    END;
    SimCust2.MODIFY;
    END;
    SimDtldCust2.DELETE;
    UNTIL SimDtldCust2.NEXT = 0;
    END;
    UNTIL NEXT = 0;
    // End of the lines. 

    END;
    WITH LedgEntryDim DO BEGIN
    LedgEntryDim.SETRANGE("Table ID",16757);
    ...
    Existing code 2
    ...
    IF SimVend.FIND('-') THEN BEGIN
    REPEAT
    WITH SimDtldVend DO BEGIN

    // Delete the following lines.
    SimDtldVend.SETRANGE("Vendor Ledger Entry No.",SimVend."Entry No.");
    IF SimDtldVend.FIND('-') THEN BEGIN
    REPEAT
    SimDtldVend.DELETE;
    UNTIL SimDtldVend.NEXT = 0;
    END;
    // End of the lines.

    END;
    WITH LedgEntryDim DO BEGIN
    LedgEntryDim.SETRANGE("Table ID",16759);
    ...
    Replacement code 2
    ...
    IF SimVend.FIND('-') THEN BEGIN
    REPEAT
    WITH SimDtldVend DO BEGIN

    // Add the following lines.
    RESET;
    SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type","Posting Date");
    SETRANGE("Vendor Ledger Entry No.",SimVend."Entry No.");
    IF FINDSET THEN
    REPEAT
    IF "Entry Type" = "Entry Type"::"Initial Entry" THEN
    DELETE
    ELSE BEGIN
    SimDtldVend2.SETRANGE("Transaction No.","Transaction No.");
    SimDtldVend2.SETFILTER("Entry Type",'>%1',"Entry Type"::"Initial Entry");
    IF SimDtldVend2.FINDSET THEN
    REPEAT
    IF (SimDtldVend2."Vendor Ledger Entry No." <> SimVend."Entry No.") AND
    (SimDtldVend2."Entry Type" = SimDtldVend2."Entry Type"::Application)
    THEN BEGIN
    SimVend2.GET(SimDtldVend2."Vendor Ledger Entry No.");
    SimVend2."Accepted Payment Tolerance" := 0;
    IF NOT SimVend2.Open THEN BEGIN
    SimVend2.Open := TRUE;
    SimVend2."Closed by Entry No." := 0;
    SimVend2."Closed at Date" := 0D;
    SimVend2."Closed by Amount" := 0;
    SimVend2."Closed by Amount (LCY)" := 0;
    SimVend2."Closed by Currency Code" := '';
    SimVend2."Closed by Currency Amount" := 0;
    SimVend2."Pmt. Disc. Rcd.(LCY)" := 0;
    SimVend2."Pmt. Tolerance (LCY)" := 0;
    END;
    SimVend2.MODIFY;
    END;
    SimDtldVend2.DELETE;
    UNTIL SimDtldVend2.NEXT = 0;
    END;
    UNTIL NEXT = 0;
    // End of the lines.

    END;
    WITH LedgEntryDim DO BEGIN
    LedgEntryDim.SETRANGE("Table ID",16759);
    ...



Prerequisites

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

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

↑ Back to the top

Article Info
Article ID : 2705187
Revision : 1
Created on : 1/7/2017
Published on : 9/19/2012
Exists online : False
Views : 236