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.

"Currency Code does not exist" error message when you run the Post Prepayment Credit Memo function on a sales order in the North American version of Microsoft Dynamics NAV 2009


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • English (Canada) (en-ca)
  • English (United States) (en-us)
  • Spanish (Mexico) (es-mx)
  • French (Canada) (fr-ca)

↑ Back to the top


Symptoms

Assume that you post a prepayment invoice for a sales order in the North American version of Microsoft Dynamics NAV 2009. You reopen the sales order and then change the unit price or the prepayment percentage value in the sales order. In this situation, when you run the Post Prepayment Credit Memo function on the sales order, you receive the following error message:
Currency Code does not exist.

This problem occurs in the following products:
  • The North American version of Microsoft Dynamics NAV 2009 R2
  • The North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

↑ 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. Apply hotfix 979109.
    For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    979109 Error message when you try to invoice a sales order in Microsoft Dynamics NAV 2009 Service Pack 1: "Currency Code '' does not exist"
  2. Change the code in the Unit Price - OnValidate trigger in the Sales Line table (37) as follows:
    Existing code
    ...
    TestStatusOpen;
    VALIDATE("Line Discount %");
    ...
    Replacement code
    ...
    TestStatusOpen;

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Unit Price" <> xRec."Unit Price")
    THEN
    FIELDERROR("Unit Price",STRSUBSTNO(Text050,xRec."Unit Price"));
    // End of the lines.

    VALIDATE("Line Discount %");
    ...
  3. Change the code in the Prepayment % - OnValidate trigger in the Sales Line table (37) as follows:
    Existing code
    ...
    TestStatusOpen;
    IF Type <> Type::" " THEN
    UpdateAmounts;
    ...
    Replacement code
    ...
    TestStatusOpen;

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Prepayment %" <> xRec."Prepayment %")
    THEN
    FIELDERROR("Prepayment %",STRSUBSTNO(Text050,xRec."Prepayment %"));
    // End of the lines.

    IF Type <> Type::" " THEN
    UpdateAmounts;
    ...
  4. Change the code in the UpdateAmounts function in the Sales Line table (37) as follows:
    Existing code
    ...
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;
    ...
    Replacement code
    ...
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Line Amount" <> xRec."Line Amount")
    THEN
    FIELDERROR("Line Amount",STRSUBSTNO(Text050,xRec."Line Amount"));
    // End of the lines.
    ...
  5. Change the code in the Direct Unit Cost - OnValidate trigger in the Purchase Line table (39) as follows:
    Existing code
    ...
    VALIDATE("Line Discount %");
    ...
    Replacement code
    ...
    VALIDATE("Line Discount %");

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Direct Unit Cost" <> xRec."Direct Unit Cost")
    THEN
    FIELDERROR("Direct Unit Cost",STRSUBSTNO(Text045,xRec."Direct Unit Cost"));
    // End of the lines.
    ...
  6. Change the code in the Prepayment % - OnValidate trigger in the Purchase Line table (39) as follows:
    Existing code
    ...
    TestStatusOpen;
    IF Type <> Type::" " THEN
    UpdateAmounts;
    ...
    Replacement code
    ...
    TestStatusOpen;

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Prepayment %" <> xRec."Prepayment %")
    THEN
    FIELDERROR("Prepayment %",STRSUBSTNO(Text045,xRec."Prepayment %"));
    // End of the lines.

    IF Type <> Type::" " THEN
    UpdateAmounts;
    ...
  7. Change the code in the UpdateAmounts function in the Purchase Line table (39) as follows:
    Existing code
    ...
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;
    ...
    Replacement code
    ...
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Add the following lines.
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Line Amount" <> xRec."Line Amount")
    THEN
    FIELDERROR("Line Amount",STRSUBSTNO(Text045,xRec."Line Amount"));
    // End of the lines.
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The North American version of Microsoft Dynamics NAV 2009 R2
  • The North American version of Microsoft Dynamics NAV 2009 Service Pack 1

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

↑ Back to the top

Article Info
Article ID : 2507996
Revision : 2
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 328