Setting up a Ship To location?

What's happening in your testing scenarios? Is the new ship-to not showing on the POs? Or are deliveries for the surgery center still going to the main receiving dock regardless of having the new ship-to on the PO?

If deliveries are still going to receiving even though the PO has the surgery center address it may be that your vendors are only seeing the ship-to account for your main receiving location. Do you have ship-to accounts built in your AP10.1 or AP10.2 records? You might have to set up a new ship-to account number with your vendors so they know to ship to this new secondary location rather than the primary account they have set up in their system.

I can help you with this but I think a phone call would be best. Send me you phone number and a time to call. mbernhard@TridentEdge.com

One thing that is happening is that the orders are still combined with other depts. they are not creating their own PO.  Or it's the complete opposite, every dept. is creating their own PO, which we definitely don't want especially with our prime vendor, we like to combine all requisitions on one PO.

 

There are so many places that you can "play" with this.....RQ01, Single Document to a PO;  IC02, Single Document to a PO;  PO10.2, Single Document to a PO;, that I think they are working against each other in my testing.

How are your PO100 jobs set up? Do you separate them by ship-to location? Is this the first time you've had to build another ship-to location? We've always had multiple ship-to locations and used to have separate process levels for each one but a couple years ago AP/Accounting decided to go to one process level for all locations. I had to modify our PO100 jobs to run each location separately because otherwise they would all combine on the same PO. The separate process levels prevented that.

Also you might look at the "Single document to a PO" flag in IC02 and RQ04 records and make sure that's set how you want them.

Yes, this is our first ship to location I've had to do so I've not had to worry about separate PO100 jobs.  On the RQ01, PO10.2, IC02 in the "Single Doc to a PO" field, they are all blank (no default).

I feel like I'm trying to reinvent the wheel.  There's got to be other hospitals out there with multiple ship to locations.  How do you get it to work?  I feel that my problem is stemming from the fact that we don't have IC12 records built for non stock items and/or we use Purchase From locations on our PO25 Price Agreements and maybe we shouldn't have. 

I will say that we do add nonstock items to our IC12 and we don't use purchase from locations in PO25. But for you neither of those should matter for this issue. I still think your problem is with with PO100. If you're running PO100 without identifying the ship-to location and you're not using process levels, your lines will combine based on the vendor. If you set at least one job up for the SC and run that first, it will pull all the SC lines out of PO23 and leave the others for your main receiving location.

We do this, but we don't allow vendors to combine ANY requesting locations on a PO. So every department gets a separate PO - negating what you are seeing.

Have you looked at Attributes? I have one that is "BillOnlyLoc" - Y/N - then created a list - Y goes on a list called BILLONLYBATCH and the others go on a NORMALBATCH - this forces the PO100 to include or "skip" and might work for you.

We have a facility that has several ship to location that utilize Procurement Templates for ordering Non-Stock items. How do we create additional ship to location in Lawson utilizing Procurement Templates without referencing IC12-Item master.

If you leave the From Company and From Location blank on the PO15, RQC will treat the line the same way it would from Express Order.

Tavares,
Normally, I would absolutely defer to Kat but I am not sure that her answer addresses your question (she may have been responding to the thread above it).

Also, I am unclear on your question at the point that you reference the "IC12-Item master." The IC12 is the Item Location, the IC11 is the Item Master, the question changes significantly based on which table/screen you are actually referring to. That said, being unclear has never stopped me from offering advice.

You can reference a "service" item on a template, which need not be defined in the IC11. I am not sure that I see a lot of value in this, because if the item/service is going to be used often enough to be placed on a template, I would just assume to build the item out.

As to the IC12, for context, we are set up as Jon A described above in his last response. In our general scenario, the template line references an IC Location/Item Location combination (IC02 and IC12, respectively) where the Item Source (IC12.2) sets the Vendor and Purchase From. This assumes that the Vendor Agreement Reference (PO25) that gets selected has the same Vendor as the Item Source. In other words, because we leave the Purchase From at the Agreement blank, if the Vendor in the Item Source matches the Vendor on the Agreement, the Purchase From from the Item Source carries on to the Requisition or Purchase Order Line. If the two vendor values do not match, the Agreement values takes precedence over the Item Source value AND the Purchase From is left . (And, after three rewrites, that was as simple as I could make that.)

The way I see it, you can get around this in a few ways, but the most robust options are: 1) do not build out the Item Source record or 2) build the Agreement so that both the Vendor and Purchase From. And, as a by-the-way, there is a Unit of Measure component to this process which could also be used (which also requires a bit of configuration of the Agreement Header). As an example in this process, the "blank" Purchase From Agreement could have a carton of 10, the "populated" Purchase From Agreement could have a box of 10, at which point the UoM defined on the Template line would drive which agreement gets selected. A bit arcane, to be sure, but it does work.

Good luck,
Red

Red,
I'm sorry for mistaking the IC12-item master statement. What I was trying to ask is this, we have a facility that has several clinics that needs to have their own ship too locations. They currently place requisitions using Procurement Templates but often times need to have time sensitive items deliver directly to their location. How do we set these areas up without creating multiple IC12 - Item Location up for each Clinic?

Will Kat V answer be the way we need to more forward in this scenario? So far we understand the IC02 - Location Setup, RQ01-Setup, but is there anything else that need to be perform in order to set up these ship to? Let me know if something seems unclear.

Kat V,

 

Is this at the Header Level or Line Level.  I am assuming the Line correct.

How is the RQ01 setup for "we have a facility that has several clinics that needs to have their own ship too locations"

RQ01: CLINIC Company: From Location: FACILITY
OR
RQ01: CLINIC Company: From Location: CLINIC

In instances where: RQ01: CLINIC Company: From Location: CLINIC and no item built in IC12. On PO15 Header Company/From Location Blank. On PO15 Line anything with Company/From Location: FACILITY, these lines will pull from stock. Company/From Location: Blank on the line -- this will order from vendor based on your defaults in PO01.4

Tavares,
As I said, I never let clarity stand in the way of a vigorous response.

To answer your question, as I now understand it... Yes, you can set up a separate IC Location (IC02/From Location) specific to the Clinic or Clinics (which is what I think Kat is alluding to). If every order these clinics place is intended to be shipped directly to them, this is probably the cleanest alternative. If they are currently using a common Procurement Template (PO15), you may want to consider making copies based on the number of IC Locations you build out.

If this issue is specific to products, rather than all orders, you may want to consider building a Par Location (IC81). This process creates a connected pair of Locations (RQ and IC), so is not much different than the option above, except that instead of the Templates, you could use a handheld (if you have MSCM) or IC83 as a manual order process. The one advantage of the Par Location is that you can set a par to order Non-Stock (direct to a Vendor) even if the product is an I-Type at the From Location (you set this up in the [More] button on the line, by populating the Vendor/Purchase From). Additionally, I believe that this Non-Stock order utilizes the IC02 information of the Par Location, not the From Location (but I would like someone to corroborate that).

The last option, if these are sporadic orders that occur outside of the parameters described above, you can offer the Requester the ability to create Drop Ship orders. This can be done with all things as they are set up today--no new IC Location is needed (there is an option to use the RQ Location address in place of the IC location address). The downside is that a straight Drop Ship order does not require Receiving (PO30). Considering these are going "directly to the floor", that may not be all that big of a deal.

We use the above option for our Desktop Delivery locations with one slight alteration. For these locations, upon release of the Requisition, we use ProcesFlow/IPA to auto-magically set the Drop Ship flag to "Yes", which sets the delivery address to that of the RQ Location. Then we set the Drop Ship flag to "No". This retains the RQ Address but now re-establishes the Receiving requirement... (because Lawson?). We use this pretty extensively, so I know it functions. What I cannot say is if ProcessFlow/IPA is doing exactly what a human would do in this situation, or if there is something a bit more "black box" going on.

Anyway... more options to consider,
Red