I'm not sure that the E really means that nothing has been done. We have
14 SO's with the E and all but one show the finished qty equal to the qty
required. They are all still SO id. We are on 6.0.4. I had never even
noticed this status before this email. We typically do not see them so
I'm not sure what it means. Most of ours go directly into a 4.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Al" <macwheel99@xxxxxxxxxx>
Sent by: bpcs-l-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
05/10/2010 07:38 PM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
"'BPCS ERP System'" <bpcs-l@xxxxxxxxxxxx>
cc
Subject
Re: [BPCS-L] FSO Shop Order Status
This is version specific.
In 405 CD
E = Order that nothing has yet been done on,
Y = Order allegedly completed.
X = Order that someone has deleted.
4 & 5 not valid ... either a modification, or a different version
When shop order purge is run, orders coded "Y" are NOT purged if there's
missing postings. For example, to make the order we need to issue some
quantity of material. If less than that reported, then order not purged.
This topic confuses many of my people.
I tell them
(a) if you have an order that is partially completed, and you want to end
it, my advice is to change the order quantity to what we actually made,
then
run a ZERO quantity ZERO time labor ticket thru, because then BPCS will
revisit all operations and code them completed, and the order will go away
in next purge.
(b) if you force close the order, BPCS will NOT update itself with costs
and
statistics associated with any work that was done on the order.
-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of
Mark
Sabol
Sent: Monday, May 10, 2010 2:18 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] FSO Shop Order Status
Does anyone know what the meaning of the alpha status' are for SSTAT in
the
FSO
E
X
Y
4
5
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.