Re: AS/400 performance - lot tracking - closed period posting

> Subj:  Re: AS/400 performance - lot tracking - closed period posting
>  From:    wendy.decair@countryfresh.com (Wendy DeCair)
>  
>  AS/400 performance - lot tracking - closed period posting

>  > > Hi all-

>  > > Several issues have cropped up that I need some assistance on 
>  We are running V6.02 full client server - march  cum 98 - as400 / v4r3.

We are on 405 CD mixed mode as400 V4r3

>  3.  Has any one come up with a way to do a negative shop order?  

Yes - human error is always with us, so we ought to be able to fix just about 
anything.  Misreporting to Shop Orders is potentially astronomical for a 
number of reasons.  People, whose Efficiency is being tracked, and they know 
it, are tempted to "cook the reporting" to make their performance look good.  
I can cite other examples.

> User has entered an overage on shop order reporting.  
> Wants to correct it after posting without having to do INV500 adjustments
>  to all the component items.

>  > > This is a very big problem here.  Any ideas?

We use JIT600 to report inventory & labor at the same time so they stay in 
sync.
We use SFC600 to make labor corrections when we do not want them to affect 
inventory, where typically the problem is in the hours reported irrespective 
of quantities.

The screens for both are the same.  Check the DDS rules & the logic of the 
programs ... there are places in which negative input is perfectly 
acceptable, and places where you do not want it.

Once an operation is coded complete you are more limited in what you can key 
in, or ought to.

Our big problem is that we might have several shop orders open at the same 
time for the same item ... one is due last week, this week, next week, etc. 
...the production department prints off the paperwork & the latest printouts 
go on top of a pile with the first needs at the bottom of the pile & people 
take the latest printouts from the top of the pile & the labor gets reported 
to the wrong order.

So the system closes out the shop order that is not due yet & shows the one 
that was due last month as being past due.  The only way that can be 
permanently fixed is to change how the production department handles their 
paperwork.  But they don't recognize that ... instead, the ancient order is 
manually closed "we got this done eons ago, why isn't the system making it go 
away?"  There are some other complications of our own making.

Another thing we do is go into shop order maintenance and change the order 
quantity  before the total reported meets the thresh hold of an order 
finished, or vica versa.  My understanding is that it is the labor reporting 
that tells the FSO etc. that the shop order is ready to go bye bye, so I tell 
them that after downsizing a shop order quantity, to run through a zero labor 
transaction to refresh what operations it thinks are completed.

>  > > Wendy DeCair
>  > > Country Fresh Inc
>  > > wendy.decair@countryfresh.com

>  > > Either you are part of the problem or part of the solution!

I am part of both - you do not get to pick which part

Al Macintyre
+---
| 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
+---