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 related posted document is not deleted from the Posted Document Signature table (12421) as expected when you delete a posted document in the Russian version of Microsoft Dynamics NAV 5.0 SP1

The related posted document is not deleted from the Posted Document Signature table (12421) as expected when you delete a posted document in the Russian version of Microsoft Dynamics NAV 5.0 SP1

This article applies to Microsoft Dynamics NAV 5.0 for the Russian (ru) region.

↑ Back to the top

Symptoms

In the Russian version of Microsoft Dynamics NAV 5.0 Service Pack 1, you delete a posted document such as a posted purchase invoice in the "Posted Document Signatures" form in Employee Signatures. However, the related posted document is not deleted from the Posted Document Signature table (12421) as expected.

↑ 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 5.0 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, follow these steps:
  1. Add the DeletePostedDocSign function in the Doc. Signature Management, codeunit (12420)

    ...

    PROCEDURE DeletePostedDocSign@1210001(TableID@1210000 : Integer;DocNo@1210001 : Code[20]);

    VAR

    PostedDocSign@1210002 : Record 12421;

    BEGIN

    PostedDocSign.RESET;

    PostedDocSign.SETRANGE("Table ID",TableID);

    PostedDocSign.SETRANGE("Document No.",DocNo);

    PostedDocSign.DELETEALL;

    END;
    ...
  2. Add the following global variable in the Sales Shipment Header table (110):
    DocSignMgt@1210000 : Codeunit 12420;
  3. Change the code in the Sales Shipment Header table (110) as follows:

    Existing code

    ...
         SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Shipment Header","No.",0);

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Shipment Header","No.");

    END;
    ...

    Replacement code

    ...
      SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Shipment Header","No.",0);

    // Add the following line.
    DocSignMgt.DeletePostedDocSign(DATABASE::"Sales Shipment Header","No.");
    // End of the added line.

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Shipment Header","No.");

    END;    
    ...
  4. Add the following global variable in the Sales Invoice Header table(112):
    DocSignMgt@1210001 : Codeunit 12420;
  5. Change the code in the Sales Invoice Header table(112) as follows:

    Existing code

    ...
     SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Invoice Header","No.",0);

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Invoice Header","No.");

    END;
    ...

    Replacement code

    ...
     SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Invoice Header","No.",0);

    // Add the following line.
    DocSignMgt.DeletePostedDocSign(DATABASE::"Sales Invoice Header","No.");
    // End of the added line.

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Invoice Header","No.");

    END;
    ...
  6. Add the following global variable in the Sales Cr.Memo Header table (114):
    DocSignMgt@1210000 : Codeunit 12420;
  7. Change the code in the Sales Cr.Memo Header table (114) as follows:

    Existing code

    ...
     SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Cr.Memo Header","No.",0);

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Cr.Memo Header","No.");

    END;
    ...

    Replacement code

    ...
     SalesCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Sales Cr.Memo Header","No.",0);

    // Add the following line.
    DocSignMgt.DeletePostedDocSign(DATABASE::"Sales Cr.Memo Header","No.");
    // End of the added line.

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Sales Cr.Memo Header","No.");

    END;
    ...
  8. Add the following global variable in the Purch. Inv. Header table (122):
    DocSignMgt@1210002 : Codeunit 12420;

  9. Change the code in the Purch. Inv. Header table (122) as follows:

    Existing code

    ...
    PurchCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Purch. Inv. Header","No.",0);

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Purch. Inv. Header","No.");

    END;
    ...

    Replacement code

    ...
    PurchCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Purch. Inv. Header","No.",0);

    // Add the following line.
    DocSignMgt.DeletePostedDocSign(DATABASE::"Purch. Inv. Header","No.");
    // End of the added line.

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Purch. Inv. Header","No.");

    END;
    ...
  10. Add the following global variable in the purch. Cr. Memo Hdr. table (124):
    DocSignMgt@1210005 : Codeunit 12420;

  11. Change the code in the purch. Cr. Memo Hdr. table (124) as follows:

    Existing code

    ...
    PurchCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Purch. Cr. Memo Hdr.","No.",0);

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Purch. Cr. Memo Hdr.","No.");

    END;
    ...

    Replacement code

    ...
    PurchCommentLine.DELETEALL;

    DimMgt.DeletePostedDocDim(DATABASE::"Purch. Cr. Memo Hdr.","No.",0);

    // Add the following line.
    DocSignMgt.DeletePostedDocSign(DATABASE::"Purch. Cr. Memo Hdr.","No.");
    // End of the added line.

    ApprovalsMgt.DeletePostedApprovalEntry(DATABASE::"Purch. Cr. Memo Hdr.","No.");

    END;
    ...
  12. Change the code in the Purch.-Post, codeunit (90):

    Existing code

    ...
    DimMgt.MoveOneDocDimToPostedDocDim(

    TempDocDim,DATABASE::"Purchase Header","Document Type","No.",0,

    DATABASE::"Purch. Cr. Memo Hdr.",PurchCrMemoHeader."No.");

    ApprovalMgt.MoveApprvalEntryToPosted(TempApprovalEntry,DATABASE::"Purch. Cr. Memo Hdr.",PurchCrMemoHeader."No.");

    IF PurchSetup."Copy Cmts Ret.Ord. to Cr. Memo" THEN BEGIN
    ...

    Replacement code

    ...
    DimMgt.MoveOneDocDimToPostedDocDim(

    TempDocDim,DATABASE::"Purchase Header","Document Type","No.",0,

    DATABASE::"Purch. Cr. Memo Hdr.",PurchCrMemoHeader."No.");

    // Add the following lines.
    DocSignMgt.MoveDocSignToPostedDocSign(

    DocSign,DATABASE::"Purchase Header",

    "Document Type","No.",

    DATABASE::"Purch. Cr. Memo Hdr.",PurchCrMemoHeader."No.");
    // End of the added lines.

    ApprovalMgt.MoveApprvalEntryToPosted(TempApprovalEntry,DATABASE::"Purch. Cr. Memo Hdr.",PurchCrMemoHeader."No.");

    IF PurchSetup."Copy Cmts Ret.Ord. to Cr. Memo" THEN BEGIN      
    ...

Prerequisites

You must have the Russian version of Microsoft Dynamics NAV 5.0 Service Pack 1installed 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: kbmbscodefix, kbsurveynew, kbmbspartner, kbmbsmigrate, kbnoloc, kbnotautohotfix, kb, kbfix, kbqfe, kbmbsquickpub

↑ Back to the top

Article Info
Article ID : 2028928
Revision : 1
Created on : 1/7/2017
Published on : 8/4/2011
Exists online : False
Views : 112