Re: shop order posting -- BPCS-L

In version 405 CD BPCS lets us post more transactions to operations that are coded closed, so long as the last operation and the order is still open.

You may want to develop a program modification to selectively re-open closed orders and closed operations. Remember that what closes operations and orders is the arrival of labor transactions against a quantity to be made, so it is best to do order maintenance early if the quantity to be made is to be changed.

BPCS can second guess us, and not do a good job of it. Suppose you have several orders open on the same item, and you report labor that is in excess of what is called for by an order. BPCS will try to find some other order, other than the one you posted, to accept the work.

If you need to back that transaction out, you need to back it out from where BPCS posted it, not from where you originally placed it.

We do not count scrap as work done, but BPCS does. Suppose we needed to make 1,000. In reality when something gets scrapped, we immediately try to make replacement parts. Suppose we made 975 and scrapped 50 ... this means we still need to make some, either repair some of the rejects, or use up more raw material. But BPCS may have closed the order because 975 made plus 50 scrap is more than the 1,000 we supposed to make.

This is another reason to either modify BPCS, make order quantity artificially large until all reporting completed, or have a program to selectively reopen closed orders and operations before running a purge.

Human error exists with all of us.
so a company has to have systems in place to detect and deal with.

Those systems may need to allow for the auditability of what the heck we were doing. A total reversal of the 100 misposting, and a corrected posting of 10 is more keying than negative 90, but is easier for auditors to figure out what was going on and why, especially if the negative 100 is in most all respects a mirror to the 100 misposting.

There is also the issue of different people stumbling over the same error, and fixing it. So that some errors get fixed more than once, and some errors not get caught.

BPCS supports input with reason codes.
Perhaps we ought to have a reason = reversing a misposting.

We do most of our labor reporting via JIT600 which handles the inventory implications. Suppose we need to back out a misposting. JIT600 will not let us post inventory reversals, so what we have to do is back out the labor part via SFC600 and the inventory part via INV500.

, you wrote:

version 6.1

suppose an employee posts a qty of 100 to and operation instead of 10
(which it should have been). this is more that the order qty so it
closes the operation. but the operation is not really complete. so now
the next operator cannot post to this operation.

can you post a negative 90 to the operation to correct the erroneous
posting an reopen the operation so that it can again be posted to. if
not, any ideas on what to do to allow the other operators to post to the
operation?
_