Location Dependent Replenishment

 8 Replies
 1 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
brupp
Veteran Member
Posts: 165
Veteran Member

    Hello - probably an easy question - Say you stock a box of gloves in your main perpetual inventory.  You want the OR's to replenish from inventory, but Ambulatory Clinics to replenish direct from vendor in LUM.  Is this all driven by IC12?  Today, Ambulatory replenishes from inventory, so that's the piece we want to change.  I assume this means all of those sites would require IC12.1 & IC12.2 screens?

    Secondly, if this is correct, what is best practice - create IC12 for ALL item master items or just the ones Ambulatory will use?

    Thanks.

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member

      I would likely do it from IC81 and create a nonstick par for Ambulatory to count and order from, but yes, IC12/12.2 would also do it.

      I would only add the items they have on the shelf. (Part of why I'd do it on IC81 is that I can make them responsible to maintain it.)

       

      Edit: IC330 for IC12 and IC331 for IC81 would need to be added to your steps for vendor switches and mergers.

      Michelle Wetzel
      Veteran Member
      Posts: 183
      Veteran Member
        We do this all the time using templates. You can set the from company and location from each line. If you make it be NOT from the inventory location, it will go to a PO as a nonstock.
        brupp
        Veteran Member
        Posts: 165
        Veteran Member

          I would definitely prefer IC81 vs IC12.  So for Seq & Shelf Location just 1,2,3, & so on?  Just use 1 for Par Level?  And GL Cat for account/sub account default?

          brupp
          Veteran Member
          Posts: 165
          Veteran Member
            @Michelle - Thanks for the advice. We are moving to GHX's requisitioning tool by year's end so I'm not sure if templates would be an option. I'll have to ask the GHX team on that.
            Kat V
            Veteran Member
            Posts: 1020
            Veteran Member
              We put the Pars at 2 so it will always keep 1 on the shelf - when it lets it go to 0 the users assume it's not working. The ORs had shelf locations - they are useful for the Optime pick tickets so we copied those and then yes, seq was just in 10s so they could go in and reorder things fairly easily.
              Mike Bernhard
              Veteran Member
              Posts: 101
              Veteran Member

                This is actually not a super-easy question and often depends upon your existing setup.  That said, I would urge you to consider using PO25 to manage this as well, but it may not work for you (depends on how other things are setup.  Read on for more info

                 

                If you were implementing Lawson from the ground up, I would urge you to consider this data model.  Since you are already live, you can review this and then look at your own data to see if your data model aligns.

                1. Only setup true perpetually tracked items in IC12 (tracking flag will be set to YES for all IC12 items);  

                2. Only setup true par items in IC81.  Naturally, you would also need to setup the SOURCE for each item so Lawson knows whether these are storeroom items or purchased direct from the supplier

                3. Create and maintain PO25s for ALL ITEM MASTER items

                4. Setup each req loc with a FROM LOCATION = the local storeroom that services their facility (or if you do not have a storeroom at a given facility then you simply setup the FROM LOCATION = main dock (IC02).

                 

                With this data model in place, reqs placed at the main hospital will automatically be routed to the storeroom when the item is active in IC12 and will automatically be routed to the supplier when they are not active in IC12.

                 

                With this model, you can also support one-offs where different facilities and/or departments purchase the same supply from multiple suppliers.  For non-stock items, this is accomplished by setting up multiple PO25s and using the PARTICIPANTS screen to assign participants where necessary.  (You only need to setup participants for the PO25 that is used by a subset of the enterprise).  For par and perpetual items you can route items to any supplier you like using the ITEM SOURCE Tabs within IC12/IC81 (but you also need PO25s to ensure contract pricing defaults)

                In your example, you don't need two PO25s unless the ambulatory clinics order from a different supplier than the rest of the Enterprise.

                Hope this helps.

                 

                brupp
                Veteran Member
                Posts: 165
                Veteran Member
                  Thanks all for your responses. @Mike - We have non stocks in IC12, using the GL Category to drive the account & sub account on req & PO lines. I don't know the reason for this as I was not here during implementation. I would love to use IC11 instead. Any reason you know of that we could not do so? We just have one Item Group.
                  Kat V
                  Veteran Member
                  Posts: 1020
                  Veteran Member
                    Account did not appear on IC11 until v9. If you were like us and went live on an earlier version, your organization likely either missed it or just didn't feel the need to change.

                    We made the switch and it has absolutely made life easier and did not impact the RQC users for the non-stock. You would need to look at your vendor defaults and make it pull from the vendor agreement over the location. Depending on your PO25.6, you may need to worry about UOM on some items which IC12 makes easier. I don't have Contract Management, so I don't know how that would impact this. Once done, assuming the items have always been non-stock, IC12 will allow you to delete the records.