It sounds like that is what we're going to need to do although I think we'll put it on the order entry side. Do you happen to have any example code you might want to share? We have a new IT person who is still learning Epicor. I'm trying to help with my limited knowledge during the evenings and weekends.
Emily
Emily
--- In vantage@yahoogroups.com, "Kevin Simon" <ksimon@...> wrote:
>
> Emily,
>
>
>
> One of the ways we handled this was by adding a "HOLD" UD checkbox to the
> Job, then had a BPM that kicked off on Start Activity, and cancelled the
> activity if the job was on HOLD.
>
>
>
> Sounds like this may be a quick fix for you.
>
>
>
> Kevin Simon
>
> SimsTrak Consulting
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Emily
> Sent: Thursday, April 07, 2011 7:15 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Job hold/order hold
>
>
>
>
>
> The majority of our jobs are make to order and we're fast about getting an
> order in to a job within a few hours of receipt of the customer's PO. I
> don't think we're the only company that has customers call a few days after
> sending in their PO and ask us to put it on hold. How do you handle these
> situations in your company to keep from having more work done on the job? Is
> there already a built in process that puts holds on jobs or orders and then
> the jobs (if it is a make to order job) that I'm missing? I've done some
> bpms that I can imagine could throw up a warning message but we're also
> using MES. Can I write a bpm for MES too? Has anyone already written a bpm
> or something else to keep from more work happening to a job that is on hold
> or flagged in some way. I appreciate the ideas. We're in 9.05.
>
> Emily
>
>
>
>
>
> [Non-text portions of this message have been removed]
>