Aaron,
Thanks for the feedback. Certainly do notify me if you get a BAM to
work. In the mean time I am going to implement scripts to shutdown the
DC workstations periodically. Probably every weekend and again at month
end.
Thanks to all who replied.
Todd
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Aaron Hoyt
Sent: Tuesday, August 15, 2006 9:30 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Material Issue...Issue - V6.1.535
Todd,
I am working on a BAM to be triggered from Data Collection that will
kill
the session and automatically restart it if the transaction is
backdated. I
have not worked out the details yet, but that is the goal. This has been
a
frustration for us for a long time.
A little history on the problem. Epicor calls it working as designed.
They
set it so from a full license you can enter transactions for yesterday
without having to reenter the date each time. If you restart the calling
window (Inventory Issue/Returns) in a full license, the date will be
reset
to today, but it will remain the same as long as the calling window is
open.
The problem created is that in Data Collection the widow that calls the
issue material screen is the Data Collection screen itself. Therefore
you
have to restart Data Collection to get the date updated.
Strange that to accommodate those who don't want real time data, the
system
was intentionally made to make the collection of real time data
problematic.
I addressed the concern with Epicor nearly 2 years ago, but they refused
to
make a change because this was a change made to fix the "bug" that it
WOULD
refresh the date every time the issue screen came up.
Wow!
Anyway, when I get my BAM worked out for this, I will be sure to let the
group know.
Aaron Hoyt
Vantage Plastics
-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ]On
Behalf Of
Todd Hofert
Sent: Monday, August 14, 2006 8:49 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Material Issue...Issue - V6.1.535
Anyone???
Todd
________________________________
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Todd Hofert
Sent: Friday, August 11, 2006 9:39 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Material Issue...Issue - V6.1.535
We recently discovered a data collection issue and I am wondering how
others might suggest dealing with it. At July month end our accounting
department noticed some bizzarre back dated transactions that in some
instances caused negative values in our inventory. I finally tracked the
problem to the shop floor. It seems that several workstations open the
material issue screen and leave it open...forever. As a result, all of
the transactions get dated with the date the material issue program was
started (unless user over rides the date which they do not do) as
opposed to the current date.
Accounting has asked if I can 'kick everyone out' at 12:01 on the first
day of every month. I suppose I could schedule a task to stop and start
the admin service at that time but am not crazy about doing that. I
could impliment a procedure that requires users to exit that screen at
the end of their shift, but you know how that goes. It might be nice if
the OK button of that application closed the window? Any other ideas?
Pros and cons to stopping/starting the service on a schedule etc.?
Thanks
Todd Hofert
Spartan Graphics, Inc.
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]
Thanks for the feedback. Certainly do notify me if you get a BAM to
work. In the mean time I am going to implement scripts to shutdown the
DC workstations periodically. Probably every weekend and again at month
end.
Thanks to all who replied.
Todd
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Aaron Hoyt
Sent: Tuesday, August 15, 2006 9:30 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Material Issue...Issue - V6.1.535
Todd,
I am working on a BAM to be triggered from Data Collection that will
kill
the session and automatically restart it if the transaction is
backdated. I
have not worked out the details yet, but that is the goal. This has been
a
frustration for us for a long time.
A little history on the problem. Epicor calls it working as designed.
They
set it so from a full license you can enter transactions for yesterday
without having to reenter the date each time. If you restart the calling
window (Inventory Issue/Returns) in a full license, the date will be
reset
to today, but it will remain the same as long as the calling window is
open.
The problem created is that in Data Collection the widow that calls the
issue material screen is the Data Collection screen itself. Therefore
you
have to restart Data Collection to get the date updated.
Strange that to accommodate those who don't want real time data, the
system
was intentionally made to make the collection of real time data
problematic.
I addressed the concern with Epicor nearly 2 years ago, but they refused
to
make a change because this was a change made to fix the "bug" that it
WOULD
refresh the date every time the issue screen came up.
Wow!
Anyway, when I get my BAM worked out for this, I will be sure to let the
group know.
Aaron Hoyt
Vantage Plastics
-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ]On
Behalf Of
Todd Hofert
Sent: Monday, August 14, 2006 8:49 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Material Issue...Issue - V6.1.535
Anyone???
Todd
________________________________
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of Todd Hofert
Sent: Friday, August 11, 2006 9:39 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Material Issue...Issue - V6.1.535
We recently discovered a data collection issue and I am wondering how
others might suggest dealing with it. At July month end our accounting
department noticed some bizzarre back dated transactions that in some
instances caused negative values in our inventory. I finally tracked the
problem to the shop floor. It seems that several workstations open the
material issue screen and leave it open...forever. As a result, all of
the transactions get dated with the date the material issue program was
started (unless user over rides the date which they do not do) as
opposed to the current date.
Accounting has asked if I can 'kick everyone out' at 12:01 on the first
day of every month. I suppose I could schedule a task to stop and start
the admin service at that time but am not crazy about doing that. I
could impliment a procedure that requires users to exit that screen at
the end of their shift, but you know how that goes. It might be nice if
the OK button of that application closed the window? Any other ideas?
Pros and cons to stopping/starting the service on a schedule etc.?
Thanks
Todd Hofert
Spartan Graphics, Inc.
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.
[Non-text portions of this message have been removed]