We have lots other things that can go wrong with processing labor tickets,
which may have nothing to do with your scenario, or could be unique to BPCS
version or where we have done modifications.

Eg. During the posting of a batch via JIT620, the job can hang, if the data
it got to is tied up thanks to some other user dedicated access to some
record. No one reads the error messages, they almost always take the
default option, which is not always best for a given scenario. So we get a
batch cancelled 1/2 way thru the process. Then, without consulting with IT,
they try to process the batch again.

There's a bug in BPCS to complicate the mess. As the tickets in a batch get
posted, there's a flag saying "Yes, this labor got posted" so that input
does not get duplicated, but there is no such flag for the inventory, so in
this scenario, we can have inventory double posted.

Al Mac

-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of
Larenzo Alexander
Sent: Monday, August 09, 2010 7:29 AM
To: BPCS Forum Post
Subject: [BPCS-L] Unprocessed Labor Tickets

I have a situation with Labor Tickets in BPCS that aren't getting
processed  and
I was wondering if any of you can point me into the right direction of what
check. And if I understand correctly if the labor tickets dont get fully
then that means some of the mateiral dont get backflush correct?  I created
report that runs at the end of the day that list all the labor tickets with
status code of '1S'. I believe that code represents Locked and waiting to be

processed?  The finished material has beed issued so those records should
have a
P=Posted on them. And when I check the Shop Order on some of them the
remainging is zero but some of the Labor tickets dont have a P=Posted beside

Any idea what could be causing those Labor Tickets not to get posted and I'm

assuming I would  have to go manually posted those tickets to flush the
out the system but I would like to determine the cause of the problem.

Thanks in advance,

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.