Error: “The Reservation Entry does not exist. Identification fields and values: Entry No.= ‘1234567’, Positive=’Yes’”
Does this error message in Microsoft Dynamics 365 Business Central look familiar to you? If so, then this blog has just the fix you need.
When a Sales Order line is created for an item, the next time MRP is generated by utilizing the Planning Worksheet’s (or Requisition Worksheet’s) Calculate Regenerative Plan, Business Central will create Reservation Entries in the Reservation Entry Table (Table = 337).
Below is an example of the Reservation Entries created after regenerating the Business Central’s replenishment function:
After using the Planning Worksheet’s “Carry Out Action Message” function to create a supply side document (Purchase Order in this example), the Reservation Entries in Table 337 are updated to reflect the connection between the Sales Order line’s demand and the Purchase Order that will suffice the demand.
Below is an example of what the Reservation Entries look like that tie the Sales Order line’s demand to the Purchase Order line’s supply. Notice that for every Entry No. that has a “Reservation Status” = “Tracking,” Business Central creates a negative quantity to track the demand and a positive corresponding quantity that represents the supply side transaction. Business Central utilizes the exact same “Entry No.” to track both negative and positive quantities.
If you have encountered the error shown below, the underlying issue that is causing the error is an “orphaned” reservation entry. The definition of an “orphaned” reservation entry is a Reservation Entry with a Reservation Status = “Tracking,” but where there is only one “Entry No.” that tracks either a negative or positive quantity. In other words, the second corresponding entry is missing.
Business Central performs extremely well to maintain and track BOTH the positive and negative quantities associated with the same “Entry No.” However, there are times when a customization conflicts with the Reservation Entry table and either the positive or negative quantity is deleted from Table 337. If you experience the above error, we recommend that you reach out to your partner for further analysis to identify the root cause related to why an orphaned reservation exists. Your partner should be able to track and identify what custom objects are creating the orphaned reservation entry. If your partner is not able to identify the root cause, contact Boyer and we can help you.
The ‘Reservation entry does not exist’ error in Business Central will keep you from performing common functions (e.g., run MRP, Post a Warehouse Receipt or Warehouse Shipment). However, there is a little trick that you can perform to delete the orphaned Reservation, which will then allow you to transact normally in Business Central. Here are those steps:
- Open the Item Card.
- Under the Planning Fasttab, change the Order Tracking Policy from “None” to “Tracking Only.”
- Change the Order Tracking Policy from “Tracking Only” back to “None.”
Changing the Order Tracking Policy’s setting as described above will delete the orphaned Reservation Entry and should allow you to proceed forward without any Reservation Entry errors. If you have any question, please don’t hesitate to reach out to Boyer for assistance.
