Hotfix til kostbeløb på sags planlægningslinje i Navision 5.0
Submitted by Elizabeth, created 30/10/2009 - 15:14, updated 09/04/2010 - 14:38
When you create a job planning line in Microsoft Dynamics NAV 5.0, the value in the Direct Unit Cost (LCY) field is incorrect. When this problem occurs, the value uses a foreign currency instead of using a local currency.
Resolution
DKK 100,00
Værdien i "Direkte Kostbeløb (RV)" feltet er forkert, når man opretter en sags planlægningslinje i Microsoft Dynamics NAV 5.0
The value in the "Direct Unit Cost (LCY)" field is incorrect when you create a job planning line in Microsoft Dynamics NAV 5.0
View products that this article applies to.
View products that this article applies to.
Symptoms
When you create a job planning line in Microsoft Dynamics NAV 5.0, the value in the Direct Unit Cost (LCY) field is incorrect. When this problem occurs, the value uses a foreign currency instead of using a local currency.
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 5.0 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.
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.
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.
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 apply this hotfix, change the code in the Job Transfer Line codeunit (1004). To do this, follow these steps:
To apply this hotfix, change the code in the Job Transfer Line codeunit (1004). To do this, follow these steps:
1. Add a new global variable as follows:
CurrencyExchRate : Record 330
2. Change the code in the FromPurchaseLineToJnlLine function as follows.
Existing code
...
IF Type = Type::Item THEN BEGIN
Item.GET("No.");
IF Item."Costing Method" = Item."Costing Method"::Standard THEN
JobJnlLine.VALIDATE("Unit Cost (LCY)",Item."Standard Cost")
ELSE
JobJnlLine.VALIDATE("Unit Cost (LCY)","Unit Cost (LCY)")
END ELSE
JobJnlLine.VALIDATE("Unit Cost (LCY)","Unit Cost (LCY)");JobJnlLine."Direct Unit Cost (LCY)" := "Direct Unit Cost";JobJnlLine."Unit Price (LCY)" := "Job Unit Price (LCY)";
JobJnlLine."Unit Price" := "Job Unit Price";JobJnlLine."Line Discount %" := "Job Line Discount %";
...Replacement code
...
IF Type = Type::Item THEN BEGIN
Item.GET("No.");
IF Item."Costing Method" = Item."Costing Method"::Standard THEN
JobJnlLine.VALIDATE("Unit Cost (LCY)",Item."Standard Cost")
ELSE
JobJnlLine.VALIDATE("Unit Cost (LCY)","Unit Cost (LCY)")
END ELSE
JobJnlLine.VALIDATE("Unit Cost (LCY)","Unit Cost (LCY)");// Add the following line.
IF PurchLine."Currency Code" = '' THENJobJnlLine."Direct Unit Cost (LCY)" := "Direct Unit Cost"// Add the following lines.
ELSE
JobJnlLine."Direct Unit Cost (LCY)" := CurrencyExchRate.ExchangeAmtFCYToLCY(
PurchHeader."Posting Date",
PurchLine."Currency Code",
"Direct Unit Cost",
PurchHeader."Currency Factor");JobJnlLine."Unit Price (LCY)" := "Job Unit Price (LCY)";
JobJnlLine."Unit Price" := "Job Unit Price";JobJnlLine."Line Discount %" := "Job Line Discount %";
...
Prerequisites
No prerequisites are required.
No prerequisites are required.
Removal information
You cannot remove this hotfix.
You cannot remove this hotfix.
Status
Applies to
• Microsoft Dynamics NAV 5.0
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Log ind
Du kan betale med
