Vendor Multiple Remit-To's OR Managing Duplicate Price Lists - E

We had looked there, but didn't carry it all the way through to the payment entry screen. I just did this testing and it appears this will work.

Unfortunately, bank payments are applied at the vendor level, not invoice level. This means we have to create separate groups for each remit-to. That being said, this is better than any other option on the table and we're going to continue to test and likely go down this path.

Thanks for the heads up,
Ken


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of leann_37@...
Sent: Thursday, July 22, 2010 2:20 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Vendor Multiple Remit-To's OR Managing Duplicate Price Lists - Email found in subject



On the supplier/bank tab, have you looked at alternate pay-to?
- l

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Ken Williams <kwilliams@...<mailto:kwilliams%40intermountainelectronics.com>>
Sender: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Date: Thu, 22 Jul 2010 13:59:27
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>>
Reply-To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Vendor Multiple Remit-To's OR Managing Duplicate Price Lists

Through testing, reading, question & answers here, etc....we've worked ourselves into a corner on how to manage a handful of vendors.

Some of our vendors, depending on which plant we buy from, require checks be cut to a different location. Vantage appears to have no support for this. My first question is, are we missing something, or does Vantage truly not support multiple remit-to's for this scenario?

On the assumption there is not support for multiple remit-to's, we've gone the route of creating separate vendorID's for each location. The issues this leads to include tougher vendor performance & historical analysis, which is manageable. Past this, Supplier Price Lists become a major issue. If we buy a part from VendorNewYork and update the price at the time of purchase in the price list - and later then try to buy from VendorCalifornia, the price list obviously isn't going to come into play.

I thought a BPM to automatically update VendorCA's price list when VendorNY's was updated would be the fix. This worked all the way up to me getting to the advanced code section when I realized I don't know how to call code to create a new record for VendorCA's price list.

Has anyone had success in using a BPM to create a new record somewhere else in the system they'd be willing to share?

Alternatively, any suggestions on how to manage this remit-to/multiple price list issue?

Thanks,
Ken


[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
Through testing, reading, question & answers here, etc....we've worked ourselves into a corner on how to manage a handful of vendors.

Some of our vendors, depending on which plant we buy from, require checks be cut to a different location. Vantage appears to have no support for this. My first question is, are we missing something, or does Vantage truly not support multiple remit-to's for this scenario?

On the assumption there is not support for multiple remit-to's, we've gone the route of creating separate vendorID's for each location. The issues this leads to include tougher vendor performance & historical analysis, which is manageable. Past this, Supplier Price Lists become a major issue. If we buy a part from VendorNewYork and update the price at the time of purchase in the price list - and later then try to buy from VendorCalifornia, the price list obviously isn't going to come into play.

I thought a BPM to automatically update VendorCA's price list when VendorNY's was updated would be the fix. This worked all the way up to me getting to the advanced code section when I realized I don't know how to call code to create a new record for VendorCA's price list.

Has anyone had success in using a BPM to create a new record somewhere else in the system they'd be willing to share?

Alternatively, any suggestions on how to manage this remit-to/multiple price list issue?

Thanks,
Ken


[Non-text portions of this message have been removed]
On the supplier/bank tab, have you looked at alternate pay-to?
- l

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Ken Williams <kwilliams@...>
Sender: vantage@yahoogroups.com
Date: Thu, 22 Jul 2010 13:59:27
To: vantage@yahoogroups.com<vantage@yahoogroups.com>
Reply-To: vantage@yahoogroups.com
Subject: [Vantage] Vendor Multiple Remit-To's OR Managing Duplicate Price Lists

Through testing, reading, question & answers here, etc....we've worked ourselves into a corner on how to manage a handful of vendors.

Some of our vendors, depending on which plant we buy from, require checks be cut to a different location. Vantage appears to have no support for this. My first question is, are we missing something, or does Vantage truly not support multiple remit-to's for this scenario?

On the assumption there is not support for multiple remit-to's, we've gone the route of creating separate vendorID's for each location. The issues this leads to include tougher vendor performance & historical analysis, which is manageable. Past this, Supplier Price Lists become a major issue. If we buy a part from VendorNewYork and update the price at the time of purchase in the price list - and later then try to buy from VendorCalifornia, the price list obviously isn't going to come into play.

I thought a BPM to automatically update VendorCA's price list when VendorNY's was updated would be the fix. This worked all the way up to me getting to the advanced code section when I realized I don't know how to call code to create a new record for VendorCA's price list.

Has anyone had success in using a BPM to create a new record somewhere else in the system they'd be willing to share?

Alternatively, any suggestions on how to manage this remit-to/multiple price list issue?

Thanks,
Ken


[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]