We are running on 407a sql and I do see a certain amount of 0 on hand
quantities for bins. Fortunately our crack inventory team seldom
notices this.
Rob Bucek
Manufacturing Engineer
PH: 715-284-5376 ext 311
FAX: 715-284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site)
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Friday, June 05, 2009 4:23 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: Partbin with 0 quantity
Tony,
Maybe it's a quirk with your version when run on SQLServer as Adam is
right - at least on Progress, there will never be a zero qty o/h PartBin
record. (PartBinInfo is another story entirely.)
We've had to run 6430 occasionally (at least I think that is the one) to
clean up messed up allocations on 405a progress (the wide open GUI
interface - and probably some misguided initial customizations on our
part that I hope we completely found and cleaned up! - allows users to
accidentally find 'creative' ways to modify the qty of requirements -
say from a job - and NOT have the allocations properly adjusted to suit)
- but I've never seen a problem with the PartBin records.
Just curious... Are you configured to disallow negative O/H's?
I ask as I'm wondering if NOT allowing negatives somehow blows up the BO
methods involved if a backflush (or perhaps even manual) PartTran hits a
PartBin record in a way that WOULD result in a negative (if executed
fully) but might trip up the PartTran record deletion for o/h = 0
PartBins...
Very curious.
If you figure it out (more than just running 6430), I'd love to hear
what it was.
Rob Brown
________________________________
From: Tony Hughes <thughes281@... <mailto:thughes281%40yahoo.com>
Sent: Thursday, June 4, 2009 2:07:42 PM
Subject: Re: [Vantage] Re: Partbin with 0 quantity
Yes, I agree they shouldn't be there, but they are.
I've called support more than once, and they just point me to "6430 -
Recalculate On Hand/Allocation Summaries", which I guess among other
things, deletes them.
The problem comes up because the users create their own BAQs, and they
do not remember to set the onhandqty <> 0.
And if you are thinkign users making BAQs is not advisable, I
semi-agree, but we use a heavily modified cycle count system, and it's
just easier if they do all of this themselves. There is no way to
automate it, or create an interface, that does all they want to do and
in the way they want to do
Just hoping this was something simpler than it seems to be.
Thank you for all replies!
____________ _________ _________ __
From: adam.whipp <adam.whipp@national tubeform. com>
To: vantage@yahoogroups .com
Sent: Thursday, June 4, 2009 12:34:55 PM
Subject: [Vantage] Re: Partbin with 0 quantity
Straight from the data dictionaryfor PartBin -- "When the OnHand
quantity becomes zero the PartBin record is deleted. There should never
be any records that exist with a zero quantity onhand."
I checked our database, and we have no 0 qty PartBin records, and I
don't recall a time when there ever were any in it here. I wonder if you
might have some other issue going on if they aren't deleting
automatically. ...
Adam Whipp
quantities for bins. Fortunately our crack inventory team seldom
notices this.
Rob Bucek
Manufacturing Engineer
PH: 715-284-5376 ext 311
FAX: 715-284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site)
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Friday, June 05, 2009 4:23 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: Partbin with 0 quantity
Tony,
Maybe it's a quirk with your version when run on SQLServer as Adam is
right - at least on Progress, there will never be a zero qty o/h PartBin
record. (PartBinInfo is another story entirely.)
We've had to run 6430 occasionally (at least I think that is the one) to
clean up messed up allocations on 405a progress (the wide open GUI
interface - and probably some misguided initial customizations on our
part that I hope we completely found and cleaned up! - allows users to
accidentally find 'creative' ways to modify the qty of requirements -
say from a job - and NOT have the allocations properly adjusted to suit)
- but I've never seen a problem with the PartBin records.
Just curious... Are you configured to disallow negative O/H's?
I ask as I'm wondering if NOT allowing negatives somehow blows up the BO
methods involved if a backflush (or perhaps even manual) PartTran hits a
PartBin record in a way that WOULD result in a negative (if executed
fully) but might trip up the PartTran record deletion for o/h = 0
PartBins...
Very curious.
If you figure it out (more than just running 6430), I'd love to hear
what it was.
Rob Brown
________________________________
From: Tony Hughes <thughes281@... <mailto:thughes281%40yahoo.com>
>To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thursday, June 4, 2009 2:07:42 PM
Subject: Re: [Vantage] Re: Partbin with 0 quantity
Yes, I agree they shouldn't be there, but they are.
I've called support more than once, and they just point me to "6430 -
Recalculate On Hand/Allocation Summaries", which I guess among other
things, deletes them.
The problem comes up because the users create their own BAQs, and they
do not remember to set the onhandqty <> 0.
And if you are thinkign users making BAQs is not advisable, I
semi-agree, but we use a heavily modified cycle count system, and it's
just easier if they do all of this themselves. There is no way to
automate it, or create an interface, that does all they want to do and
in the way they want to do
Just hoping this was something simpler than it seems to be.
Thank you for all replies!
____________ _________ _________ __
From: adam.whipp <adam.whipp@national tubeform. com>
To: vantage@yahoogroups .com
Sent: Thursday, June 4, 2009 12:34:55 PM
Subject: [Vantage] Re: Partbin with 0 quantity
Straight from the data dictionaryfor PartBin -- "When the OnHand
quantity becomes zero the PartBin record is deleted. There should never
be any records that exist with a zero quantity onhand."
I checked our database, and we have no 0 qty PartBin records, and I
don't recall a time when there ever were any in it here. I wonder if you
might have some other issue going on if they aren't deleting
automatically. ...
Adam Whipp
--- In vantage@yahoogroups .com, Tony Hughes <thughes281@ ...> wrote:
>
>
> Is it safe to just delete any partbin entries that show onhandqty = 0?
> These come up once in a while, and for inventory people it just throws
their little world upside down and they call us 75 times to make sure we
know. Some quote Nostradamus, others throw Bible verses at us.
> Rather than resort to medication for them, or drinking for me, I was
thinking I'd just delete the records on a scheduled, regular basis. (we
have SQL Server backend)
>
> I assume it is safe to delete partbin records with zero onhandqty?
> I know there is a progress procedure, but it requires me to remote in
to the server, log in to that progress thingy, click a button, find the
procedure, run it, wait an extraordinarily long amount of time, then
close all this out.
> when all I really need to do is type "delete from partbin where
onhandqty = 0" and hit F5.
>
>
>
> Thanks!
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]