× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



As of version BPCS 405 CD the program that does it for us is within the job stream of JIT620C.

Basically, labor transactions are posted via JIT600C (CL) which is SFC600 (RPG) under the covers, and there is a screen showing the components of what got made, where substitutions can be made, or function key to accept as is.

This BOM within the shop order, starts its life as a copy of BOM from MBM master file, as it existed at the time of the shop order creation, not reflecting any subsequent engineering changes, then this BOM (now in the FMA file) can be altered through shop order maintenance, or altered at time of individual labor transaction reporting.

After JIT600C inputs the batch, JIT610C and JIT620C can run, both of which have a ton of other programs within their jobstream.

You might find it useful to explore the IBM cross-reference tool at GO CMDREF to see all the stuff called by the CL programs, and drill down, since it only shows 1st level children, so you have to rerun it on children to get to grandchildren and great grandchildren of programs called by programs.

Completion transactions for final operation generate PR transactions = production receipts. Assuming the BOM is correctly coded with what operation consumes what materials, then when some quantity made or scrapped at some operation, the corresponding components needed to get that becomes CI transactions.
Scrap transactions also end up as RJ.

Thus, errors of omission in BOM coding can result in missing backflushing. It is easy enough to list BOM to see which items are inadvertently coded to be invisible to backflushing.

It is also possible to enter transactions individually via INV500.

Within the ITH file layout, there is a labor ticket # which is the same # used in the FLT file layout, and which you can link to get more info on the transaction, if in fact it came from JIT600. If it came from INV500 the labor ticket # field is not populated in ITH.

Does anyone know the program name that writes out the backflush records
to ITH. "CI" transactions in our system.

Version 6.01.1



Thanks,

Daniel



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.