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. "qty. assigned must be 0 in item charge assignment" error message when you run the "Delete invoiced sales order" report in the French version of Microsoft Dynamics NAV 2009 SP1

"qty. assigned must be 0 in item charge assignment" error message when you run the "Delete invoiced sales order" report in the French version of Microsoft Dynamics NAV 2009 SP1

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the French (fr) language locale.

↑ Back to the top

Symptoms

In the French version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1), assume that you invoice and post a sales order. Then, when you run the "Delete invoiced sales order" report, you receive the following error message:
qty. assigned must be 0 in item charge assignment…

↑ 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 2009 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, change the code in Data Item Number 1 function in the Delete Invoiced Sales Orders report (299) as follows:
Existing code 1
...
         OnAfterGetRecord=VAR

                             ReserveSalesLine@1000 : Codeunit 99000832;

                           BEGIN

                             Window.UPDATE(1,"No.");
...
Replacement code 1
...
         OnAfterGetRecord=VAR

                             ReserveSalesLine@1000 : Codeunit 99000832;

// Add the following line.
                             ChargeItemLinesDeleted@1120000 : Boolean;
// End of the added line.

                           BEGIN

                             Window.UPDATE(1,"No.");
...
Existing code 2
...
                            Window.UPDATE(1,"No.");  

                             AllLinesDeleted := TRUE;

                             DocDim.RESET;

                             DocDim.SETRANGE("Document Type","Document Type");

                             DocDim.SETRANGE("Document No.","No.");
...
Replacement code 2
...
                           Window.UPDATE(1,"No.");  

                             AllLinesDeleted := TRUE;

// Add the following line.
                             ChargeItemLinesDeleted := TRUE;
// End of the added line.

                             DocDim.RESET;

                             DocDim.SETRANGE("Document Type","Document Type");

                             DocDim.SETRANGE("Document No.","No.");
...
Existing code 3
...
                                  IF NOT SalesOrderLine.FIND('-') THEN BEGIN

                                   SalesOrderLine.SETRANGE("Qty. Shipped Not Invoiced");

                                   DocDim.SETRANGE("Table ID",DATABASE::"Sales Line");

                                   IF SalesOrderLine.FIND('-') THEN

                                     REPEAT
...
Replacement code 3
...
                                 IF NOT SalesOrderLine.FIND('-') THEN BEGIN

                                   SalesOrderLine.SETRANGE("Qty. Shipped Not Invoiced");

                                   DocDim.SETRANGE("Table ID",DATABASE::"Sales Line");

// Add the following lines.
                                   SalesOrderLine.SETRANGE(Type,SalesOrderLine.Type::"Charge (Item)");

                                   IF SalesOrderLine.FINDSET THEN

                                     REPEAT

                                       SalesOrderLine.CALCFIELDS("Qty. Assigned");

                                       IF (SalesOrderLine."Qty. Assigned" = SalesOrderLine."Quantity Invoiced") THEN BEGIN

                                         DocDim.SETRANGE("Line No.",SalesOrderLine."Line No.");

                                         DocDim.DELETEALL;

                                         IF SalesOrderLine.HASLINKS THEN

                                           SalesOrderLine.DELETELINKS;

                                         SalesOrderLine.SuspendStatusCheck(TRUE);

                                         SalesOrderLine.DELETE(TRUE);

                                       END ELSE

                                         ChargeItemLinesDeleted := FALSE;

                                     UNTIL SalesOrderLine.NEXT = 0;

                                   SalesOrderLine.SETRANGE(Type);
// End of the added lines.

                                   IF SalesOrderLine.FIND('-') THEN

                                     REPEAT
...
Existing code 4
...
                                       IF (SalesOrderLine."Qty. Assigned" = SalesOrderLine."Quantity Invoiced") OR

                                          (SalesOrderLine.Type <> SalesOrderLine.Type::"Charge (Item)")

                                       THEN BEGIN

                                         DocDim.SETRANGE("Line No.",SalesOrderLine."Line No.");

                                         DocDim.DELETEALL;

// Delete the following lines.
                                         IF SalesOrderLine.Type = SalesOrderLine.Type::"Charge (Item)" THEN BEGIN

                                           ItemChargeAssgntSales.SETRANGE("Document Line No.",SalesOrderLine."Line No.");

                                           ItemChargeAssgntSales.DELETEALL;

                                         END;
// End of the deleted lines.

                                         IF SalesOrderLine.HASLINKS THEN

                                           SalesOrderLine.DELETELINKS;
...
Replacement code 4
...
                                        IF (SalesOrderLine."Qty. Assigned" = SalesOrderLine."Quantity Invoiced") OR

                                          (SalesOrderLine.Type  <> SalesOrderLine.Type::"Charge (Item)")

                                       THEN BEGIN

                                         DocDim.SETRANGE("Line No.",SalesOrderLine."Line No.");

                                         DocDim.DELETEALL;

                                         IF SalesOrderLine.HASLINKS THEN

                                           SalesOrderLine.DELETELINKS;
...
Existing code 5
...
                                      UNTIL SalesOrderLine.NEXT = 0;  

// Delete the following line.
                                     IF AllLinesDeleted THEN BEGIN
// End of the deleted line.

                                       SalesPost.DeleteHeader(

                                         "Sales Header",SalesShptHeader,SalesInvHeader,SalesCrMemoHeader,ReturnRcptHeader,

                                         PrepmtSalesInvHeader,PrepmtSalesCrMemoHeader);
...
Replacement code 5
...
                                    UNTIL SalesOrderLine.NEXT = 0;  

// Add the following line.
                                     IF AllLinesDeleted AND ChargeItemLinesDeleted THEN BEGIN
// End of the added line.

                                       SalesPost.DeleteHeader(

                                         "Sales Header",SalesShptHeader,SalesInvHeader,SalesCrMemoHeader,ReturnRcptHeader,

                                         PrepmtSalesInvHeader,PrepmtSalesCrMemoHeader);
...

Prerequisites

You must have the French version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1) 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

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

↑ Back to the top

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