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. Cost adjustment is posted to an incorrect losses or gains account in general ledger in the Portuguese version of Microsoft Dynamics NAV 2009

Cost adjustment is posted to an incorrect losses or gains account in general ledger in the Portuguese version of Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Portuguese (pt) language locale.

↑ Back to the top

Symptoms

If several lines are recorded referring to different inventory posting groups and different losses or gains account in the physical inventory journal in the Portuguese version of Microsoft Dynamics NAV 2009, cost adjustment is posted to an incorrect losses or gains account in general ledger.

This problem occurs in the following products:
  • The Portuguese version of Microsoft Dynamics NAV 2009 R2
  • The Portuguese 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 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. 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 Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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 GetPhysicalInv function in the Item Jnl.-Post Line Codeunit (22) as follows:

Existing code 1

...
VAR
PhysInvLedgEntry@1110002 : Record 281;
IsPhysInventory@1110003 : Boolean;
PrevAdjAcc@1110004 : Text[20];
GLEntry@1110005 : Record 17;
BEGIN
WITH ValueEntry DO BEGIN
IsPhysInventory := FALSE;
PhysInvLedgEntry.SETCURRENTKEY("Document No.","Posting Date");
PhysInvLedgEntry.SETRANGE(PhysInvLedgEntry."Document No.","Document No.");
...

Replacement code 1

...
VAR
PhysInvLedgEntry@1110002 : Record 281;
IsPhysInventory@1110003 : Boolean;
PrevAdjAcc@1110004 : Text[20];
GLEntry@1110005 : Record 17;

// Add the following line.
GLItemLedgRelation@1110006 : Record 5823;
// End of the added line.

BEGIN
WITH ValueEntry DO BEGIN
IsPhysInventory := FALSE;
PhysInvLedgEntry.SETCURRENTKEY("Document No.","Posting Date");
PhysInvLedgEntry.SETRANGE(PhysInvLedgEntry."Document No.","Document No.");
...

Existing code 2

...
IsPhysInventory := FALSE;
 PhysInvLedgEntry.SETCURRENTKEY("Document No.","Posting Date");
PhysInvLedgEntry.SETRANGE(PhysInvLedgEntry."Document No.","Document No.");
IF PhysInvLedgEntry.FINDSET THEN BEGIN
IsPhysInventory := TRUE;

// Delete the following lines.
GLEntry.SETCURRENTKEY("Document No.","Posting Date");
GLEntry.SETRANGE(GLEntry."Document No.","Document No.");
IF GLEntry.FINDSET THEN BEGIN
GLEntry.FINDLAST;
IF CalledFromAdjustment THEN
PrevAdjAcc := GLEntry."G/L Account No.";
END;
// End of the deleted lines.

END;
  
IF (("Item Ledger Entry Type" IN ["Item Ledger Entry Type"::"Negative Adjmt.","Item Ledger Entry Type"::"Positive Adjmt."]) AND
("Entry Type" = "Entry Type"::"Direct Cost") AND Adjustment AND IsPhysInventory) OR ItemJnlLine."Phys. Inventory" THEN
InvtPost.GetPhysicalInventory(TRUE,ItemJnlLine."Location Code",ItemJnlLine."Inventory Posting Group",PrevAdjAcc)
...

Replacement code 2

...
IsPhysInventory := FALSE;
PhysInvLedgEntry.SETCURRENTKEY("Document No.","Posting Date");
PhysInvLedgEntry.SETRANGE(PhysInvLedgEntry."Document No.","Document No.");
IF PhysInvLedgEntry.FINDSET THEN BEGIN
IsPhysInventory := TRUE;

// Add the following lines.
IF CalledFromAdjustment THEN BEGIN
GLItemLedgRelation.SETCURRENTKEY("Value Entry No.");
GLItemLedgRelation.SETRANGE("Value Entry No.",ItemJnlLine."Applies-to Value Entry");
IF GLItemLedgRelation.FINDLAST THEN BEGIN
GLEntry.GET(GLItemLedgRelation."G/L Entry No.");
PrevAdjAcc := GLEntry."G/L Account No.";
END;
END;
// End of the added lines.

END;
  
IF (("Item Ledger Entry Type" IN ["Item Ledger Entry Type"::"Negative Adjmt.","Item Ledger Entry Type"::"Positive Adjmt."]) AND
("Entry Type" = "Entry Type"::"Direct Cost") AND Adjustment AND IsPhysInventory) OR ItemJnlLine."Phys. Inventory" THEN
InvtPost.GetPhysicalInventory(TRUE,ItemJnlLine."Location Code",ItemJnlLine."Inventory Posting Group",PrevAdjAcc)
...

Prerequisites

You must have one of the following products installed and the following hotfix applied to apply this hotfix:
  • The Portuguese version of Microsoft Dynamics NAV 2009 R2
  • The Portuguese version of Microsoft Dynamics NAV 2009 Service Pack 1
Additionally, you must have hotfix 2845151 installed to apply this hotfix. For more information about hotfix 2845151, click the following article number to view the article in the Microsoft Knowledge Base:
2845151 losses in inventory is not considered in the Portuguese version of Microsoft Dynamics NAV 2009

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 Usefor other considerations.

↑ Back to the top

Keywords: kbmbspartner, kbqfe, kbmbsmigrate, kbmbscodefix, kbsurveynew, kbmbsquickpub, kbnoloc, kb

↑ Back to the top

Article Info
Article ID : 2845192
Revision : 1
Created on : 1/7/2017
Published on : 5/22/2013
Exists online : False
Views : 264