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 unit price for an item is not updated correctly on the job planning line in Microsoft Dynamics NAV 2009

The unit price for an item is not updated correctly on the job planning line in Microsoft Dynamics NAV 2009

View products that this article applies to.

Rapidly Published articles provide information directly from within the Microsoft support organization. The information that is contained herein is created in response to emerging or unique topics, or is intended to supplement other Knowledge Base information.

↑ Back to the top

This article applies to Microsoft Dynamics NAV 2009 for all countries and all language locales.

↑ Back to the top

Symptoms

Assume that you set up the sales prices for an item in Microsoft Dynamics NAV 2009. When you create a new job planning line for the item, you experience the following symptoms:

  • In the Microsoft Dynamics NAV 2009 Classic client, the sales prices are not considered. Therefore, the unit price for the item in the job planning line is incorrect.
  • In the Microsoft Dynamics NAV 2009 RoleTailored client (RTC), the sales prices are considered. However, if you change the quantity for the item in the job planning line, the Microsoft Dynamics NAV 2009 RTC calculates the Line Amount value, the Line Discount Amount value and the Discount % value incorrectly. Additionally, if you move the pointer to any other planning line and then go back to the job planning line that you created to change the quantity for the item, Microsoft Dynamics NAV 2009 RTC does not recalculate the correct unit price. Therefore, the unit price for the item is incorrect.

↑ 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, do the following steps:
  1. Change the code in the RetrieveCostPrice function in the Job Journal Line table (210) as follows:
    Existing code
    ...
            CASE Type OF
              Type::Item:
                IF ("No." <> xRec."No.") OR
                   ("Location Code" <> xRec."Location Code") OR
                   ("Variant Code" <> xRec."Variant Code") OR
                   ("Unit of Measure Code" <> xRec."Unit of Measure Code") AND
                   (("Applies-to Entry" = 0) AND ("Applies-from Entry" = 0)) THEN
                  EXIT(TRUE);
              Type::Resource:
                IF ("No." <> xRec."No.") OR
    ...
    Replacement code
    ...
            CASE Type OF
              Type::Item:
                IF ("No." <> xRec."No.") OR
                   ("Location Code" <> xRec."Location Code") OR
                   ("Variant Code" <> xRec."Variant Code") OR

    // Add the following line.
                   (Quantity <> xRec.Quantity) OR
    // End of added line.

                   ("Unit of Measure Code" <> xRec."Unit of Measure Code") AND
                   (("Applies-to Entry" = 0) AND ("Applies-from Entry" = 0)) THEN
                  EXIT(TRUE);
              Type::Resource:
                IF ("No." <> xRec."No.") OR
    ...
  2. Change the code in the RetrieveCostPrice function in the Job Planning Line table (1003) as follows:
    Existing code
    ...
            CASE Type OF
              Type::Item:
                IF ("No." <> xRec."No.") OR
                   ("Location Code" <> xRec."Location Code") OR
                   ("Variant Code" <> xRec."Variant Code") OR
                   ("Unit of Measure Code" <> xRec."Unit of Measure Code") THEN
                  EXIT(TRUE);
              Type::Resource:
                IF ("No." <> xRec."No.") OR
                   ("Work Type Code" <> xRec."Work Type Code") OR
    ...
    Replacement code
    ...
            CASE Type OF
              Type::Item:
                IF ("No." <> xRec."No.") OR
                   ("Location Code" <> xRec."Location Code") OR
                   ("Variant Code" <> xRec."Variant Code") OR

    // Add the following line.
                   (Quantity <> xRec.Quantity) OR
    // End of added line.

                   ("Unit of Measure Code" <> xRec."Unit of Measure Code") THEN
                  EXIT(TRUE);
              Type::Resource:
                IF ("No." <> xRec."No.") OR
                   ("Work Type Code" <> xRec."Work Type Code") OR
    ...

Prerequisites

You must have 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

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top

Keywords: kbmbsquickpub, kbnoloc, kbmbscodefix, kbqfe, kbmbsgeneralledger, kbmbspartner, kbsurveynew, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 980831
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 170