Options

Multiple Units of Measure in Bin Contents

DarkSideDarkSide Member Posts: 46
OK...my head hurts...

It appears (at least in NAV 5) that unless directed pick and put-away is used I cannot have multiple units of measure in the warehouse entry table...and thus bin contents? It kind of wrecks the idea of having multiple units of measure doesn't it?

Am I missing something or do I have to do a modification for this?

Thanks in advance.
My mommy says I'm special

Comments

  • Alex_ChowAlex_Chow Member Posts: 5,063
    Why can't you use multiple units of measure with bins without using directed pick and put-away? :-k
  • DarkSideDarkSide Member Posts: 46
    It appears I can take an order with multiple units, create a pick ticket with multiple units, but it won't let me have multiple UOM in bin contents. It changes everything to the base UOM. I've done this in unmodified Cronus...

    It's my first experience using multiple units of measure without directed pick/putway. I guess it seems to defy logic...what's the point of having multiple UOM if you can't track it that way in inventory???

    Has anyone done a mod to get around this? It seems like it a nice little surgical strike should fix it but I don't want to open pandora's box.
    My mommy says I'm special
  • DenSterDenSter Member Posts: 8,307
    Stock is kept in Base unit of measure.
  • ara3nara3n Member Posts: 9,258
    It is a simple mod. The code that creates the warehouse journal from item journal to post checks if it's directed pick and putaway and if it's not it it converts it to base. You can easily modify that to allow multiple unit of measure in warehouse.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • DarkSideDarkSide Member Posts: 46
    Thanks ara3n. I played with this for a while last night. You are correct about the test for directed pick and put-away. However, I found a whole lot of other issues in create pick, physical inventory, etc. I even found several places where the qty. per UOM is HARDCODED (my god what were they thinking??) to a quantity of 1 instead of referring the the quantity for the base UOM. To top it all off this company uses lot control and want to use FEFO for generating picks.

    In short, they're going to have to live with it or buy the WMS granule.

    Thanks.
    My mommy says I'm special
  • Alex_ChowAlex_Chow Member Posts: 5,063
    NAV has this for a reason, I wouldn't recommend modifying it.

    One of the reason is that there is no way to "break bulk" from case to eaches without creating inventory adjustments.
  • ara3nara3n Member Posts: 9,258
    Alex Chow wrote:
    NAV has this for a reason, I wouldn't recommend modifying it.

    One of the reason is that there is no way to "break bulk" from case to eaches without creating inventory adjustments.

    If you use reservation for lot tracked it will do the reverse "break bulk"
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Alex_ChowAlex_Chow Member Posts: 5,063
    I don't think the original poster has lot numbers implemented.

    Personally, I wouldn't touch this portion of WHM since it's possible serious damage can occur with quantity and costing. Check with the client to see if there are alternatives. Maybe you can create a new field to calculate case quantities on the Bin Content table.

    Or implement directed pick and put-away.
  • ara3nara3n Member Posts: 9,258
    Alex Chow wrote:
    I don't think the original poster has lot numbers implemented.

    Personally, I wouldn't touch this portion of WHM since it's possible serious damage can occur with quantity and costing. Check with the client to see if there are alternatives. Maybe you can create a new field to calculate case quantities on the Bin Content table.

    Or implement directed pick and put-away.

    Costing has nothing to do with WMS btw, but yes I do agree that WMS does certain warehouse setup in unexpected way. The code isn't pretty as well.
    Reservation/serial no./lot no has made it even more complicated.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Alex_ChowAlex_Chow Member Posts: 5,063
    ara3n wrote:
    Costing has nothing to do with WMS btw, but yes I do agree that WMS does certain warehouse setup in unexpected way. The code isn't pretty as well.
    Reservation/serial no./lot no has made it even more complicated.

    Modifying the unit conversion in WHM has indirect effect on costing. In another words, if you modify WHM to take cases, NAV may not recognize that it should be in cases and count it as eaches. So costing MAY (and probably will) be affect if not careful.
Sign In or Register to comment.