This article applies to Microsoft Dynamics NAV for the Portuguese (pt) language locale.
Symptoms
Assume that the last line of a purchase order only has the Description field specified in the Portuguese version of Microsoft Dynamics NAV 2009 R2 and of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). When you run the Fill function on Liquidity Journal, you enable the Group by Order option. In this situation, the account number is blank. However, you expect the Account Number field to be filled with the corresponding vendor number.
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 Purchase Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
Existing code...
"Reason Code" := PurchHeader."Reason Code"; "Account Type" := LiqLine2."Account Type"::Vendor; // Delete the following line. "Account Number" := "Purchase Line"."Buy-from Vendor No."; // End of the line. "Liquidity Account No." := LiqSetup."Purch. Order Liq. Account No."; ...Replacement code
...
"Reason Code" := PurchHeader."Reason Code"; "Account Type" := LiqLine2."Account Type"::Vendor; // Add the following line. "Account Number" := PurchHeader."Buy-from Vendor No."; // End of the line. "Liquidity Account No." := LiqSetup."Purch. Order Liq. Account No."; ... -
Change the code in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
Existing code...
"Reason Code" := SalesHeader."Reason Code"; "Account Type" := LiqLine2."Account Type"::Customer; // Delete the following line. "Account Number" := "Sales Line"."Sell-to Customer No."; // End of the line. "Liquidity Account No." := LiqSetup."Sales Order Liq. Account No."; Description := COPYSTR(STRSUBSTNO(Text1140026,SalesHeader."Sell-to Customer Name", ...Replacement code
...
"Reason Code" := SalesHeader."Reason Code"; "Account Type" := LiqLine2."Account Type"::Customer; // Add the following line. "Account Number" := SalesHeader."Sell-to Customer No."; // End of the line. "Liquidity Account No." := LiqSetup."Sales Order Liq. Account No."; Description := COPYSTR(STRSUBSTNO(Text1140026,SalesHeader."Sell-to Customer Name", ... -
Change the code in the Service Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
Existing code...
"Gen. Bus. Posting Group" := "Service Line"."Gen. Bus. Posting Group"; "Account Type" := LiqLine2."Account Type"::Customer; // Delete the following line. "Account Number" := "Service Line"."Customer No."; // End of the line. "Liquidity Account No." := LiqSetup."Service Liq. Account No."; Description := COPYSTR(STRSUBSTNO(Text1140026,ServiceHeader.Name, ...Replacement code
...
"Gen. Bus. Posting Group" := "Service Line"."Gen. Bus. Posting Group"; "Account Type" := LiqLine2."Account Type"::Customer; // Add the following line. "Account Number" := ServiceHeader."Customer No."; // End of the line. "Liquidity Account No." := LiqSetup."Service Liq. Account No."; Description := COPYSTR(STRSUBSTNO(Text1140026,ServiceHeader.Name, ...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Portuguese version of Microsoft Dynamics NAV 2009 R2
-
The Portuguese 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.