Probably not :( We can live with using the system generated numbers.
We already have a spot on the Sales Order for them to enter their 'Fake
Job Number' into, so they will probably have to be happy with that at
this point. If it wasn't for users,our jobs would be easy as pie. :)
Thanks for the heads up, it tended to confirm what I felt in my gut.
Paul Millsaps
Time Manufacturing
254.399.2170
paulm@... <mailto:paulm@...>
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Thursday, July 24, 2008 2:43 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Firming up an unfirm job
When we were piloting (and I still get the occasional echo of a 'whine'
:) even now that we are Live) - our planners had a strong desire for
just what you are referring.
Most of that piloting was on 305 and, at that time, it appeared the
Firming process (and resulting Firmed job number re-assignment) was a
blackbox process a little too deep within the business object for us to
feel we could alter the behavior safely.
I doubt that has changed since 305.
That said, you could probably trap the Firming process (before it
executes) and write either app based VB code (or a BPM if all the
various apps that do Firming use a common BO - which I don't beleive
they do) - to mimic the Firming process at the data level (essentially
writing new JobNumber key values to multiple tables - and doing so in a
way that doesn't trash the DB).
Probably a safer way would be to remove the native Firminhg action
controls from all apps, replace them with your own equivalent look/feel
controls, and then have them fire off a safer 'firming' process that, in
reality, creates a new Firmed Job (based on your job number 'rules'),
copying everything prossible from the Unfirmed job - and then deleting
the Unfirmed job (to make it appear to the user as if they had simply
firmed it).
Is that really worth it?
Rob Brown
--- On Thu, 7/24/08, Paul E. Millsaps <paulm@...
<mailto:paulm%40timemfg.com> > wrote:
From: Paul E. Millsaps <paulm@... <mailto:paulm%40timemfg.com> >
Subject: [Vantage] Firming up an unfirm job
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Date: Thursday, July 24, 2008, 1:18 PM
When firming UNFIRM jobs, we would like to be able to assign a specific
Job Number based on the Character02 field from the Sales Order. Has
anyone done anything similar with the Job Firming process ? Can this
even be done, or is it pretty much hard-coded into the system?
Paul Millsaps
Time Manufacturing
254.399.2170
paulm@timemfg. com
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
We already have a spot on the Sales Order for them to enter their 'Fake
Job Number' into, so they will probably have to be happy with that at
this point. If it wasn't for users,our jobs would be easy as pie. :)
Thanks for the heads up, it tended to confirm what I felt in my gut.
Paul Millsaps
Time Manufacturing
254.399.2170
paulm@... <mailto:paulm@...>
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Thursday, July 24, 2008 2:43 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Firming up an unfirm job
When we were piloting (and I still get the occasional echo of a 'whine'
:) even now that we are Live) - our planners had a strong desire for
just what you are referring.
Most of that piloting was on 305 and, at that time, it appeared the
Firming process (and resulting Firmed job number re-assignment) was a
blackbox process a little too deep within the business object for us to
feel we could alter the behavior safely.
I doubt that has changed since 305.
That said, you could probably trap the Firming process (before it
executes) and write either app based VB code (or a BPM if all the
various apps that do Firming use a common BO - which I don't beleive
they do) - to mimic the Firming process at the data level (essentially
writing new JobNumber key values to multiple tables - and doing so in a
way that doesn't trash the DB).
Probably a safer way would be to remove the native Firminhg action
controls from all apps, replace them with your own equivalent look/feel
controls, and then have them fire off a safer 'firming' process that, in
reality, creates a new Firmed Job (based on your job number 'rules'),
copying everything prossible from the Unfirmed job - and then deleting
the Unfirmed job (to make it appear to the user as if they had simply
firmed it).
Is that really worth it?
Rob Brown
--- On Thu, 7/24/08, Paul E. Millsaps <paulm@...
<mailto:paulm%40timemfg.com> > wrote:
From: Paul E. Millsaps <paulm@... <mailto:paulm%40timemfg.com> >
Subject: [Vantage] Firming up an unfirm job
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Date: Thursday, July 24, 2008, 1:18 PM
When firming UNFIRM jobs, we would like to be able to assign a specific
Job Number based on the Character02 field from the Sales Order. Has
anyone done anything similar with the Job Firming process ? Can this
even be done, or is it pretty much hard-coded into the system?
Paul Millsaps
Time Manufacturing
254.399.2170
paulm@timemfg. com
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]