|
Antwi, Repairs can be "no charge" to correct product that was shipped with a defect, or they can be a separate part of your business that is involved with repairing equipment for a charge or against a warranty claim. The two distinctions are important since one would normally be returned on an RMA (as Al Mac has mentioned) where the other may only have a shipping manifest referencing a PO for the work to be done. The first situation is normally handled by a QA or Engineering generated document that may be a "generic" BPCS repair routing with a manual material list created to identify replacement parts. All of this is very ad hoc, and specific to each individual company's procedures. The other situation (actual repair services done for customers for things such as fork lift trucks) is usually handled by creating order specific Shop Orders that are routed through a "virtual" production area or department. By virtual I mean that a company may use the same equipment that is used to make new equipment, but will "reserve" a portion of the capacity that will be assigned to the separate "virtual" work center ID to accommodate repair orders. The reason for doing this is to separate the different type of orders flowing through the same work centers, since the repair orders usually have a "premium" cost associated to them. On the other hand, if by repairs you mean tracking equipment repairs done by the Maintenance department, then you would be talking about the BPCS Maintenance Management System that was probably called Elke in your version (if it was even available). In that case, the history would be in a file that is identified something like EWSHSTXX in a library that begins with something like PMF, PMO, PMP, etc. Frederick C. Davy, CPIM, PMP Business Systems Analyst Interface Solution, Inc. Phone: (315) 592-8101 Fax: (315) 592-8481 e-mail: fcdavy@xxxxxxxxxxxx "antwi, isaac a." <iantwi@xxxxxxxxxxxxxxxxxxxxxxx> Sent by: bpcs-l-bounces+fcdavy=sealinfo.com@xxxxxxxxxxxx 09/11/2006 10:42 AM Please respond to SSA's BPCS ERP System <bpcs-l@xxxxxxxxxxxx> To "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> cc Subject Re: [BPCS-L] Work In Progress I do not mean shop orders but repairs. Regards, Isaac A. Antwi -----Original Message----- From: bpcs-l-bounces+iantwi=anglogoldashanti.com.gh@xxxxxxxxxxxx [mailto:bpcs-l-bounces+iantwi=anglogoldashanti.com.gh@xxxxxxxxxxxx] On Behalf Of Al Mac Sent: Monday, September 11, 2006 12:46 To: SSA's BPCS ERP System Subject: Re: [BPCS-L] Work In Progress When you say "Work in Progress" do you mean shop orders that have been released to the factory, but not yet completed? Other meanings can include item #s between raw materials and completed customer parts, factory work between discrete item#s, whether shop order exists or not, customer orders not yet fulfilled. INV300 F22 in 4.05 CD gets at a list of all orders on an item (customer, purchase, factory, outside, inter-facility resupply etc. etc.), their work-in-process status, when next installment due. File FSO has summary on each shop order File FOD shows work in progress from perspective of labor reported File FMA shows work in progress from perspective of materials consumed SFC300 inquires into these files I do not know if JIT was available at 4.1 File FLT has history of updates to FOD File ITH has history of updates to FMA ... in our case transactions CI consumes the material PR receives completed parts RJ records scrap There is a report CST270 that we found to be so unreadable that we modified to not show the additional description lines, and other alterations.
Hi 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 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.