|
How do we go about killing a batch or several batches of labor tickets from member WORK? The problem is that a user has some kind of mishap & the work station does not get reset via SYS993 so that the batch can be posted. Then several months later, some user at same work station thinks they creating a batch of labor, but in reality they are adding to pre-existing batch. We have people who do not look at SFC610 until after SFC620 has run ... this step that step ... they check the tickets they know they entered, they don't check the tickets they do not know are there. So SFC620 bombs this time because the original tickets are for long gone factory work orders. We now have a query/400 listing the contents of WORK member in FLT file sequenced by WS & date to identify data in there that needs to be got rid of. WRKDTAARA JT* lists all work stations with JT6* batches for SYS993 inspection. I used WRKCFGSTS to change my work station to that of an old work station address & tried to access the labor tickets found to be in WORK/FLT & found that I did not know enough JIT6 to do so. My end users even less. Thus, I need to learn how to identify hung batches & know how to kill them when they contain tickets too late to post, without neccessarily clearing the whole member of good stuff. I need to learn how an end user can tell that their batch has debris that they can kill ... I tried entering the labor ticket # for purpose of deleting individually & it told me no such ticket, but I could see plain as day on my query/400 list that it existed. Al Macintyre ©¿© MIS Manager Green Screen Programmer & Computer Janitor of BPCS 405 CD Rel-02 running on AS/400 V4R3 http://www.cen-elec.com Central Industries of Indiana--->Quality manufacturer of wire harnesses and electrical sub-assemblies +--- | 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.