Limiting a Part Search to Certain Customers

Yahoo Archive
1
All our part numbers can only be purchased by specific customers as each customer group owns their own tooling. And although our Part Search Words show our customer group, we raise Sales Orders using the 'Customer Part' and not our Part Number - you will have to set them up for each customer / part number though.

Just another option to give you only the customer parts you want available.




--- In vantage@yahoogroups.com, "Kevin Simon" <simstrak@...> wrote:
>
> First, you could always create a BAQ search. However, what I don't like
> about BAQ searches is that you lose some of the standard search
> functionality (example: ability to specify purchased or manufactured parts).
> You can always customize most of those features in.
>
>
>
> Another option, and something I've done for clients with other searches, is
> to set the call context BPM data in the main calling programs to the value
> you want to search for (in this case, the CustID). Then, you can have a
> post processing BPM on the returned data (it's probably on the Part.GetRows
> method, but a trace would verify it), and that post-processing BPM triggers
> when the call context field is not empty, and eliminates (deletes) returned
> rows that don't match it. It's a little hokey, but it works.
>
>
>
> One other note: I'd HIGHLY recommend that you store the CustNum on your
> Part table, not CustID. CustID's are designed to change, whereas CustNums
> will never change.
>
>
>
> Kevin Simon
>
> SimsTrak Consulting, LLC
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> madgett1
> Sent: Thursday, May 31, 2012 4:14 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Limiting a Part Search to Certain Customers
>
>
>
>
>
> We have parts that can only be ordered by certain customers so we've linked
> parts to customers through placing the CustID in ShortChar02.
>
> Obviously not all parts are linked to customers, it's really only "sales
> parts", that are.
>
> The upshot is that when searching for parts on a Sales Order Line we want to
> limit the search by the customer entered on the Summary screen.
>
> I thought this might be achieved by pre-loading a quick search screen with
> the customer, but to no avail.
>
> Anybody any suggestions how I might achieve this?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
We have parts that can only be ordered by certain customers so we've linked parts to customers through placing the CustID in ShortChar02.

Obviously not all parts are linked to customers, it's really only "sales parts", that are.

The upshot is that when searching for parts on a Sales Order Line we want to limit the search by the customer entered on the Summary screen.

I thought this might be achieved by pre-loading a quick search screen with the customer, but to no avail.

Anybody any suggestions how I might achieve this?
3
We put the Customer ID in the Search Word on the Part Table then use the Sort By option on the standard search.

--- In vantage@yahoogroups.com, "madgett1" <simon@...> wrote:
>
> We have parts that can only be ordered by certain customers so we've linked parts to customers through placing the CustID in ShortChar02.
>
> Obviously not all parts are linked to customers, it's really only "sales parts", that are.
>
> The upshot is that when searching for parts on a Sales Order Line we want to limit the search by the customer entered on the Summary screen.
>
> I thought this might be achieved by pre-loading a quick search screen with the customer, but to no avail.
>
> Anybody any suggestions how I might achieve this?
>
4
First, you could always create a BAQ search. However, what I don't like
about BAQ searches is that you lose some of the standard search
functionality (example: ability to specify purchased or manufactured parts).
You can always customize most of those features in.



Another option, and something I've done for clients with other searches, is
to set the call context BPM data in the main calling programs to the value
you want to search for (in this case, the CustID). Then, you can have a
post processing BPM on the returned data (it's probably on the Part.GetRows
method, but a trace would verify it), and that post-processing BPM triggers
when the call context field is not empty, and eliminates (deletes) returned
rows that don't match it. It's a little hokey, but it works.



One other note: I'd HIGHLY recommend that you store the CustNum on your
Part table, not CustID. CustID's are designed to change, whereas CustNums
will never change.



Kevin Simon

SimsTrak Consulting, LLC



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
madgett1
Sent: Thursday, May 31, 2012 4:14 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Limiting a Part Search to Certain Customers





We have parts that can only be ordered by certain customers so we've linked
parts to customers through placing the CustID in ShortChar02.

Obviously not all parts are linked to customers, it's really only "sales
parts", that are.

The upshot is that when searching for parts on a Sales Order Line we want to
limit the search by the customer entered on the Summary screen.

I thought this might be achieved by pre-loading a quick search screen with
the customer, but to no avail.

Anybody any suggestions how I might achieve this?





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