• Subject: Re: Finishing 405 CD Shop Orders
  • From: MacWheel99@xxxxxxx
  • Date: Sun, 15 Apr 2001 15:34:26 EDT

> after we run CST900. it purges orders but then there is always a complaint 
> that mfg can longer post transactions to the order after it has been purged.

There are several intertwined scenarios that people need to be aware of.
Here is one of them.  I talked about some others in my earlier posts.

We have had people who tried to reconcile total labor reporting for some 
location with total payroll hours, as a means of locating misreporting or 
mistranscriptions.  Even though the payroll has not been run yet for the 
week, our time card machines are connected to a computer network & people 
with the right authorization can find out how many hours worked by clock 
number for yesterday.  Or at least that is what they tell me - I could have 
misunderstood.

When clerical shift knocks off for the day, they might not have 100% labor 
tickets for everyone who was working up to factory shift knocked off for the 
day, so they can leave a labor ticket batch open in the evening & wrap up the 
labor tickets next morning for that day.

Unposted labor tickets are in FLT file WORK member with TFWSID identifying 
each batch.  A query can be run off this by clock # to get total hours 
reported through labor.  Teams can confuse this a bit.  So do the total 
reported hours by person seem to be within reason, or are there peaks & 
valleys, indicating labor tickets that need extra verification before final 
posting?

Suppose in the evening I run CST900, closing all shop orders that have had 
enough posted to them to purge, and suppose we had one of these JIT600 or 
SFC600 batches still open, and suppose some labor tickets in that batch got 
purged?

When the batch tries to close next day, it gets hung on the purged orders, 
resulting in a corrupted batch, with the gone shop order still in the WORK 
member.  If we do not clean that up properly, that is a time bomb waiting to 
crash the next labor ticket input batch that someone might do from the same 
work station.

Well we now avoid this risk with a query over FLT file WORK member by TFWSID 
TTDTE & other fields to check what batches are open overnight.  If I see 
this, I am NOT going to do a CST900 on a facility that has open labor ticket 
batches, and I also notify the user of the work station involved, to make 
absolute certain they are aware that a batch is still open.

This scenario may or may not be related to what you were asking about.  But I 
think other BPCS users might like to make a similar query for safety 
assurance.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| 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 thread ...


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

This mailing list archive is Copyright 1997-2022 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.