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.

"You must specify Bin Code in Job Journal Line Journal Template" error message when you invoice (or receive and then invoice) a purchase order for an item that is assigned to a job and is in a Bin mandatory location in Microsoft Dynamics NAV


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for all regions.

↑ Back to the top


Symptoms

Assume that you have a purchase order for an item that is assigned to a job and you specify a Bin code for the item in Microsoft Dynamics NAV. Then, when you post (receive and invoice) the purchase order, you receive the following error message because a mismatch of data between item ledger entries and warehouse occurs:
You must specify Bin Code in Job Journal Line Journal Template…

Additionally, when you post undo receipt for the purchase order, the item ledger entries are updated incorrectly. You expect the system to update the warehouse and item ledger entries equally.
This problem occurs after you apply the hotfix in KB 2159936.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2159936 You can unexpectedly post a purchase order as Receive for a Bin mandatory location with a job in Microsoft Dynamics NAV 2009 Service Pack 1

This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009 R2

↑ 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, follow these steps:
  1. Change the code in the FromPurchaseLineToJnlLine function in the codeunit (1004) as follows:

    Existing code
    ...
    JobJnlLine."Line Discount Amount" :=
    ROUND("Job Line Discount Amount" * Factor,Currency."Amount Rounding Precision");
    END;

    JobJnlLine."Location Code" := "Location Code";
    JobJnlLine."Line Type" := "Job Line Type";
    ...
    Replacement code
    ...
    JobJnlLine."Line Discount Amount" :=
    ROUND("Job Line Discount Amount" * Factor,Currency."Amount Rounding Precision");
    END;

    JobJnlLine."Location Code" := "Location Code";

    // Add the following line.
    JobJnlLine."Bin Code" := "Bin Code";
    // End of the added line.

    JobJnlLine."Line Type" := "Job Line Type";
    ...
  2. Change the code in the OnRun trigger in the Purch.-Post codeunit (90) as follows:

    Note The code to remove was added with KB 2159936, so it may or may not be necessary to change the following code.

    Existing code
    ...
    IF PurchLine.Type = PurchLine.Type::"Charge (Item)" THEN BEGIN
    PurchLine.TESTFIELD(Amount);
    PurchLine.TESTFIELD("Job No.",'');
    END;

    // Delete the following lines.
    IF (PurchLine."Job No." <> '') AND (PurchLine.Type = PurchLine.Type::Item) THEN
    PurchLine.TESTFIELD("Bin Code",'');
    // End of the deleted lines.
    ...
    Replacement code
    ...
    IF PurchLine.Type = PurchLine.Type::"Charge (Item)" THEN BEGIN
    PurchLine.TESTFIELD(Amount);
    PurchLine.TESTFIELD("Job No.",'');
    END;
    ...
  3. Change the code in the PostItemJnlLine function in the Purch.-Post codeunit (90) as follows:

    Existing code
    ...
    IF PostWhseJnlLine THEN BEGIN
    ItemTrackingMgt.SplitWhseJnlLine(TempWhseJnlLine,TempWhseJnlLine2,TempWhseTrackingSpecification,FALSE);
    IF TempWhseJnlLine2.FIND('-') THEN
    REPEAT
    WhseJnlPostLine.RUN(TempWhseJnlLine2);
    UNTIL TempWhseJnlLine2.NEXT = 0;
    ...
    Replacement code
    ...
    IF PostWhseJnlLine THEN BEGIN
    ItemTrackingMgt.SplitWhseJnlLine(TempWhseJnlLine,TempWhseJnlLine2,TempWhseTrackingSpecification,FALSE);
    IF TempWhseJnlLine2.FIND('-') THEN
    REPEAT
    WhseJnlPostLine.RUN(TempWhseJnlLine2);
    // Add the following lines.
    IF RevertWarehouseEntry(TempWhseJnlLine2,"Job No.",PostJobConsumptionBeforePurch) THEN
    WhseJnlPostLine.RUN(TempWhseJnlLine2);
    // End of the added lines.

    UNTIL TempWhseJnlLine2.NEXT = 0;
    ...
  4. Add the following local function: RevertWarehouseEntry@92(VAR TempWhseJnlLine@1000 : TEMPORARY Record 7311;JobNo@1001 : Code[20];PostJobConsumptionBeforePurch@1002 : Boolean). Then, add the following code for the function:
    IF PostJobConsumptionBeforePurch OR (JobNo = '') THEN
    EXIT(FALSE);
    WITH TempWhseJnlLine DO BEGIN
    "Entry Type" := "Entry Type"::"Negative Adjmt.";
    Quantity := -Quantity;
    "Qty. (Base)" := -"Qty. (Base)";
    "From Bin Code" := "To Bin Code";
    "To Bin Code" := '';
    END;
    EXIT(TRUE);

Prerequisites

You must have the one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009 R2


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


References

VSTF DynamicsNAV SE: 244430

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

↑ Back to the top

Article Info
Article ID : 2578695
Revision : 4
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 257