Thanks. Have it working now.
Miguel A. Santillan
Compass Manufacturing Systems
510-661-6666 Office
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Habib Smith
Sent: Wednesday, February 19, 2014 4:28 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] E9: BPM to prevent Job Deletion
looks like the firm status is stored on the jobfirm field. so, if you wanted to prevent firm jobs from being deleted by this one user the conditions could be:
the method is called by specified user (where specified user is the Epicor ID)
AND there is at least one deleted row in the ttjobhead table
AND the ttjobhead.jobfirm field of the deleted row is equal to the true expression
On Wed, Feb 19, 2014 at 5:52 PM, Miguel Santillan <msantillan@...> wrote:
Thanks for the idea…ow I just have to figure out how to let UNFIRM jobs to be deleted only
Miguel A. Santillan
Compass Manufacturing Systems
510-661-6666 Office
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Habib Smith
Sent: Wednesday, February 19, 2014 3:32 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] E9: BPM to prevent Job Deletion
Could create an in-transaction data directive Jobhead.
Condition:
the method is called by specified user (where specified user is the Epicor ID)
AND there is at least one deleted row in the ttjobhead table
Action:
Raise exception based on the designed template (where designed is the message that you want to display to your user that should have known better than to try to delete a job)
Method directive would likely offer better overall performance though or rather, not reduce performance in other areas like MRP
On Wed, Feb 19, 2014 at 3:39 PM, Miguel Santillan <msantillan@...> wrote:
Does anyone have a BPM to prevent the deletion other than a certain userid.
Miguel A. Santillan
ERP Analyst
Compass Manufacturing Systems
510-661-6666 Office
510-656-0603 Fax