web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

(0) ShareShare
ReportReport
Posted on by 323

I have negative inventory (-3) for the remaining quantity that I am attempting to adjust through the item journal entry. I received the error above.

When I look at the application worksheet I see the following. I need to adjust this negative quantity! What steps do I take to do so? The entry 11907 is not in the table and nothings is applied to this existing entry? 

Item No. Posting Date Entry Type Source No. Quantity Remaining Quantity Invoiced Quantity Reserved Quantity Shipped Qty. Not Returned Cost Amount (Actual) Open Positive Entry No.
2590 BLT 9/30/2016 Purchase 000000007326 12 0 12 0 0 61.25 No Yes 5596
2590 BLT 1/1/2017 Negative Adjmt. -12 0 -12 0 -12 -61.25 No No 10712
2590 BLT 1/25/2017 Sale 000000078675 -4 -3 -4 0 -4 -20.42 Yes No 11160

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    dkatson Profile Picture
    2,263 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    And suggestion once again - don't delete entries :) you will get errors somewhere in the system later

  • Verified answer
    addision1 Profile Picture
    323 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    Alright, I was finally able to get some assistance on this. What has happen is that some entries were deleted. In my particular instance our original vendor had initially allowed negative inventory and I was attempting to implement the next stage of our warehouse and begin using "Bins". For that conversion you cannot have negative inventory. So I found this problem when attempting to adjust to "0" inventory for the negative inventory items..  

    Regardless, my specific problems were corrected through object designer and a few steps on table 339 and checking some entries on the inbound and outbound entry columns. There are a few steps and each of my 4  item errors had a slightly different solution so that is why I can't post one specific solution here. But I can post to tell you that this problem can be resolved by someone who knows the table relationships and how NAV posts the entries. This was not a code  error. But running the debugger did help me to understand where the error was happening. Once the problem was recognized by my new tech support guy, it took about 3 minutes to fix each problem.

    You must have access to object designer and the SQL database with appropriate permissions.

  • addision1 Profile Picture
    323 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    Does anyone have any ideas where to look next?

  • addision1 Profile Picture
    323 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    Alright,   I was able to set the debugger on the post process. I get the error break in the GetValuationDate function @ OldValueEntry.SetRange("Entry Type") in code unit 22. It appears to recognize the error here first, then proceeds to code unit 5895> CalcInbndEntryAdjustedCost, Where it sends the error message box to the screen when it errors on line InbndItemLedgEntry.GET(InbndItemLedgEntryNo):

     

    It seems to be looking for the last entry number and using that as a comparison.

    Here is a copy of the code with the error lines highlighted:

     

    . Code Unit 22

    GetValuationDate(VAR ValueEntry : Record "Value Entry";OldItemLedgEntry : Record "Item Ledger Entry")

     WITH OldItemLedgEntry DO BEGIN

       OldValueEntry.SETCURRENTKEY("Item Ledger Entry No.","Entry Type");

       OldValueEntry.SETRANGE("Item Ledger Entry No.","Entry No.");

       OldValueEntry.SETRANGE("Entry Type",OldValueEntry."Entry Type"::Revaluation);

       IF NOT OldValueEntry.FINDLAST THEN BEGIN

         OldValueEntry.SETRANGE("Entry Type");

         OldValueEntry.FINDLAST;

       END;

       IF Positive THEN BEGIN

         IF (ValueEntry."Posting Date" < OldValueEntry."Valuation Date") OR

            (ItemJnlLine."Applies-to Entry" <> 0)

         THEN BEGIN

           ValueEntry."Valuation Date" := OldValueEntry."Valuation Date";

           SetValuationDateAllValueEntrie(

             ValueEntry."Item Ledger Entry No.",

             OldValueEntry."Valuation Date",

             ItemJnlLine."Applies-to Entry" <> 0)

         END ELSE BEGIN

           ValueEntry."Valuation Date" := ValueEntry."Posting Date";

           SetValuationDateAllValueEntrie(

             ValueEntry."Item Ledger Entry No.",

             ValueEntry."Posting Date",

             ItemJnlLine."Applies-to Entry" <> 0)

         END

       END ELSE

    .

    .Code Unit 5895

    CalcInbndEntryAdjustedCost(VAR AdjustedCostElementBuf : Record "Cost Element Buffer";ItemApplnEntry : Record "Item Application Entry";OutbndItemLedgEntryNo : Integer;InbndItemLedgEntryNo : Integer;ExactCostReversing : Boolean;Recursion : Boolean) : Boolean

      AdjustedCostElementBuf.DELETEALL;

      WITH InbndValueEntry DO BEGIN

        InbndItemLedgEntry.GET(InbndItemLedgEntryNo);

        SETCURRENTKEY("Item Ledger Entry No.");

        SETRANGE("Item Ledger Entry No.",InbndItemLedgEntryNo);

        QtyNotInvoiced := InbndItemLedgEntry.Quantity - InbndItemLedgEntry."Invoiced Quantity";

     

        FINDSET;

  • Suggested answer
    dkatson Profile Picture
    2,263 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    if it is sale entry, so may be try Sales credit memo on this sale

  • Suggested answer
    Maneesha Profile Picture
    5,891 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    addision1 ,

    hope you not delete any ledger entries ....

    on that scope.

    first open debugger and check

    then check this may be happen due to Item No. and Entry No. both filed has taken as primary key

    Make EntryNo. as primary key

  • addision1 Profile Picture
    323 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    I attempted this through the Phys. Inventory Journal and I receive the same error message.

  • ManishS Profile Picture
    86 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    @Maneesha,

    How to apply to that specific entry from Phys. Inventory Journal.

  • Suggested answer
    Maneesha Profile Picture
    5,891 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    addision1 ,

    use Phys. Inventory Journal (392)

  • addision1 Profile Picture
    323 on at
    RE: Item Ledger entry does not exist. Identification fields and values: Entry No. ='11907"

    I apologize for the formatting!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
Saurav.Dhyani Profile Picture

Saurav.Dhyani 2 Super User 2025 Season 2

#2
RK-25090803-0 Profile Picture

RK-25090803-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans