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. The Cost Amount (Actual) value is generated incorrectly in value entries when you post a purchase credit memo that has an item charge in the Greek version of Microsoft Dynamics NAV

The Cost Amount (Actual) value is generated incorrectly in value entries when you post a purchase credit memo that has an item charge in the Greek version of Microsoft Dynamics NAV

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 create a purchase credit memo that has an item charge in the Greek version of Microsoft Dynamics NAV. After you post the purchase credit memo, the value in the Cost Amount (Actual) field in the created value entry is incorrect. The Cost Amount (Actual) value has the positive sign instead of the negative sign incorrectly. Additionally, when you run the "Post Inventory Cost to G/L" report for the item, the Cost Posted to G/L value is zero in the created value entry of item charge (credit) incorrectly.
This problem occurs in the following products:
  • The Greek version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Greek version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

↑ Back to the top

Cause

This problem occurs because the Cost Amount (Actual) field is updated by the UpdateValuationFields function incorrectly in the Greek version of Microsoft Dynamics NAV.

↑ 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 InitValueEntry function in the Item Jnl.-Post Line codeunit (22) as follow:
    Existing code
    ...
    IF "Partial Revaluation" THEN
    ValueEntry."Partial Revaluation" := TRUE;

    // Delete the following lines.
    IF (ItemLedgEntry.Quantity > 0) OR
     (ItemLedgEntry."Invoiced Quantity" > 0) OR
     (("Value Entry Type" = "Value Entry Type"::"Direct Cost") AND ("Item Charge No." = '')) OR
     ("Entry Type" = "Entry Type"::Output) OR
     Adjustment
    THEN
    // End of the lines.

    ValueEntry.Inventoriable := TRUE;
    ...
    Replacement code
    ...
    IF "Partial Revaluation" THEN
    ValueEntry."Partial Revaluation" := TRUE;

    // Add the following lines.
    IF (ItemLedgEntry.Quantity > 0) OR
    (ItemLedgEntry."Invoiced Quantity" > 0) OR
    (("Value Entry Type" = "Value Entry Type"::"Direct Cost") AND ("Item Charge No." = '')) OR
    ("Entry Type" = "Entry Type"::Output) OR
    Adjustment OR
    (("Document Type" IN ["Document Type"::"Purchase Return Shipment","Document Type"::"Purchase Credit Memo"]) AND
    ("Item Charge No." <> '') AND
    ("Entry Type" = "Entry Type"::Purchase))
    THEN
    // End of the lines.

    ValueEntry.Inventoriable := TRUE;
    ...
  2. Change the code in the UpdateValuationFields function in the Item Jnl.-Post Line codeunit (22) as follow:
    Existing code
    ...
    IF (ValueEntry."Expected Cost" = FALSE) AND (ValueEntry."Item Charge No." <> '') AND
    (ValueEntry."Item Ledger Entry Type" = ValueEntry."Item Ledger Entry Type"::Purchase) THEN BEGIN

    // Delete the following lines.
    IF ValueEntry."Cost Amount (Actual)" = 0 THEN
     ValueEntry."Cost Amount (Actual)" := -ValueEntry."Purchase Amount (Actual)";
    // End of the lines.

    END;
    ...
    Replacement code
    ...
    IF (ValueEntry."Expected Cost" = FALSE) AND (ValueEntry."Item Charge No." <> '') AND
    (ValueEntry."Item Ledger Entry Type" = ValueEntry."Item Ledger Entry Type"::Purchase) THEN BEGIN

    // Add the following lines.
    IF ValueEntry."Cost Amount (Actual)" = 0 THEN
    IF ValueEntry."Document Type" = ValueEntry."Document Type"::"Purchase Credit Memo" THEN
    ValueEntry."Cost Amount (Actual)" := ValueEntry."Purchase Amount (Actual)"
    ELSE
    ValueEntry."Cost Amount (Actual)" := -ValueEntry."Purchase Amount (Actual)";
    // End of the lines.

    END;
    ...
  3. Change the code in the PostItemJnlLine function in the Purch.-Post codeunit (90) as follow:
    Existing code
    ...
    IF QtyToBeInvoiced <> 0 THEN BEGIN
    ItemJnlLine."Invoice No." := GenJnlLineDocNo;
    ItemJnlLine."External Document No." := GenJnlLineExtDocNo;

    // Delete the following lines.
    IF ItemJnlLine."Document No." = '' THEN BEGIN
     IF "Document Type" = "Document Type"::"Credit Memo" THEN
     ItemJnlLine."Document Type" := ItemJnlLine."Document Type"::"Purchase Credit Memo"
     ELSE
     ItemJnlLine."Document Type" := ItemJnlLine."Document Type"::"Purchase Invoice";
     ItemJnlLine."Document No." := GenJnlLineDocNo;
    END;
    // End of the lines.

    ItemJnlLine."Posting No. Series" := PurchHeader."Posting No. Series";
    END;
    END;
    ...
    Replacement code
    ...
    IF QtyToBeInvoiced <> 0 THEN BEGIN
    ItemJnlLine."Invoice No." := GenJnlLineDocNo;
    ItemJnlLine."External Document No." := GenJnlLineExtDocNo;

    // Add the following lines.
    IF "Document Type" IN ["Document Type"::"Return Order","Document Type"::"Credit Memo"] THEN
    ItemJnlLine."Document Type" := ItemJnlLine."Document Type"::"Purchase Credit Memo"
    ELSE
    ItemJnlLine."Document Type" := ItemJnlLine."Document Type"::"Purchase Invoice";
    IF ItemJnlLine."Document No." = '' THEN
    ItemJnlLine."Document No." := GenJnlLineDocNo;
    // End of the lines.

    ItemJnlLine."Posting No. Series" := PurchHeader."Posting No. Series";
    END;
    END;
    ...

Prerequisites

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

Restart requirement

After you apply this hotfix, and you perform any required data repair, you must restart each Microsoft Dynamics NAV client.
You do not have to restart Microsoft Windows.

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

↑ Back to the top

Article Info
Article ID : 2494368
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 227