I'm having fun with the Ship To addresses in POA. I am entering orders for a single billing account with multiple ship to addresses. I am creating the PO by entering the O/N from OE and using all the items from the customer's order. No problem there. The program asks me if I want to use the "ship to" from the OE order, but it doesn't allow it to happen. I manually have to enter that particular "Ship to" for the order. You'd think that would be the end of it - but it's not. If you go back to edit an earlier order for some reason, the "ship to" that was originally assigned to that order is not retained for that PO. The "ship to" on that order that is being edited changes to whatever the most recent "Ship To" entered was on a later order. (Not sure if I've explained myself clearly.) Is there something I'm missing in the process or is it one of the "challenges" of the Purchase Orders program?

You need to use different codes for each address. PO only stores the code on the purchase order (unlike OrderEntry which stores a copy of the information with the order so that it can be modified without changing the basic information).

PO Ship to addresses can be created on the fly.

Thanks, Andrew. Will this change in future versions?

Why would the 'ship to' change if you go back and edit an earlier order that was already posted?

Because when you change the address, you are changing the address pointed to by the code in the older PO's. Only the code is stored. The address on the form is the address retrieved from the file as it currently exists, even for an old PO.

Just make up a new code for each address. There is no practical limit on the number of codes.

We are currently re-writing Purchase Orders for Adagio, but this is not one of the changes that will be in first version. we want both the old and new versions to run beside each other without converting the data, so that people can e confident that the new version is working well without disrupting their business.

Once we're confident that we're there, then we'll be happy to introduce other changes that would be useful to people.

This would make a good "Adagio Wish"!

OK - Thanks. I have a lengthy POA "Wish List". I'll add this one!

Hi Andrew

Although I am sure R&D is aware of this, a couple of my clients have been begging for this change for years. One in particular thinks this is the single worst feature in all of Adagio - they drop-ship to everyone and their PO ship-to list is totally unmanageable. It has caused them, a user with 14 Adagio modules (including 3rd party ones) on Upgrade Plans, to consider looking for another software package.

I understand your response but I wanted to chime in anyway.

Steve

Hi Steve,

Is the pain point dreaming up a new ship to code? Adding a ship to address block to the PO itself is a big structural change, and won't be happening for a while.

I understand it is a big structural change and it won't be happening for a while. But it would be well worth doing, in order to make Adagio PO a better functioning module.

The pain is not only dreaming up new ship-to codes, it's the fact that they are not associated with a vendor as they should be (as ship-tos in OE are associated with a customer), it's the fact that you can't view the address while in the PO itself, and it's the fact that nonintuitive results occur such as the one that affected Marion.

Steve