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 run the Trial Balance Spread Periods report (10026) that crosses over a fiscal year closing period in the North American version Microsoft Dynamics NAV 2009. If you run the report that uses the weekly option, the balances in the report are incorrect. All closing entries are included in the weekly period that includes the cross over to the new fiscal year unexpectedly.
Note When you run the report that uses a time division of 1P or a time division of 1M, the system displays the monthly totals correctly, even if you run the report that crosses over a fiscal year closing period.
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 (SP1)

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 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:

  1. Add a new global variable in the Trial Balance, Spread Periods report (10026), and then specify the variable as follows:

    • Name: CloDate

    • DataType: Date

  2. Change the code in the Report - OnPreReport trigger in the Trial Balance, Spread Periods report (10026) as follows:
    Existing code

    ...
    CompanyInformation.GET;
    { set up the date ranges }
    FromDate := "G/L Account".GETRANGEMIN("Date Filter");
    ToDate := "G/L Account".GETRANGEMAX("Date Filter");
    PriorFromDate := CALCDATE('<-1Y>',FromDate);
    PriorToDate := CALCDATE('<-1Y>',ToDate);
    IF NOT PrintToExcel THEN
    "G/L Account".SETRANGE("Date Filter"); // since these are in the titles, they
    GLAccountFilter := "G/L Account".GETFILTERS; // do not have to be in the filter string
    ...

    Replacement code

    ...
    CompanyInformation.GET;
    { set up the date ranges }
    FromDate := "G/L Account".GETRANGEMIN("Date Filter");
    ToDate := "G/L Account".GETRANGEMAX("Date Filter");
    PriorFromDate := CALCDATE('<-1Y>',FromDate);
    PriorToDate := CALCDATE('<-1Y>',ToDate);

    // Add the following line.
    CloDate := FindClosingDate(ToDate);

    IF NOT PrintToExcel THEN
    "G/L Account".SETRANGE("Date Filter"); // since these are in the titles, they
    GLAccountFilter := "G/L Account".GETFILTERS; // do not have to be in the filter string
    ...
  3. Change the code in the G/L Account - OnAfterGetRecord trigger in the DataItem1 - <G/L Account> in the Trial Balance, Spread Periods report (10026) as follows:
    Existing code

    ...
    THEN BEGIN
    FOR i := 1 TO MaxColumns DO
    IF (ColumnFilter[i] <> '') THEN BEGIN

    // Delete the following line.
    SETFILTER("Date Filter",ColumnFilter[i]);

    CASE AmountType OF
    AmountType::"Actual Change":
    IF UseAddRptCurr THEN BEGIN
    CALCFIELDS("Additional-Currency Net Change");
    ...

    Replacement code

    ...
    THEN BEGIN
    FOR i := 1 TO MaxColumns DO
    IF (ColumnFilter[i] <> '') THEN BEGIN

    // Add the following lines.
    IF CloDate = 0D THEN
    SETFILTER("Date Filter",ColumnFilter[i])
    ELSE
    SETFILTER("Date Filter",STRSUBSTNO('%1&<>%2',ColumnFilter[i],CloDate));
    // End of the lines.

    CASE AmountType OF
    AmountType::"Actual Change":
    IF UseAddRptCurr THEN BEGIN
    CALCFIELDS("Additional-Currency Net Change");
    ...
  4. Add a new function in the Trial Balance, Spread Periods report (10026) as follows:

    NEW LOCAL PROCEDURE:
    FindClosingDate@1020000(ToDate@1020000 : Date) : Date;
    VAR
    AccountingPeriod@1020001 : Record 50;

    AccountingPeriod.SETFILTER("Starting Date",'..%1',ToDate);
    AccountingPeriod.SETRANGE(Closed,FALSE);
    AccountingPeriod.SETRANGE("New Fiscal Year",TRUE);
    IF AccountingPeriod.FINDLAST THEN
    EXIT(CLOSINGDATE(CALCDATE('-1D',AccountingPeriod."Starting Date")))
    ELSE
    EXIT(0D);


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.

Benötigen Sie weitere Hilfe?

Ihre Office-Fähigkeiten erweitern
Schulungen erkunden
Neue Funktionen als Erster erhalten
Microsoft Insider beitreten

War diese Information hilfreich?

Was hat Ihre Erfahrung beeinflusst?

Vielen Dank für Ihr Feedback!

×