Hi Evan, should I be seeing this in the BETA as still showing as an issue?

The next trap for you will be where you enter manual ROP, then auto calculate. It will hold the manual level until this time expires then auto cuts in and sets to zero if insufficient sales. Pretty tricky stuff just to hold a min level, without guessing when to check the auto calculate option. The SSL is no help in reality…

It should be in beta. If you have safety stock level expressed in units, not days, and the item has no history, the reorder point should still be set to the safety stock level. Thanks, -e why would we want to still enter a qty into the reorder point? This is checked as zero qty and SSL should be observed regardless.

perhaps they can address the "SSL" (qty) at the same time :(

Mass update cannot update location-based reorder points, only when MLI is off. I don't quite understand the issue that remains. You are saying you don't want the calculation to happen on inactive locations? Defect 161788 - Advanced Inventory Management> Reorder Point calculates In-correctly and even to In-active Locations…

Evan, can I use the mass update to change the null values in the ROP to "0" by using the new formula fields? This will save me some time. In the help screen I get this far (which of course does nothing as I don't know what I am doing) NVL({reorderpoint},0). Any help appreciated.

thanks Evan, NS does not need to make any changes to min/max manual levels being set back to zero when "auto" boxes are checked. They currently show zero when checked and appear to revert ok back to the original manual settings when unchecked (not 100% sure on this as some anomolies). From reading the notes I think that is…

Case #722729 Update : (Self service) Defect 144772: (AU 9748) Reorder point calculation not working again. Our view is that the SSL when used as a "QTY" value should be active regardless of sales history.

Tom, try setting "0" in your ROP as "null" does not return a value, unless something has changed recently.

The task ran as I saw the numbers change on items with history available. Evan, I believe that I did not tick the auto reorder point box on the items I was monitoring. Now having the live account installed I have ticked the box and find the reoder point is reading the SSL qty. This makes sense in hindsight....haha, sorry…

Hi Evan, this still going ahead? :confused:

now Enhancement 144772, but the main issue with the SSL has been confused in the NS translation. The problem is that we believe the SSL expressed as a QTY should be the minimum level held despite any sales history. Otherwise we are constantly fiddling with manual min/max levels v. auto settings. In the initial fault we…

Hang on, a bit of a spin on this Evan, I understood it would be regardless of history that the SSL would be observed. Am I now being advised that if history exists and if there is insufficient sales to show a value =>1 then the result will be "0" rendering the SSL useless still? Otherwise, the SSL is not working as I have…

we were scared to use "ORDERS" as transactions to consider because we could not establish if it was calculating as well against "CLOSED" orders so decided on invoiced sales being the safer option. Our main drama is "SSL" not operating as we would have thought if using the qty option. If insufficient sales/history then does…

yes you may, but be aware of setting the "auto" as difficult to disengage in multi-locations. Keeps calculating regardless of status of location. This can be filtered on the reorder inventory level but pretty poxy really. Also do not rely on SSL for a min qty to be kept as this does not start calculating until you have a…

yes there is a PSL for eac, as well as a "Reorder Point" which we use as the "MIN". So you have say 5 as the trigger point, PSL = 10, reorder qty is a pack of 20....so then at 5 you would see an order for 1* pack of 20 pieces say. Can be varied by location. As mentioned before, stay away from the "SSL" (Safety Stock Level)…

I did not realise that we had an option for autocommit on assy item members? Is this when using work orders maybe? My battle is with assy items needing to be built versus purchasing prebuilt.

NO CHANCE.....you will need to go for a new assy item :)

we have no end of issues with this as when "auto inventory" is used it often picks up min/max levels by calculating aginst :inactive: locations. To correct this we find ourselves often having to reactivate these inactive locations, edit the auto settings for the relevant items & then deactivate the location again.

Hi Damon, not sure if this would work, but on the inventory tab on the right there is a field called safety stock level, you can enter a value and amount of days in there as well. SSL was reported as defective. Apparently an update is coming in new release. At present the entered value in units is not calculated as one…

sure thing, I would like to know how other users are juggling this (those with MLI active & no DLE). Evan, the question about the manual entry into PSL & then ticking the auto box? Does it observe this value only until sufficient sales history and then if insufficient sales sends the value to zero?

unsure if she would hire herself out....but....you could try an email to [EMAIL="emma@invertek.com.au"]emma@invertek.com.au[/EMAIL] as she has ours working to what I believe to be the best NS has to offer at present. Remember.....the sticky part is the inability to receive "multiple" item receipts to a single freight bill.

Evan, failed miserably I'm afraid with implementing PSL as the single column solution. [LIST=1] [*]The PSL does not get picked up on the reorder report so therefore nothing gets purchased...at all. [*]I seem to see the manual qty in mine sets back to "0" when updating after checking the auto box so therefore cannot be used…

so there is the same old issue.....I enter in say 1 piece of a new sales line, I always want 1 piece regardless....more if sales justify it. I enter this 1 piece into PSL (the only active column I am now using) then in 3 months say if this item still is slow moving/not moving at all, then NS drives the qty to "0". So…

Defect 161788 - Advanced Inventory Management> Reorder Point calculates In-correctly and even to In-active Locations SUMMARY: Reorder Point calculates In-correctly and even to In-active Locations WORKAROUND: None Identified yet

Also...watch out for this little gem.... You can now receive multiple PO's onto a single bill, thanks NS...but...the "Landed Cost" needs linking somehow to the single "Bill".....how do you expect anyone using this feature to sit all day plodding along splitting up the freight/duty invoices across multiple 'IR's"? A part…

so does NS suggest using the PSL with a manual setting of min required and set to auto? Or does NS drive the auto level automatically down to "0" value if insufficeient sales? Would I need to have null value in ROP and no auto ticked as well? Evan, we simply want 1 column to maintain and have it observe a minimum point and…

Hi Evan, I am sure that NS still believe it works as intended, just has no value in this form to us. The fact that you consider this SSL as a working qty now (value = x), which then adds over and above the automatic caluclated reorder qty (value = y), so then "x+y" is the total qty for order.....I just don't get it. Yes, I…

our account is fine, just tested and tracked ok. :)

Hi David, I would have to disagree with you on this. MLI stuffs the SSL & inventory management. (Refer below) Defect 161788 - Advanced Inventory Management> Reorder Point calculates In-correctly and even to In-active Locations SUMMARY: Reorder Point calculates In-correctly and even to In-active Locations WORKAROUND: None…