Read my other response first. It is a simpler scenario to check out.

A second problem could be related to how your routings and BOM are coded.
We use bubble # in BOM of the reporting routing step to designate where the
raw material is consumed.

Typically our reporting steps are numbered 50 100 150 200 250 etc. where
most of the consumed inventory is at early steps. If labor reports making
step 100, and BOM for the components is at step 100, then inventory is
consumed that must have been needed to do that.

If some component is needed, where the engineer neglected to specify the
operation, then no backflushing until get to final production receipt for
the whole thing. If error in engineering, where the consumption operation
is a non-reporting operation, then the component inventory will NEVER get
backflushed.

In this scenario, the labor reporting clerical operation was done precisely
correctly. The problem is in the engineering for the parts.

There is a way to code the item, to second guess mis-reporting (which we
don't use because it does not work well). Suppose a shop order says we made
500 at step 50, 425 at step 100, 500 at step 150, it would seem reasonable
that we really made 75 more at step 100 and failed to report it, so with the
assumption system turned on in BPCS, we can get that extra 75 automatically
posted. The problem is that if the missing 75 shows up in a later posted
ticket, the assumption is not reversed, and we have duplicated inventory
transactions.

Scrap also factors into this. The way we handle scrap is counter-intuitive
to how BPCS functions. Let's suppose at step 100, we had 75 rejected by
inspection. There is an immediate effort to see if it can be repaired. If
not, an additional 75 is made right away to be replenished. If it can be
repaired, then there may be additional inventory adjustments needed, but the
end result is that there are legitimate reasons why some labor transactions
do not get posted in sequence.

-
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
to
check. And if I understand correctly if the labor tickets dont get fully
process
then that means some of the mateiral dont get backflush correct?  I created
a
report that runs at the end of the day that list all the labor tickets with
a
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
qauntity
remainging is zero but some of the Labor tickets dont have a P=Posted beside
the
tickets.


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
material
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 ...

Replies:

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.