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.

The net profit or the net loss is not reversed by the Close/Open Balance Sheet report when the net profit or the net loss is calculated and posted by using the Close Income Statement report in the Italian version of Microsoft Dynamics NAV


View products that this article applies to.

Rapidly Published articles provide information directly from within the Microsoft support organization. The information that is contained herein is created in response to emerging or unique topics, or is intended to supplement other Knowledge Base information.

↑ Back to the top


This article applies to Microsoft Dynamics NAV for the Italian (it) language locale.

↑ Back to the top


Symptoms

When the net profit or the net loss is calculated and posted by using the Close Income Statement report in the Italian version of Microsoft Dynamics NAV, the net profit or the net loss is not reversed by the Close/Open Balance Sheet report.

This problem occurs in the following products:
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
  • The Italian version of Microsoft Dynamics NAV 2009
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1

↑ 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 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, follow these steps:
  1. Change the following key in the G/L Entry table (17) as follows:
    Existing key
    • Key: G/L Account No.,Posting Date,Bal. Account No.
    • SumIndexFields: Amount,Debit Amount,Credit Amount,Additional-Currency Amount,Add.-Currency Debit Amount,Add.-Currency Credit Amount
    Replacement key
    • Key: G/L Account No.,Posting Date,Bal. Account No.,Transaction No.
    • SumIndexFields: Amount,Debit Amount,Credit Amount,Additional-Currency Amount,Add.-Currency Debit Amount,Add.-Currency Credit Amount
  2. Change the following key in the G/L Entry table (17) as follows:
    Existing key
    • Key: G/L Account No.,Business Unit Code,Global Dimension 1 Code,Global Dimension 2 Code,Close Income Statement Dim. ID,Posting Date,Bal. Account No.
    • SumIndexFields: Amount,Debit Amount,Credit Amount,Additional-Currency Amount,Add.-Currency Debit Amount,Add.-Currency Credit Amount
    Replacement key
    • Key: G/L Account No.,Business Unit Code,Global Dimension 1 Code,Global Dimension 2 Code,Close Income Statement Dim. ID,Posting Date,Bal. Account No.,Transaction No.
    • SumIndexFields: Amount,Debit Amount,Credit Amount,Additional-Currency Amount,Add.-Currency Debit Amount,Add.-Currency Credit Amount
  3. Add a global variable in the Close/Open Balance Sheet report (12113), and then specify the variable as follows:
    • Name:CloseTransactionNo
    • DataType:Integer
  4. Add a local variable in the Integer - OnAfterGetRecord trigger in the Close/Open Balance Sheet report (12113), and then specify the variable as follows:
    • Name:CloseGLEntry
    • DataType:Record
    • Subtype:G/L Entry
  5. Change the code in the Integer - OnAfterGetRecord trigger in the Close/Open Balance Sheet report (12113) as follows:
    Existing code
    ...
    IF Number = 1 THEN BEGIN
    GenJnlLine."Journal Template Name" := ClTemplateName;
    GenJnlLine."Journal Batch Name" := ClBatchName;
    END ELSE BEGIN
    GenJnlLine."Journal Template Name" := OpTemplateName;
    GenJnlLine."Journal Batch Name" := OpBatchName;
    END;
    ...
    Replacement code
    ...
    IF Number = 1 THEN BEGIN
    GenJnlLine."Journal Template Name" := ClTemplateName;
    GenJnlLine."Journal Batch Name" := ClBatchName;
    END ELSE BEGIN
    GenJnlLine."Journal Template Name" := OpTemplateName;
    GenJnlLine."Journal Batch Name" := OpBatchName;

    // Add the following lines.
    IF GLSetup."Additional Reporting Currency" <> '' THEN
    IF CloseGLEntry.FINDLAST THEN
    CloseTransactionNo := CloseGLEntry."Transaction No.";
    // End of the lines.
    ...
  6. Change the code in the G/L Entry - OnPreDataItem trigger in the Close/Open Balance Sheet report (12113) as follows:
    Existing code
    ...
    IF ClosePerBusUnit OR ClosePerGlobalDim1 OR ClosePerGlobalDim2 OR NOT ClosePerGlobalDimOnly THEN
    SETCURRENTKEY(
    "G/L Account No.","Business Unit Code",
    "Global Dimension 1 Code","Global Dimension 2 Code","Close Income Statement Dim. ID",

    // Delete the following line.
    "Posting Date","Bal. Account No.")

    ELSE

    // Delete the following lines.
    SETCURRENTKEY("G/L Account No.","Posting Date","Bal. Account No.");
    IF Integer.Number = 2 THEN
    SETFILTER("Bal. Account No.",'<>%1',ClAccNo);
    // End of the lines.

    EntryNoAmountBuf.DELETEALL;

    CLEAR(DimBufMgt2);
    ...
    Replacement code
    ...
    IF ClosePerBusUnit OR ClosePerGlobalDim1 OR ClosePerGlobalDim2 OR NOT ClosePerGlobalDimOnly THEN
    SETCURRENTKEY(
    "G/L Account No.","Business Unit Code",
    "Global Dimension 1 Code","Global Dimension 2 Code","Close Income Statement Dim. ID",

    // Add the following line.
    "Posting Date","Bal. Account No.","Transaction No.")

    ELSE

    // Add the following line.
    SETCURRENTKEY("G/L Account No.","Posting Date","Bal. Account No.","Transaction No.");

    SETRANGE("Posting Date",FiscalYearStartDate,FiscYearClosingDate);
    // Add the following lines.
    IF (GLSetup."Additional Reporting Currency" <> '') AND (Integer.Number = 2) THEN
    IF CloseTransactionNo <> 0 THEN
    SETFILTER("Transaction No.",'<>%1',CloseTransactionNo);
    // End of the lines.

    EntryNoAmountBuf.DELETEALL;

    CLEAR(DimBufMgt2);
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
  • The Italian version of Microsoft Dynamics NAV 2009
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1

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


MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 979075
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 294