There's something in BPCS customer orders called RMA or Return Material Authorization. This is where the customer has some problem with what was shipped, they return to us for repair or alteration. There is an ORD menu that tracks the RMA from customer service perspective, in which all that data is in the RETURN member of the ORD files, same format as the ORD data. There are BPCS programs to track this that parallel ORD300 capabilities, and you can also do your own QRY/400 or other tools against ORD files member RETURN.


To implement some repairs we had to do stuff in engineering, since the part already contained most of the components needed, and the specific work to be done was non-standard. This WIP can be tracked through the standard engineering and shop order programs.


We were not able to do shop order repairs via BPCS. We did it strictly through modifications in the paperwork flow. In this kind of repairs, it is discovered during the shop order process that some part was not made perfectly, but it could be fixed, and we needed to let later stop in the process know what volume of repairs were coming, by a different path than the good parts. So our tracking document has a box for how much is "in repair" and the QC people, overseeing the repair, have a copy of the tracking document showing where the combined parts need to end up. Our standard routings identify where parts are coming from, and where they are going, by factory department.



I do not mean shop orders but repairs.

Regards,

Isaac A. Antwi

<snip>

>Could anyone explain to me how I could extract data on "Work in
>Progress" in BPCS v4.1 service module.
>
>  Regards,
>
>Isaac A. Antwi



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.