|
Hi Ho Otto. When a user chooses to close a shop order with a (21) in Version 6.X This is what happens 1. FSO Header a) SID field goes to 'SZ' from 'SO' b) SSTA field goes to 'X' from '5' c) SOSTS field goes to 'XX' from '05' 2. FOD Operation Detail a) ODID field goes to 'OZ' from 'OD' b) ODSTS field "REMAINS" set at '05' 3. FMA Material Detail a) MID field goes to 'MZ' from 'MA' b) MASTS field "REMAINS" set at '05' When using CST900 it does the same as closing a shop order manually and it also does the following, the ODSTS field from FOD and MASTS field from FMA are updated to 'XX'. Marc Lacelle Royal Canadian Mint Keep on BPCS'ing > ---------- > From: hason@pbsvb.cz[SMTP:hason@pbsvb.cz] on behalf of PBS Velka > Bites, a.s. - AIS[SMTP:hason@pbsvb.cz] > Reply To: BPCS-L@midrange.com > Sent: Friday, November 26, 1999 1:30 AM > To: 'BPCS-L@midrange.com' > Subject: Shop orders close conditions in v.6.0.04 > > AS400 v4r4 BPCS v 6.0.04, mixed mode > > Hi all, > could anyone explain me when a shop order is closed by CST900 ? > There are some S.O.s at the end of month we force not to close > (in sql we set sstat='5', sosts='05') - because all operation are not > finished > or there is not all required material in FMA. > > In v.5 was the condition for closing a S.O. > fso.sqreq = fso.sqfin & fso.sstat in ('X', 'Y') > > I'm not sure about v.6 condition; > and second question - is there a program in BPCS which checks all S.O.s > and resets status fields in FSO (to correct our SQL changes)? > > Thanks in advance > Otto > > > +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
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.