You cannot change or delete a sales order or a purchase order when it is in open status in a certain scenario in the North American version of Microsoft Dynamics NAV 2009

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)

Symptoms

Assume that you post a prepayment invoice for a sales order or a purchase order in the North American version of Microsoft Dynamics NAV 2009. You post a partial shipment and invoice for the order, and then you post a prepayment credit memo for the order. In this situation, after you reopen the order, you cannot change any fields in the order lines or delete the order.
This problem occurs after you apply hotfix 2507996, hotfix 2159928 and hotfix 2665650.
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


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.



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:

Change the code in the

  1. Create a new local variable in the UpdateAmountsfunction in the Sales Line table (table 37), and then specify the variable as follows:

    • Name: SalesCrMemoHdr

    • DataType: Record

    • Subtype: Sales CR.Memo Header

  2. Change the code in the UpdateAmountsfunction in the Sales Line table (table 37) as follows:
    Existing code

    ...
    THEN
    CustCheckCreditLimit.SalesLineCheck(Rec);
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Delete 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.

    CalcPrepaymentToDeduct;
    ...

    Replacement code

    ... 
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Add the following lines.
    IF Quantity < xRec.Quantity THEN BEGIN
    SalesCrMemoHdr.SETRANGE("Prepayment Order No.","Document No.");
    SalesCrMemoHdr.SETCURRENTKEY(SalesCrMemoHdr."Prepayment Order No.");
    IF SalesCrMemoHdr.FINDFIRST THEN BEGIN
    SalesCrMemoHdr.CALCFIELDS(Amount);
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Line Amount" <> (xRec."Line Amount" - (SalesCrMemoHdr.Amount * 100 / "Prepayment %")))
    THEN
    FIELDERROR("Line Amount",STRSUBSTNO(Text050,xRec."Line Amount"));
    END;
    END;
    // End of the lines.

    CalcPrepaymentToDeduct;
    ...
  3. Change the code in the Quantity - OnValidate trigger in the Purchase Line table (table 39) as follows:
    Existing code

    ...TestStatusOpen;

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

    IF "Drop Shipment" AND ("Document Type" <> "Document Type"::Invoice) THEN
    ERROR(
    Text001,
    FIELDCAPTION(Quantity),"Sales Order No.");
    ...

    Replacement code

    ...TestStatusOpen;
    IF "Drop Shipment" AND ("Document Type" <> "Document Type"::Invoice) THEN
    ERROR(
    Text001,
    FIELDCAPTION(Quantity),"Sales Order No.");
    ...
  4. Create a new local variable in the UpdateAmountsfunction in the Purchase Line table (table 39), and then specify the variable as follows:

    • Name: PurchCrMemoHeader

    • DataType: Record

    • Subtype: Purch Cr.Memo Hdr.

  5. Change the code in the UpdateAmounts function in the Purchase Line table (table 39) as follows:
    Existing code

    ...
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Delete 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.

    CalcPrepaymentToDeduct;
    ...

    Replacement code

    ... 
    IF Type = Type::"Charge (Item)" THEN
    UpdateItemChargeAssgnt;

    // Add the following lines.
    IF Quantity < xRec.Quantity THEN BEGIN
    PurchCrMemoHeader.SETRANGE("Prepayment Order No.","Document No.");
    PurchCrMemoHeader.SETCURRENTKEY("Prepayment Order No.");
    IF PurchCrMemoHeader.FINDFIRST THEN BEGIN
    PurchCrMemoHeader.CALCFIELDS(Amount);
    IF ("Prepmt. Amt. Inv." <> 0) AND
    ("Line Amount" <> (xRec."Line Amount" - (PurchCrMemoHeader.Amount * 100 / "Prepayment %")))
    THEN
    FIELDERROR("Line Amount",STRSUBSTNO(Text045,xRec."Line Amount"));
    END;
    END;
    // End of the lines.

    CalcPrepaymentToDeduct;
    ...


Prerequisites

You must have one of the following products installed with hotfix 2507996, hotfix 2159928 and hotfix 2665650 applied 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

For more information about hotfix 2507996, click the following article number to view the article in the Microsoft Knowledge Base:

2507996 "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 For more information about hotfix 2159928, click the following article number to view the article in the Microsoft Knowledge Base:

2159928 The created general ledger entries are incorrect when you post a sales order in Microsoft Dynamics NAV 2009 Service Pack 1 For more information about hotfix 2665650, click the following article number to view the article in the Microsoft Knowledge Base:

2665650 "Currency Code does not exist" error message when you post a prepayment credit memo for a sales order that has a partial shipment and invoice posted in Microsoft Dynamics NAV 2009

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.

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×