Customer ASSIGN conundrum

You could use the Alternate Bill to functionality of Vantage to set it
equal to the customer you want. Then use a BPM to update as needed.

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Wed, Oct 17, 2012 at 2:56 PM, chan213419 <chan213419@...> wrote:

> **
>
>
> Anyone?
>
> OK, here's the short-short version. The company has 2 kinds of Customers:
> Actual-Customers AND Supplier-Customers. Supplier-Customers 'cover' many
> Actual-Customers. The SoldTo is NEVER = Supplier-Customers. BUT the BillTo
> CAN = Supplier-Customers.
>
> User wants to be able to quickly update MULTIPLE Actual-customer's BillTo
> information, and have it equal 1 Supplier-Customer's BillTo information.
>
> What is the best way to do this?
>
> An updateable BAQ?
>
>
> --- In vantage@yahoogroups.com, "chan213419" <chan213419@...> wrote:
> >
> > I need help from you professionals out there. I need to know if you
> believe our solution to a client's problem sounds satisfactory to you, or
> if you have a better solution.
> >
> > Our client has 2 types of Customers that have been built in the Customer
> table. 1.) ACTUAL Customers (we'll call them ACs) 2.)International Rep
> Customers (lets call them IRCs).
> >
> > The IRCs cover geographical territories across the globe. The ACs are in
> these territories.
> >
> > The IRCs TYPICALLY go by Country to Country. BUT there are instances
> where there will be multiple IRCs for 1 Country (China for example).
> >
> > The ACs BillTo information is equal to the IRCs BillTo information (i.e.
> AC's BillTo = IRC's BillTo).
> >
> > When the IRCs BillTo information changes (say they move, or they cover
> more territory, lose territory etc) our client wants the AC's that are tied
> to this IRC to be updated.
> >
> > Our proposed solution:
> > Since the IRCs are setup in the Customer Maintenance application the
> actual information associated to the BillTo can be manipulated there,
> likewise the TerritoryID can be assigned in its'application. So I believe
> we are good on changing that information.
> >
> > The tricky part is getting that IRC information to update the AC's
> BillTo information. We proposed creating an Updateable BAQ. This BAQ would
> Query by TerritoryID then the user could check the ACs they wish to update.
> Once that is done we would have the Updateable BAQ ASSIGN IRC's BillTo =
> AC's BillTo.
> >
> > What do you think? I like it because it gives flexibility. Lets say an
> IRC covers all of Italy, but wants to cover another AC in Austria for
> whatever reason. The user could ASSIGN the IRC in the appropriate Italy
> Territory, but then look up Austria's territory and update the AC there too.
> >
>
>
>


[Non-text portions of this message have been removed]
I need help from you professionals out there. I need to know if you believe our solution to a client's problem sounds satisfactory to you, or if you have a better solution.

Our client has 2 types of Customers that have been built in the Customer table. 1.) ACTUAL Customers (we'll call them ACs) 2.)International Rep Customers (lets call them IRCs).

The IRCs cover geographical territories across the globe. The ACs are in these territories.

The IRCs TYPICALLY go by Country to Country. BUT there are instances where there will be multiple IRCs for 1 Country (China for example).

The ACs BillTo information is equal to the IRCs BillTo information (i.e. AC's BillTo = IRC's BillTo).

When the IRCs BillTo information changes (say they move, or they cover more territory, lose territory etc) our client wants the AC's that are tied to this IRC to be updated.

Our proposed solution:
Since the IRCs are setup in the Customer Maintenance application the actual information associated to the BillTo can be manipulated there, likewise the TerritoryID can be assigned in its'application. So I believe we are good on changing that information.

The tricky part is getting that IRC information to update the AC's BillTo information. We proposed creating an Updateable BAQ. This BAQ would Query by TerritoryID then the user could check the ACs they wish to update. Once that is done we would have the Updateable BAQ ASSIGN IRC's BillTo = AC's BillTo.

What do you think? I like it because it gives flexibility. Lets say an IRC covers all of Italy, but wants to cover another AC in Austria for whatever reason. The user could ASSIGN the IRC in the appropriate Italy Territory, but then look up Austria's territory and update the AC there too.
Anyone?

OK, here's the short-short version. The company has 2 kinds of Customers: Actual-Customers AND Supplier-Customers. Supplier-Customers 'cover' many Actual-Customers. The SoldTo is NEVER = Supplier-Customers. BUT the BillTo CAN = Supplier-Customers.

User wants to be able to quickly update MULTIPLE Actual-customer's BillTo information, and have it equal 1 Supplier-Customer's BillTo information.

What is the best way to do this?

An updateable BAQ?

--- In vantage@yahoogroups.com, "chan213419" <chan213419@...> wrote:
>
> I need help from you professionals out there. I need to know if you believe our solution to a client's problem sounds satisfactory to you, or if you have a better solution.
>
> Our client has 2 types of Customers that have been built in the Customer table. 1.) ACTUAL Customers (we'll call them ACs) 2.)International Rep Customers (lets call them IRCs).
>
> The IRCs cover geographical territories across the globe. The ACs are in these territories.
>
> The IRCs TYPICALLY go by Country to Country. BUT there are instances where there will be multiple IRCs for 1 Country (China for example).
>
> The ACs BillTo information is equal to the IRCs BillTo information (i.e. AC's BillTo = IRC's BillTo).
>
> When the IRCs BillTo information changes (say they move, or they cover more territory, lose territory etc) our client wants the AC's that are tied to this IRC to be updated.
>
> Our proposed solution:
> Since the IRCs are setup in the Customer Maintenance application the actual information associated to the BillTo can be manipulated there, likewise the TerritoryID can be assigned in its'application. So I believe we are good on changing that information.
>
> The tricky part is getting that IRC information to update the AC's BillTo information. We proposed creating an Updateable BAQ. This BAQ would Query by TerritoryID then the user could check the ACs they wish to update. Once that is done we would have the Updateable BAQ ASSIGN IRC's BillTo = AC's BillTo.
>
> What do you think? I like it because it gives flexibility. Lets say an IRC covers all of Italy, but wants to cover another AC in Austria for whatever reason. The user could ASSIGN the IRC in the appropriate Italy Territory, but then look up Austria's territory and update the AC there too.
>