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. You receive an error message when you issue more than two finance charge memos that have invoicing rounding lines in Microsoft Dynamics NAV 2009 SP1

You receive an error message when you issue more than two finance charge memos that have invoicing rounding lines in Microsoft Dynamics NAV 2009 SP1

View products that this article applies to.

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

↑ Back to the top

Symptoms

When you issue more than two finance charge memos that have invoicing rounding lines in Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1), you receive the following error message:
The following C/AL functions can be used only to a limited degree during write transactions because one or more tables will be locked.

Form.RunModal is not allowed in write transactions.

CodeUnit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := CodeUnit.Run()' is not allowed.

Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed.

DataPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'DataPort.RunModal(...,FALSE)' is allowed.

Use the COMMIT function to save the changes before this call, or structure the code differently.

↑ 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 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 install this hotfix, change the code in the following objects:
  • Issue Reminders report (190)
  • Issue Finance Charge Memos
     report (193)
  • Reminder-Issue codeunit (393)
  • FinChrgMemo-Issue codeunit (395)

To do this, follow these steps:
  1. Change code in the Reminder Header - OnAfterGetRecord trigger in the Issue Reminders report (190) as follows:
    Existing code
    ...
    RecordNo := RecordNo + 1;
    //UpdateReminderRounding("Reminder Header"); // Delete this line.
    CLEAR(ReminderIssue);
    ReminderIssue.Set("Reminder Header",ReplacePostingDate,PostingDateReq);
    IF NoOfRecords = 1 THEN BEGIN
    ....

    Replacement code
    ...
    RecordNo := RecordNo + 1;
    CLEAR(ReminderIssue);
    ReminderIssue.Set("Reminder Header",ReplacePostingDate,PostingDateReq);
    IF NoOfRecords = 1 THEN BEGIN
    ....

  2. Change code in the Finance Charge Memo Header - OnAfterGetRecord trigger in the Issue Finance Charge Memos
    report (193) as follows:
    Existing code 
    …
    RecordNo := RecordNo + 1;
    UpdateFinanceChargeRounding("Finance Charge Memo Header"); // Delete this line.
    CLEAR(FinChrgMemoIssue);
    FinChrgMemoIssue.Set("Finance Charge Memo Header",ReplacePostingDate,PostingDateReq);
    IF NoOfRecords = 1 THEN BEGIN
    ...
    Replacement code 
    …
    RecordNo := RecordNo + 1;
    CLEAR(FinChrgMemoIssue);
    FinChrgMemoIssue.Set("Finance Charge Memo Header",ReplacePostingDate,PostingDateReq);
    IF NoOfRecords = 1 THEN BEGIN
    ...
  3. Change code in the OnRun trigger in the Reminder-Issue codeunit (393) as follows:
    Existing code 
    …
    WITH ReminderHeader DO BEGIN
      IF (PostingDate <> 0D) AND (ReplacePostingDate OR ("Posting Date" = 0D)) THEN
        VALIDATE("Posting Date",PostingDate);
    ...
    Replacement code 
    ...
    WITH ReminderHeader DO BEGIN
      UpdateReminderRounding(ReminderHeader); // Add this line. 
      IF (PostingDate <> 0D) AND (ReplacePostingDate OR ("Posting Date" = 0D)) THEN
        VALIDATE("Posting Date",PostingDate);
    ...

  4. Change code in the OnRun trigger in the FinChrgMemo-Issue codeunit (395) as follows:
    Existing code 
    …
    WITH FinChrgMemoHeader DO BEGIN
      IF (PostingDate <> 0D) AND (ReplacePostingDate OR ("Posting Date" = 0D)) THEN
        VALIDATE("Posting Date",PostingDate);
    ...
    Replacement code 
    ...
    WITH FinChrgMemoHeader DO BEGIN
      UpdateFinanceChargeRounding(FinChrgMemoHeader); // Add this line. 
      IF (PostingDate <> 0D) AND (ReplacePostingDate OR ("Posting Date" = 0D)) THEN
        VALIDATE("Posting Date",PostingDate);
    ...

Prerequisites

You must have Microsoft Dynamics NAV 2009 SP1 installed to apply this hotfix:

Removal information

You cannot remove this hotfix.

↑ Back to the top

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

979086 The Adjust Exchange Rates report does not work as expected in Microsoft Dynamics NAV 2009

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

↑ Back to the top

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