Home Button  Buy Button 

Topic:   Cost for Outsourced Assembly

By: BenPosted on: Aug 25 2017 at 12:39:05 PM
Hello. I've got an assembly loaded in miniMRP that we have now outsourced. I'd like to override the "build cost" with the purchased cost. Is there a way to do that other than converting it into a part? I'd rather keep it as a CSAS so that we have easy access to the parts list for product support. Thanks.

By: Ken at DTSPosted on: Aug 25 2017 at 01:20:14 PM
If a record's Type field is "ASSY (Assembly/SubAssembly)", then the Build Cost is calculated from the BOM as one would expect.

If you change an assembly's Type field to "PART (Component)", then the Build Cost field now becomes the Cost Price (EA) field, and this value is populated from the Default Supplier's Price. The assembly's BOM is still in the database and it may be viewed/edited by simply changing the Type field back to "ASSY (Assembly/SubAssembly)" again.

We use this undocumented feature to outsource/insource ASSY's as needed.

We don't use any CSAS's in my organization, but it seems like the above should work for CSAS's as well as ASSY's.

By: BoPosted on: Aug 25 2017 at 01:25:30 PM
I have the same problem. I work round it by having a PART with the same part number as the sub assembly and the letters "OSA" in the revision column (OutSourcedAssembly) This PART appears in the final BOM in place of the actual sub assembly.

Although in some cases I also include the sub assembly/CSAS in the BOM but with a quantity of zero. That means it can exist in the BOM and be exploded and seen if necessary but because qty is zero its cost doesn't affect the build and is never pulled from inventory.

Reply - add a comment to this topic.

You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.

Topic:- Cost for Outsourced Assembly

Enter the numbers.

Your name here is optional