Hjem › Nøgleord › Hotfix › Navision 5.0 SP1 › Navision 4.03 › Debitor › Navision 4.0 › Kreditnota › NAV 5.0

Forkert udligning af debitorposter

Submitted by Elizabeth, created 22/10/2009 - 14:59, updated 03/11/2009 - 22:42
DKK 100,00

Forkert udligning af debitorposter

En fejl i Navision (NAV) 4.0 og 5.0 gør det muligt at udligne en debitorpost med en kreditnota, selv om kreditnotaet har en tidligere bogføringsdato. Guldmedlemmer kan downloade hotfix til Navision 4.0SP3, 5.0 og 5.0SP1 nedenfor.

 
Se også den engelske beskrivelse af hotfixet nedenfor.

You can apply an existing open customer ledger entry by using a credit memo even if the credit memo has an earlier posting date in Microsoft Dynamics NAV

Symptoms

Resolution

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.

 

Download hotfix

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

 

 

...
      IF (TempGenJnlLine."Bal. Account Type" = TempGenJnlLine."Bal. Account Type"::Customer) OR
        (TempGenJnlLine."Bal. Account Type" = TempGenJnlLine."Bal. Account Type"::Vendor)
      THEN
        ExchAccGLJnlLine.RUN(TempGenJnlLine);

// Delete the following lines.
      IF (TempGenJnlLine."Document Type" = TempGenJnlLine."Document Type"::Payment) OR       
      (TempGenJnlLine."Document Type" = TempGenJnlLine."Document Type"::Refund) 
        THEN

      IF TempGenJnlLine."Account Type" = TempGenJnlLine."Account Type"::Customer THEN BEGIN
        IF TempGenJnlLine."Applies-to ID" <> '' THEN BEGIN
          CustLedgEntry.SETCURRENTKEY("Customer No.","Applies-to ID",Open);
          CustLedgEntry.SETRANGE("Customer No.",TempGenJnlLine."Account No.");
...

Replacement code

...
      IF (TempGenJnlLine."Bal. Account Type" = TempGenJnlLine."Bal. Account Type"::Customer) OR
        (TempGenJnlLine."Bal. Account Type" = TempGenJnlLine."Bal. Account Type"::Vendor)
      THEN
        ExchAccGLJnlLine.RUN(TempGenJnlLine);

       IF TempGenJnlLine."Account Type" = TempGenJnlLine."Account Type"::Customer THEN BEGIN
        IF TempGenJnlLine."Applies-to ID" <> '' THEN BEGIN
          CustLedgEntry.SETCURRENTKEY("Customer No.","Applies-to ID",Open);
          CustLedgEntry.SETRANGE("Customer No.",TempGenJnlLine."Account No.");
...

Prerequisites
You must have Microsoft Dynamics NAV 4.0 installed to apply this hotfix.

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. 
  
Applies to
 
• Microsoft Dynamics NAV 5.0
• Microsoft Dynamics NAV 4.0
Download hotfix til version 4.0SP3 - 5.0 - 5.0SP1

 
Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To apply this hotfix, change the code in the ValidateApplyRequirements function in the Gen. Journal Line table (81) as follows.

Existing code

 

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 5.0 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

 

In Microsoft Dynamics NAV, you can apply an existing open customer ledger entry by using a credit memo even if the credit memo has an earlier posting date. Additionally, if two entries have a foreign currency and use different exchange rates, the balance of the general ledger differs from the balance of the customer ledger entries. This problem occurs in the following products:
• Microsoft Dynamics NAV 5.0
• Microsoft Dynamics NAV 4.0
 
 
Nøgleord: