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. Certain fields are not updated correctly after you unapply and reapply a dishonored document in the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1

Certain fields are not updated correctly after you unapply and reapply a dishonored document in the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1

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 a dishonored document in a cash receipt journal to a bill in the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). After you run the Unapply function on the dishonored document, the Document Type to Close field and the Document No. to Close field are not reset as expected. The value in the two fields still maintains the old invoice value. In this situation, after you apply the dishonored document to another bill, the document still keeps the old value in the Document Type to Close field and the Document No. to Close field.

↑ 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. Change the code in the ApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follow:
    Existing code
    ...

    OldCustLedgEntry."Applies-to ID" := '';
    OldCustLedgEntry."Amount to Apply" := 0;
    OldCustLedgEntry.MODIFY;

    IF GLSetup."Unrealized VAT" OR
    ...
    Replacement code
    ...

    OldCustLedgEntry."Applies-to ID" := '';
    OldCustLedgEntry."Amount to Apply" := 0;

    //Add the following lines.
    IF OldCustLedgEntry."Document Type" = OldCustLedgEntry."Document Type"::Dishonored THEN BEGIN 
    OldCustLedgEntry."Document Type to Close" := GenJnlLine."Document Type to Close"; 
    OldCustLedgEntry."Document No. to Close" := GenJnlLine."Document No. to Close";
    END; 
    IF OldCustLedgEntry."Document Type" = OldCustLedgEntry."Document Type"::Payment THEN BEGIN 
    NewCVLedgEntryBuf."Document Type to Close" := OldCustLedgEntry."Document Type to Close"; 
    NewCVLedgEntryBuf."Document No. to Close" := OldCustLedgEntry."Document No. to Close"; 
    END;
    //End of the lines.

    OldCustLedgEntry.MODIFY;

    IF GLSetup."Unrealized VAT" OR
    ...
  2. Change the code in the CustPostApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follow:
    Existing code 1
    GenJnlLine := GenJnlLinePostApply;
    GenJnlLine."Source Currency Code" := CustLedgEntryPostApply."Currency Code";
    GenJnlLine."Applies-to ID" := CustLedgEntryPostApply."Applies-to ID";
    CustLedgEntry.TRANSFERFIELDS(CustLedgEntryPostApply);
    ...
    Replacement code 1
    GenJnlLine := GenJnlLinePostApply;
    GenJnlLine."Source Currency Code" := CustLedgEntryPostApply."Currency Code";
    GenJnlLine."Applies-to ID" := CustLedgEntryPostApply."Applies-to ID";

    //Add the following lines.
    IF GenJnlLine."Document Type" = GenJnlLine."Document Type"::Payment THEN BEGIN 
    GenJnlLine."Document Type to Close" := CustLedgEntryPostApply."Document Type to Close"; 
    GenJnlLine."Document No. to Close" := CustLedgEntryPostApply."Document No. to Close"; 
    END; 
    //End of the lines.

    CustLedgEntry.TRANSFERFIELDS(CustLedgEntryPostApply);
    ...
    Existing code 2
    ...

    ApplyCustLedgEntry(
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,GLSetup."Appln. Rounding Precision");
    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,FALSE);
    CustLedgEntry.MODIFY;
    ...
    Replacement code 2
    ...

    ApplyCustLedgEntry(
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,GLSetup."Appln. Rounding Precision");
    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,FALSE);

    //Add the following lines.
    IF CVLedgEntryBuf."Document Type" = CVLedgEntryBuf."Document Type"::Dishonored THEN BEGIN 
    CustLedgEntry."Document Type to Close" := CVLedgEntryBuf."Document Type to Close"; 
    CustLedgEntry."Document No. to Close" := CVLedgEntryBuf."Document No. to Close";
    END; 
    //End of the lines.

    CustLedgEntry.MODIFY;
    ...
  3. Change the code in the UnapplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follow:
    Existing code
    ...

    CustLedgEntry."Pmt. Disc. Given (LCY)" := 0;
    CustLedgEntry."Pmt. Tolerance (LCY)" := 0;
    END;
    CustLedgEntry.MODIFY;
    END;
    UNTIL DtldCustLedgEntry2.NEXT(-1) = 0;
    ...
    Replacement code
    ...

    CustLedgEntry."Pmt. Disc. Given (LCY)" := 0;
    CustLedgEntry."Pmt. Tolerance (LCY)" := 0;

    //Add the following lines.
    IF CustLedgEntry."Document Type" = CustLedgEntry."Document Type"::Dishonored THEN BEGIN 
    CustLedgEntry."Document Type to Close" := CustLedgEntry."Document Type to Close"::" ";
    CustLedgEntry."Document No. to Close" := '';
    END; 
    //End of the lines.

    END;
    CustLedgEntry.MODIFY;
    END;
    UNTIL DtldCustLedgEntry2.NEXT(-1) = 0;
    ...

Prerequisites

You must have the Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 installed to apply this hotfix.

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

↑ Back to the top

Article Info
Article ID : 2274662
Revision : 2
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 266