Reservation Entry-table-problems (4.00 SP1/SP2)

frede

We are having very big problems with the update of reservation entries (table 337).

Very often Navision creates postings with source type 83 (Item Journal Line) - even though they are posted - and don't exist anymore.

Then we cannot change status for production orders before we delete the reservation entries with source type 83.

But sometimes now we also have to delete the reservation entries for the specific production order (source type 5406 and 5407) or else we cannot post anything nor change status on the production order.

Also on sales orders we cannot post the order because Navision tells us the reservation is not in stock - but there is plenty of stock avaiable. Then we delete reservation entries for the sales order in question!

I know it is not a solution just to delete in the reservation entries - but does anyone know of any fixes or anything?

Or are we doing something wrong (besides deleting records in 337)?

Does the reservation entry-handling work better in 4.00 SP2? ](*,)

johnson_alonso

You must set reserve to be optional and order tracking set to be tracking only.
Do you use reserve field and order tracking ?
Oftentimes, if you post somethingfrom item journal but wrong to put location, it is also cause error in reservation.


Rgds,

ara3n

Are you using serialization? Which version are you working on currently? 3.7 and 3.6 did have bugs and would leave orphaned entries in that table.

frede

Thank You both,

we are not using serialization.

We have set Reserve=Optional on both Customer and Item - and Order Tracking we don't use at all (not licensed).

It is version 4.00 SP1 with all of the CU's from 4.00 SP2 concerning Reservations.

Scott_Frappier

Henrik:

Are you using the planning capabilities of Navision? Specifically, the requisistion worksheet or planning worksheet?

What type of entries are being created? Is it the type "tracking" or a different type?

4.0 SP1 had numerous issues with reservations, and 4.0 SP2 seems to be better...I need to know a little more before I can relate to your enviroment.

Let me know at your convenience.

Thanks!

frede

Yep!

We are using planning capabilities (99001017 - calculate plan)!

And at this time this report is creating more than 6.600 "orphans" in the reservation entry-table.

Maybe it is because I have only installed most of 4.00.SP2-CU's and no 4.00.SP2-tables?

Thanks for your questions/answers - it is greatly appreciated!

Scott_Frappier

Henrik:

Calculate Plan (report) calls Codeunit 5431 (Calc. Item Plan), which in turn calls the Inventory Profile Offsetting codeunit (99000854).

Codeunit 99000854 creates Tracking type entries when it is calculating a plan, and then commits the tracking at the end of the process (per item) with the CommitTracking() function.

If you are not using Tracking or Action Messages within your database, you may want to make it so that the following code exists on the CalculatePlanFromWorksheet() function:

CalculatePlanFromWorksheet()

InitVariables(InventoryProfile[1],ManufacturingSetup2,Item,TemplateName,WorksheetName,OrderDate,MPSPlanning);
DemandtoInvProfile(InventoryProfile[1],Item,OrderDate,ToDate);
ForecastConsumption(InventoryProfile[1],Item,OrderDate,ToDate);
BlanketOrderConsump(InventoryProfile[1],Item,ToDate);
SupplytoInvProfile(InventoryProfile[1],Item,ToDate);
UnfoldItemTracking(InventoryProfile[1],InventoryProfile[2]);
FindCombination(InventoryProfile[1],InventoryProfile[2],Item);
PlanItem(InventoryProfile[1],InventoryProfile[2],OrderDate,ToDate);
//>> SYM/SF
//CommitTracking;
IF ItemRequiresTracking THEN 
  CommitTracking;
//<< SYM/SF

ItemRequiresTracking() - (Item = Local Item Record)

IF Item.GET(TempSKU."Item No.") THEN
  EXIT(Item."Order Tracking Policy" > Item."Order Tracking Policy"::None)
ELSE
  EXIT(TRUE); // Leave standard functionality alone

The consequences of this change are the fact that the tracking system will not be updated when the planning functionality is run. This can be a good/bad thing...I still have not understood why Navision dumps tracking entries when planning if the item is not setup to do order tracking...it causes unwanted locks and data issues.

We have used the fix above for our customer sites, and it seems to work w/o problems. Your Mileage May Vary (YMMV), so please test the functionality thoroughly before introducing a change into your enviroment.

I believe this will resolve most of the data issues that you are having, if they are related to these entries that are being created.

Let me know if this helps or not!

ecclectic

i 'im using item tracking- lot no with order tracking policy =none. when i process a sales order, and then i use function reserve. its does update the reserved quantity field on sales order.

however when i go to line- item tracking lines- no lot no has been assigned.

i checked the reservation entry table and the entries have been created there.

any idea.