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. The Payment Order report displays incorrect beneficiary names and beneficiary addresses in the Swiss version of Microsoft Dynamics NAV 2009 with SP1

The Payment Order report displays incorrect beneficiary names and beneficiary addresses in the Swiss version of Microsoft Dynamics NAV 2009 with SP1

View products that this article applies to.

RAPID PUBLISHING 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 following countries and language locales.
  • French (Switzerland) (fr-ch)
  • German (Switzerland) (de-ch)
  • Italian (Switzerland) (it-ch)

↑ Back to the top

Symptoms

Consider the following scenario in the Swiss version of Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1):

  • You have two banks defined in two payment forms in a staff card.
  • You define different beneficiary names and beneficiary addresses in two payment forms.
  • You run the "Payment Order" report from the salary payment order.

In this scenario, the "Payment Order" report displays the same beneficiary name and the beneficiary address for two payment forms. However, you expect that the "Payment Order" report displays the corresponding beneficiary name and the corresponding beneficiary address.

↑ 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 Salary Payment Order report (3010606) as follows.


To do this, follow these steps:
  1. Add the following global variables as follows:
     ChristiannameName2Text[61]
            BenAdr2@1150022Text[30]
            BenCity2@1150023Text[30]

  2. Change the code in the Salary Entry - OnAfterGetRecord trigger as follows:
    Existing code
    …
    // Not printing if Amt 0 or Cash.
    IF (Staff."Payment Form 2" = Staff."Payment Form 2"::"Cash Payment") OR (NetPayment2 = 0) THEN
      Display2 := FALSE;//CurrReport.SHOWOUTPUT(FALSE)
    IF Staff."Beneficiary Name 2" = '' THEN BEGIN
      ChristiannameName := Staff."Christian Name" + ' ' + Staff.Name;
      BenAdr := Staff.Address;
      BenCity := Staff."Post Code" + ' ' + Staff.City;
    END ELSE BEGIN
      ChristiannameName := Staff."Beneficiary Name 2";
      BenAdr := Staff."Beneficiary Address 2";
      BenCity := '';
    END;
    RecordCount := RecordCount + 1;       // to count number of data items
    …
    Replacement code
    …
    // Not printing if Amt 0 or Cash.
    IF (Staff."Payment Form 2" = Staff."Payment Form 2"::"Cash Payment") OR (NetPayment2 = 0) THEN
      Display2 := FALSE;//CurrReport.SHOWOUTPUT(FALSE)
    IF Staff."Beneficiary Name 2" = '' THEN BEGIN
      ChristiannameName2 := Staff."Christian Name" + ' ' + Staff.Name;
      BenAdr2 := Staff.Address;
      BenCity2 := Staff."Post Code" + ' ' + Staff.City;
    END ELSE BEGIN
      ChristiannameName2 := Staff."Beneficiary Name 2";
      BenAdr2 := Staff."Beneficiary Address 2";
      BenCity2 := '';
    END;
    RecordCount := RecordCount + 1;       // to count number of data items
    …
  3. Change the code in "Salary Entry, Body (2)" section as follows:
    Existing code
    { 1150019;TextBox   ;0    ;0    ;4500 ;423  ;SourceExpr=ChristiannameName;
                                                               DataSetFieldName=ChristiannameName_Control44 }
                  { 1150020;TextBox   ;0    ;423  ;4500 ;423  ;SourceExpr=BenAdr;
                                                               DataSetFieldName=BenAdr_Control46 }
                  { 1150021;TextBox   ;0    ;846  ;4500 ;423  ;SourceExpr=BenCity;
                                                               DataSetFieldName=BenCity_Control48 }
    Replacement code
     { 1150019;TextBox   ;0    ;0    ;4500 ;423  ;SourceExpr=ChristiannameName2;
                                                               DataSetFieldName=ChristiannameName_2 }
                  { 1150020;TextBox   ;0    ;423  ;4500 ;423  ;SourceExpr=BenAdr2;
                                                               DataSetFieldName=BenAdr_2 }
                  { 1150021;TextBox   ;0    ;846  ;4500 ;423  ;SourceExpr=BenCity2;
                                                               DataSetFieldName=BenCity_2 }

Prerequisites

You must have the Swiss version of Microsoft Dynamics NAV 2009 with Service Pack 1 installed to apply this hotfix.

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, kbmbspayroll, kbmbspartner, kbsurveynew, kb, kbnotautohotfix, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 978414
Revision : 2
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 269