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. Statement of Indirect Expenses (PA.470.00) report prints blank in Microsoft Dynamics SL

Statement of Indirect Expenses (PA.470.00) report prints blank in Microsoft Dynamics SL

Symptoms

Consider the following scenario in Project Allocator in Microsoft Dynamics SL:
  • You have a Microsoft Dynamics SL application database that contains multiple companies.
  • You log on to one company, and you create an allocation group on the Allocation Group Maintenance (01.290.00) screen that has a value in the Pool Sequence box that is greater than zero.
  • You log on to a different company and create a different allocation group on the Allocation Group Maintenance (01.290.00) screen that has a value in the Pool Sequence box that is greater than zero.
  • You log on to the first company again, and then you run the Indirect Rate Calculator (AL.IRC.00) process.
  • You log on to the second company again, and then you run the Indirect Rate Calculator (AL.IRC.00) process.
  • You try to reprint the Statement of Indirect Expenses (PA.470.00) report for the first company from the Indirect Rate Calculator (AL.IRC.00) screen.
In this scenario, you notice that the report is printed blank. You expect the Statement of Indirect Expenses (PA.470.00) report to be populated for the first company.

This problem occurs because running the Indirect Rate Calculator (AL.IRC.00) process for the second company after it has already been run for the first company causes all the records in the PJPOOLH table to be deleted for the first company. 


↑ Back to the top

Resolution

Hotfix information for Microsoft Dynamics SL 

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics SL Service Pack that contains this hotfix as specified in the "Status" section in this article.

To resolve this problem, click the "View and request hotfix downloads" link at the top of this article to obtain the hotfix.

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.


Microsoft Dynamics SL 7.0 Feature Pack 1 (FP1)
Changed filesDateFile version
ALIRC00.exe 19-Jul 20107.3.40723
GRRSW00.exe19-Jul 20107.3.40723
BUG21730AL.sql19-Jul 2010
PA470.rpt23-Jul 2010

Installation information

Install this hotfix by following the installation instructions that are included in the hotfix download.

Prerequisites

For information about the prerequisites for this hotfix, see the installation instructions that are included in the hotfix download.

Restart requirement

If you are prompted, restart the computer after you install the 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.

This problem was reported as issue numbers 21730 and 21731.


↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbsolomon, kbhotfixserver, kbqfe, kbmbsmigrate, kbmbspartner, kbbug, kb, kbtshoot, kbexpertisebeginner, kbexpertiseinter, kbautohotfix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2294649
Revision : 3
Created on : 2/3/2017
Published on : 2/3/2017
Exists online : False
Views : 101