× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Finding out ... if you have source code of programs which do stuff with FSO
file, such as shop order purge, labor update, then you can see what the
program does differently with that field.

This is version sensitive, where new versions get more stuff added.

A currently open shop order in 405 CD has status codes in FSO FOD FMA files.
There's relevant status info (not codes) in CEM CIC ELA IIM ITH LWK &
possible modifications, referenced in addition to the status codes.

The overall shop order has a status.
E = shop order has been entered.
Y = shop order is ready to be purged, but won't be if the inventory history
is not complete, relative to quantity needed to make order quantities (if
order quantities are maintenance lowered, then zero labor entered, that can
fix order we want to purge with all correct cost updates)
Z = someone force closed this shop order, to hell with correct costing
ID of shop order changes from SO (active) to SZ (purge this sucker)

FMA id changes from MA (active) to MZ (go away in next purge)
ELA order type "S" Shop Order, "C" Customer Order

FOD has a status code which comes from FRT nature of routing data ... is it
reportable? Also OD (reportable) RD (not) gets into FOD.OID changing to OZ
or RZ if candidate for purging. If labor operation is reported complete,
that goes to FOD.PCMPL

Vanilla Dispatch Report has a status code
Running = done some work, but not finished yet.
Waiting = prior operation completed, but nothing reported on this one yet.
Arriving = prior operation had some work, not yet completed, this operation
could get started.
We have modified dispatch report, have added status codes which did not come
out of the BPCS Box.
Cancel = MRP says this shop order is no longer desired.
Past Due = Due Date on this shop order is historical.
Current = Due date is good, not past due, on track or future.

MRP also has status codes.

-
Al Mac

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bailey, Dick
Sent: Wednesday, July 20, 2011 9:31 AM
To: BPCS ERP System
Subject: [BPCS-L] FSO Field named SSTAT

The field SSTAT field in FSO has a number of codes in it - E,X,Y,4,5,6.

Can somebody tell me what they mean? Or tell me how to find out?

Dick


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.