What is that error message about “Remaining quantity is too low” about?


When a user tries to change the application of item ledger entries, they can see the following error message: “Remaining Quantity is too low in Item Ledger Entry Entry No.=’341′.” In Dynamics NAV 2013 we made a much needed change to the inventory costing functionality, and the error message is the result of that: We wanted people to know that they cannot post the changes because they made the changes in a way that would result in incorrect quantities. This blog post explains the scenarios where users can see this error message, and suggests a better way to change application.

Scenario 1: Application Worksheet

  1. In the Item journal, create the following lines:
    1. Type Purchase; Posting Date: Jan 28, 2017; Item 80001; Quantity 10; Unit Amount 15;
    2. Type Purchase; Posting Date: Jan 29, 2017; Item 80001; Quantity 7; Unit Amount 10;
    3. Type Purchase; Posting Date: Jan 30, 2017; Item 80001; Quantity 3; Unit Amount 10;
    4. Type Sale; Posting Date: Jan 31, 2017; Item 80001; Quantity 10; Unit Amount 12;
  2. Run the Adjust Cost – Item Entries batch job.

You can now review the status of the generated item ledger entries.

navblog_QtyTooLow_1

The sale was applied to the first and oldest purchase in accordance to the items costing method FIFO. However, the sale was a special deal and the favourable price based upon the acquisition of a special consignment, purchase entry 340 and 341.
Currently the sale demonstrates a loss with a higher Cost Amount (Actual) than Sales Amount (Actual). So you try to make a re-application and apply the sale to the two purchases by using the application worksheet.

  1. Open the Application Worksheet and filter on item 80001.
  2. Remove the existing application.
  3. Choose the sales entry line.
  4. Choose Navigate, and then choose Applied Entries.
  5. The Applied Entries window appears and shows the applied purchase entry, 339.
  6. Choose Remove Application and then choose OK.
  7. Apply the sale to the two purchases from the special consignment – fixed application.
  8. Select the sales entry line.
  9. Choose Navigate, and then choose Unapplied Entries.
  10. The Unapplied Entries window appears and shows three purchase entries available for application.
  11. Select the purchase entries from the special consignment with Remaining Quantity = 7, entry 340 and entry 341 with Remaining Quantity = 3, and then click OK.

The error message appears:
“Remaining Quantity is too low in Item Ledger Entry Entry No.=’341′.”

The stated entry no. will depend on which entry is the active line when you click OK, because that is when the validation is made.

Scenario 2: Journal or Document Line

The same error message can be experienced when posting an item journal or document line, in the attempt of making a fixed application to several inbound item ledger entries.

Assume the same transactions has been created as in step 1a – 1c. This time for item 80002 in the demonstration database.

navblog_QtyTooLow_2

A sale of 10 units is to be recorded. To select supply from the special consignment, drill down in the Applies-to Entry field on the journal or document line to select the particular purchase item ledger entries, as below, and click OK.

navblog_QtyTooLow_3.png
navblog_QtyTooLow_4

Note, that only one entry number can be stored in the Applies-to Entry field. It will be entry no. of the active line in the item ledger entries window above.

When you post the line, the error message is generated:

“Remaining Quantity is too low in Item Ledger Entry Entry No.=’345′.”

Cause

In the event of creating fixed applications, the outbound entry can only be supplied by one inbound entry, covering the full quantity. The selection of several lines (entries) in the scenarios above to cover the outbound entry quantity is overruled, and only the active line is considered for fixed application, as there is only one cost source allowed.

One inbound entry, the cost source, can however supply several outbound entries in fixed applications.

For example, you have a Purchase item ledger entry with 10 units. In the Application Worksheet window, you choose the purchase entry as the active line and then, when you choose to navigate to Unapplied Entries, and you see there are several outbound entries shown, you can select several lines and then click OK. Back in the Application Worksheet page, you will see that all selected outbound entries respectively, state the entry no. of the purchase in the Applies-to Entry field.

How to: Change the Application of Item Ledger Entries

In the case where a sales event (or any outbound entry) requires fixed application and several inbound entries are required to fully supply the outbound entry, it can be represented in several lines in the document or journal. In the scenario above when entering a line in a journal or document, the sale of 10 units can be split into two lines with corresponding quantity to the supplying item ledger entries.

navblog_QtyTooLow_5
These lines are posted successfully.

After running Adjust Cost –Item Entries batch job, the sale entries are valued to the cost of the special consignment transactions and provide a profit, with the favourable sales price in mind. The first inbound entry, purchase entry 343 is still open.

In the first scenario where the sale is already posted, represented in one item ledger entry of quantity -10, the application worksheet is not providing any option to apply the sale to the two purchases.

Depending on the specific situation different work arounds can be considered. Below are suggestions, briefly described.

  1. Post negative adjustments of quantity 7 and 3 respectively and have them applied to respective purchase entry from the special consignment.
    Post a positive adjustment with quantity 10 at same cost as the special consignment.
    Apply the sale to this positive adjustment entry in the application worksheet.
  2. Reverse the Sale of 10 units in a Credit memo.
    Create a new Sales document with two lines with quantity 7 and 3 respectively and apply them to the existing purchase entries.

 

For more information, see Design Details: Item Application

 

Helene Holmin

Dynamics NAV Escalation Engineer

Comments (5)

  1. Astur says:

    “In the event of creating fixed applications, the outbound entry can only be supplied by one inbound entry, covering the full quantity”.
    Is there any reason based on Buiseness Rules that makes this sentence compulsory or is just a technical matter?
    It is hard to explain to standard users to do such operations and not giving a bussiness rule reason.
    In case there are only technical reasons for not supporting that multiselection-option, are you planning to develope a solution for the issue?
    Thank you very much

    1. Helene Holmin says:

      Hi Astur,
      It’s due to a technical limitation, only one entry number can be stored in the Applies-to Entry field.
      I don’t see any development plans in that direction to extend the functionality.

      Best Regards,
      Helene Holmin

  2. Henrik says:

    Great post, thank you!

  3. spidi says:

    This is a drawback from previous versions.
    For transfer entries is not working , now for this cases not working .An expected functionality that should be improved start to become useless in lot of cases.
    How to explain this to users ??? We have this functionality , but wait is not working ..Nav 2016 same situation…

  4. Algirdas says:

    Frankly, this is crap.

    NAV *does* allow outbound entry to have application to multiple inbound entries. Had the first purchase of 10 not existed, this would be exactly what happened. Application worksheet does not mention “fixed” application anywhere. It was provided as a means to change the application post-posting. The way it currently is, it does not. And this is absolutely misleading and annoying to users. Explanations as this do not help.

Skip to main content