My employer is extremely resistant to spending more money on our computer infrastructure, unless someone does a gifted sales job on the benefits we would get from some investment.

We have heavily modified the SFC/JIT output. There has been an evolution in the mixture used. Currently we have, what we call JT05 (major version # 5 of the Job Tickets), because that is now the form name. This has a copy of the routing description for the part being made, where used that it is needed, what BOM goes into it, what customer it is for, other info, and space for labor reporting start stop time, who worked on it, date, etc. where the layout of stuff on the form, and layout of stuff on JIT/SFC/600 has also been modified to simplify transcription.

When we do a print run, there can be several thousand of these, which then involves a manual task of getting them where they need to go. Getting the paperwork back, ciorrectly filled out, for data entry, is a bigger challenge. It is not unusual for there to be a need for adjustments, to compensate for missing reporting.

This has been supplemented by some reports on the work-in-progress & the work to be done. You know SFC230? We have a different version for each factory department, optimized to that department's setup & other needs. We have what we call "The Schedule" whose birth was cloned from an MRP2 report, but is unlike any MRP2 report in appearance.

Our shipping / invoicing documents have also undergone significant modification.
I think the trouble trend for the future is that different major customers want THEIR documents electronically, in which THEIR definition of form & substance is like they all fantasize about FAX or EDI or FTP or some e-mail attachment, but no two customers share the same fantasy. They are all reinventing this wheel, like on different planets in different universes. Then when it is time for them to pay for our shipment, we would prefer that they identify the invoice they are paying for, but many identify the part #, or the shipping packing tracking delivery ticket#, deduct for RMAs or unearned discounts, or price increases they dispute. Some customer accounting is moving off-shore to personnel who do not have experience in any kind of commerce, such as the purpose of a remittance advice with a check payment.

I suspect this is a challenge for all ERP.

Hello All,

I am looking for a few BPCS users who currently print and assemble shop
floor data packets or other shipping and billing documents using a
manual process. (IE: Print, Manually Assemble, then Mail.)

If your users are doing a lot of manual labor to assemble documents,
please contact me if you're interested in discussing what you're doing.

I'm doing a little research for a new document assembly product we're
working on for the Native iSeries and Windows environments and I need
some input.

I can be reached directly via any of the below methods.


Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Email: richard@xxxxxxxxxxxxxxx
Web Site:
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

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