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. Project Inventory commitments that are displayed in "Project Net Profits Inquiry (PA.PNR.00)" are not consumed when inventory is issued for a shipment of a project-related Sales Order that has an OU order type that auto creates a Purchase Order

Project Inventory commitments that are displayed in "Project Net Profits Inquiry (PA.PNR.00)" are not consumed when inventory is issued for a shipment of a project-related Sales Order that has an OU order type that auto creates a Purchase Order

View products that this article applies to.

Symptoms

Consider the following scenario in Order Management in Microsoft Dynamics SL 2011:
  • In Sales Order Entry (40.100.00), you create a Sales Order by using an Order Type of OU.
  • In Receipt/Invoice Entry (04.010.00), you release the receipt that was created from the purchase order that was generated from the OU Sales Order.
  • In Shippers (40.110.00), you confirm the shipment for the OU Sales Order.
  • You print the Sales Journal (40.690.00) report.
  • In Release IN Batches (10.400.00), you release the batch that was created when you printed the Sales Journal report.
  • You open Project Net Profit (PA.PNR.00).

When you do this, you notice that the amount in the Commit column shows the amount on the Purchase Order. You expect the Commit amount would be reduced when the OU order was processed, and the inventory batch was released.

↑ 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 2011
Changed FilesDateFile Version
5040200.exe 06-Jan-20128.00.30106.00
5040500.exe 06-Jan-20128.00.30106.00
DMGDataAccess.dll 06-Jan-20128.00.30106.00
DMGDataServer.dll 06-Jan-20128.00.30106.00
DMGOrderTotals.dll 06-Jan-20128.00.30106.00
DMGPOReceiptBO.dll06-Jan-20128.00.30106.00
DMGPurchOrderBO.dll 06-Jan-20128.00.30106.00
DMGSalesOrderBO.dll 06-Jan-20128.00.30106.00
FMGCustomerBO.dll06-Jan-20128.00.30106.00
Microsoft.Dynamics.SL.Reporting.dll 06-Jan-20128.00.30106.00
SOLOMON.KERNEL.dll 06-Jan-20128.00.30106.00
SOLDB.dll06-Jan-20128.00.30106.00
SAFMENUSTRIP.dll 06-Jan-20128.00.30106.00
SWIMAPI.dll06-Jan-20128.00.30106.00
LLI.dll06-Jan-20128.00.30106.00
TOOLBARENU.dll 06-Jan-20128.00.30106.00
4440100.exe 06-Jan-20128.00.30106.00
4440500.exe 06-Jan-20128.00.30106.00
4440700.exe 06-Jan-20128.00.30106.00
1040000.exe 06-Jan-20128.00.30106.00
4010000.exe06-Jan-20128.00.30106.00
4011000.exe06-Jan-20128.00.30106.00
4011500.exe06-Jan-20128.00.30106.00
4011700.exe06-Jan-20128.00.30106.00
4017000.exe 06-Jan-20128.00.30106.00
4040000.exe 06-Jan-20128.00.30106.00
4060000.exe 06-Jan-20128.00.30106.00
4060001.exe 06-Jan-20128.00.30106.00
4061000.exe 06-Jan-20128.00.30106.00
4061001.exe 06-Jan-20128.00.30106.00
4069002.exe 06-Jan-20128.00.30106.00
6040000.exe06-Jan-20128.00.30106.00
6041000.exe06-Jan-20128.00.30106.00
ROI.exe 06-Jan-20128.00.30106.00
ROISRS.exe 06-Jan-20128.00.30106.00
1265010.exe06-Jan-20128.00.30106.00
QQVIE00.exe 06-Jan-20128.00.30106.00
9829000.exe06-Jan-20128.00.30106.00
Bug23964APP.sql15-Nov-2011
Bug23694SYS.sql 15-Nov-2011

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, refer to 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 number 23939.


This problem was first corrected in Microsoft Dynamics SL 2011 Service Pack 2.

↑ 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, kbtshoot, kbbug, kb, kbexpertisebeginner, kbexpertiseinter, kbautohotfix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2664253
Revision : 2
Created on : 1/31/2017
Published on : 1/31/2017
Exists online : False
Views : 251