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 function of the "Appl.-from Item Entry No." field works incorrectly when you perform sales return order that has a serial/lot tracked item in Microsoft Dynamics NAV 2009 Service Pack 1

The function of the "Appl.-from Item Entry No." field works incorrectly when you perform sales return order that has a serial/lot tracked item in Microsoft Dynamics NAV 2009 Service Pack 1

View products that this article applies to.

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

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1):
  • You have a sales return order that has a serial /lot tracked item.
  • You set value in the Appl.-from Item Entry No. field on the sales return order.
  • You run a cost adjustment for the item after posting a receipt for the sales return order.
  • You post the sales return order to invoice and then run the cost adjustment for the item again.

In this scenario, the function of the Appl.-from Item Entry No. field works incorrectly. Therefore, you find that the cost amount 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, change the code in the ForwardAppliedCost function in the Inventory Adjustment codeunit(5895) as follows:

Existing code

...
    WITH ItemLedgEntry DO BEGIN
  // Avoid stack overflow, if too many recursions
  IF Recursion THEN
    LevelNo[3] := LevelNo[3] + 1
  ELSE
    LevelNo[3] := 0;

  IF LevelNo[3] = MaxLevels THEN BEGIN
    SetAppliedEntryToAdjust(TRUE);
    LevelExceeded := TRUE;
    LevelNo[3] := 0;
    EXIT;
  END;

  UpDateWindow(WindowAdjmtLevel,WindowItem,WindowAdjust,LevelNo[3],WindowEntry);

  ForwardCostToOutbndEntries("Entry No.",Recursion,AppliedEntryToAdjust);

  ForwardCostToInbndTransEntries("Entry No.",Recursion);

  ForwardCostToInbndEntries("Entry No.");


  IF NOT IsOutbndConsump THEN
    UpdateAppliedEntryToAdjustBuf("Entry No.",AppliedEntryToAdjust);
  SetAppliedEntryToAdjust(FALSE);
END;      
...

Replacement code

...
  WITH ItemLedgEntry DO BEGIN
  // Avoid stack overflow, if too many recursions
  IF Recursion THEN
    LevelNo[3] := LevelNo[3] + 1
  ELSE
    LevelNo[3] := 0;

  IF LevelNo[3] = MaxLevels THEN BEGIN
    SetAppliedEntryToAdjust(TRUE);
    LevelExceeded := TRUE;
    LevelNo[3] := 0;
    EXIT;
  END;

  UpDateWindow(WindowAdjmtLevel,WindowItem,WindowAdjust,LevelNo[3],WindowEntry);

  ForwardCostToOutbndEntries("Entry No.",Recursion,AppliedEntryToAdjust);

  ForwardCostToInbndTransEntries("Entry No.",Recursion);

  ForwardCostToInbndEntries("Entry No.");

//Add the following lines.
  IF OutboundSalesEntryToAdjust(ItemLedgEntry) THEN
    AppliedEntryToAdjust := TRUE;
//End of the added lines.

  IF NOT IsOutbndConsump THEN
    UpdateAppliedEntryToAdjustBuf("Entry No.",AppliedEntryToAdjust);
  SetAppliedEntryToAdjust(FALSE);
END;  
...

In the Inventory Adjustment codeunit(5895), follow these steps:
  1. Add the OutboundSalesEntryToAdjust function.
  2. Add a parameter, and then specify the parameter as follows: 
    • Name:Item Ledger Entry
    • Data Type: Record
    • Subtype: Item Ledger Entry
     
  3. Set the return value type to Boolean. 
  4. Add two variables, and then specify the parameter as follows:
    • Name: ItemApplnEntry
      • Data Type: Record
      • Subtype: Item Applicaiton Entry
    • Name: InbndItemLedgEntry
      • Data Type:Record
      • Subtype: Item Ledger Entry
  5. Add the following code:
    ...
    IF NOT ItemLedgEntry.IsOutbndSale THEN
            EXIT(FALSE);

          WITH ItemApplnEntry DO BEGIN
            RESET;
            SETCURRENTKEY(
              "Outbound Item Entry No.","Item Ledger Entry No.","Cost Application","Transferred-from Entry No.");
            SETRANGE("Outbound Item Entry No.",ItemLedgEntry."Entry No.");
            SETFILTER("Item Ledger Entry No.",'<>%1',ItemLedgEntry."Entry No.");
            SETRANGE("Transferred-from Entry No.",0);
            IF FINDSET THEN
              REPEAT
                IF InbndItemLedgEntry.GET("Inbound Item Entry No.") THEN
                  IF NOT InbndItemLedgEntry."Completely Invoiced" THEN
                    EXIT(TRUE);
              UNTIL NEXT = 0;
          END;
    ...

In the Item Ledger Entry table (32), follow these steps:
  1. Add the IsOutbndSale global function.
  2. Set the return type to Boolean
  3. Add the following code:
    ...
    EXIT(("Entry Type" = "Entry Type"::Sale) AND NOT Positive);
    ...

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

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

↑ Back to the top

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