Unfortunately it's still without its drawbacks and own problems.
You'll need to make sure you don't have a salesperson set at the
customer level, otherwise it will always bring that person into the
quote and set them as the primary salesperson on the quote.
Secondly, if the sales person hits save on the quote BEFORE they set
the appropriate territory, it won't update the salepersons tab under
people with the right people. So - they must select the customer,
territory THEN they can hit save.
You're required at the company config to assign a default territory,
so we assigned a dummy entry that has a dummy salesperson. If
someone messes up and doesn't do the quote right, we'll suddenly see
the dummy user appearing on commission reports.
We're not really happy with the CRM module in many ways.
You'll need to make sure you don't have a salesperson set at the
customer level, otherwise it will always bring that person into the
quote and set them as the primary salesperson on the quote.
Secondly, if the sales person hits save on the quote BEFORE they set
the appropriate territory, it won't update the salepersons tab under
people with the right people. So - they must select the customer,
territory THEN they can hit save.
You're required at the company config to assign a default territory,
so we assigned a dummy entry that has a dummy salesperson. If
someone messes up and doesn't do the quote right, we'll suddenly see
the dummy user appearing on commission reports.
We're not really happy with the CRM module in many ways.
--- In vantage@yahoogroups.com, "Ken Williams" <ken@...> wrote:
>
> Actually, I think this will work very well. We're going to play
with
> this this afternoon and I believe this'll fix the last of the
problems
> I'm seeing.
>
> Thanks!
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Patrick Parker
> Sent: Friday, February 15, 2008 1:00 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: CRM Workforce/Salesperson
>
>
>
> I can't take credit for this, someone else suggested this idea on
> this list, but it works for us.
>
> If you don't really have territories in your business, you could
> create a territory that's the name of each sales person. Then for
> those territories, set the default sales person to the same name as
> the territory. That way they simply select the territory (which
> would be their name) and then the salesperson is automatically set
> based on that territory, since it's identical to the territory.
>
> Just an idea.
>
> --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> , "Ken
> Williams" <ken@> wrote:
> >
> > We're in the process of trying to implement the CRM Module. It
> sounds
> > like we do things differently then Epicor is expecting (and
probably
> > from what most companies do), but I hope we're not alone.
> >
> > From what I can see, CRM expects each territory &/or customer to
> have a
> > default salesperson. Any new opportunities/quotes goes to this
> > customer's default or their territory default salesperson. We
need
> it
> > to go to whoever is entering the opportunity/quote and have all
> tasks
> > default to that person, not the one assigned as default. We have
a
> ton
> > of overlap and we have no commissions.
> >
> > Anyone have experience getting the entry salesperson to be the
> default
> > instead of looking to the customer record? I spent some time
> looking at
> > BPM but I cannot see through trace logging when it sets the
default
> > Sales Rep.
> >
> > Thanks for any pointers,
> > Ken
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>