The system does not roll back the quantity of kit component if an error occurs after you change the quantity in the BOM Journal line 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–U.S. (en-us)

  • Spanish–Mexico (es-mx)

  • French-Canada (fr-ca)

Symptoms

Assume that an error occurs after you change the value in the Quantity field in the BOM Journal line in the North American version of Microsoft Dynamics NAV 2009 R2 and of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). Then, the system reverts the value to its original quantity in the Quantity field in the BOM Journal line. However, the system does not roll back the Quantity field in the Kit BOM Journal line as expected.

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. However, 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 BOM Journal Linetable (89). To do this, follow these steps:

    1. Change the code in the OnModify trigger as follows:
      Existing code

      ...
      ReserveBOMJnlLine.VerifyChange(Rec,xRec);
      ...

      Replacement code

      ...
      // Add the following line.
      RecheckKitBOM;

      ReserveBOMJnlLine.VerifyChange(Rec,xRec);
      ...
    2. Create a new procedure as follows:

      PROCEDURE RecheckKitBOM@1462001();
      BEGIN
      IF ("Entry Type" = "Entry Type"::Disassembly) OR (CurrFieldNo = 0) THEN
      KitManagement.MaintainKitBOM(Rec,TempKitBOMJnlLine,FALSE)
      ELSE
      KitManagement.MaintainKitBOM(Rec,TempKitBOMJnlLine,TRUE);
      END;
  2. Change the code in the BOM Journal form (109). To do this, follow these steps:

    1. Change the code in the <Control25> - OnPush trigger as follows:
      Existing code

      ...
      CODEUNIT.RUN(CODEUNIT::"BOM Jnl.-Post",Rec);
      CurrentJnlBatchName := GETRANGEMAX("Journal Batch Name");
      CurrForm.UPDATE(FALSE);
      ...

      Replacement code

      ...
      // Add the following line.
      RecheckKitBOM;

      CODEUNIT.RUN(CODEUNIT::"BOM Jnl.-Post",Rec);
      CurrentJnlBatchName := GETRANGEMAX("Journal Batch Name");
      CurrForm.UPDATE(FALSE);
      ...
    2. Change the code in the <Control26> - OnPush trigger as follows:
      Existing code

      ...
      CODEUNIT.RUN(CODEUNIT::"BOM Jnl.-Post+Print",Rec);
      CurrentJnlBatchName := GETRANGEMAX("Journal Batch Name");
      CurrForm.UPDATE(FALSE);
      ...

      Replacement code

      ...
      // Add the following line.
      RecheckKitBOM;

      CODEUNIT.RUN(CODEUNIT::"BOM Jnl.-Post+Print",Rec);
      CurrentJnlBatchName := GETRANGEMAX("Journal Batch Name");
      CurrForm.UPDATE(FALSE);
      ...
  3. Create a new menu button on the Postingmenu (Control23)and specify the menu button as follows:

    ID=1000;
    CaptionML=ENU=Re-Check BOM Kit Lines;
    OnPush=BEGIN
    RecheckKitBOM;
    END;

Note The code fix corrects the scenario. Additionally, it adds a new menu button to the Posting menu. You can use the button to recheck the BOM Kit lines after any update that results in an error. You can also use this button as an option to verify that the system performs the posting based on the available data. The new menu button can only be used if an error occurs after the system validates the quantity.

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.

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!

×