Co-Parts: how to define a yield < 1 relative to the primary part?

I haven’t looked at co parts in quite a while, but a customer asked today, how to define a co-part where the primary part A is produced in batches of 100, and out of that process, we get 24 of part B, every time. In Engineering Workbench, in the Yield field, it only allows integers.

Must we have the Advanced Production license to define this?

Can I ask why they wouldn’t set Part A’s Yield Per to 100 and Part B’s Yield Per to 24?

:exploding_head: :exploding_head: :exploding_head: :exploding_head:

Is that how you do it? When I was using co-parts before, we could only put in integers like the OP says. Even Epicor was like, “sorry, looks like you can’t use it”. I think they eventually told us to make the lesser quantity the main part and the higher quantity the co-part.

But seriously, you enter the actual quantities that are produced?

According to the Field Help, the Yield Per is a field that defines how many parts will be made when one quantity of the primary part is manufactured. The total part quantities produced is calculated by multiplying each co-part’s Yield Per value against the primary part’s quantity.

The logic is Co-Part Quantity = Primary Part Quantity x Yield Per

Total Part Quantity = Primary Part Quantity + Co-Part Quantity 1 + Co-Part Quantity 2 + Co-Part Quantity 3 and so on…

With that said, if you create a job for 1 piece of part A and part A has a Yield Per of 100 and Part B has a Yield Per of 24, you would get 124 pieces total: 100 pieces of A and 24 pieces of B.

Give it a try :smiley: But note that the job MUST BE for a quantity of 1 for each “set” of parts you want to produce.

The Material Cost Factor and the Labor Cost Factor are integers, too. I was calculating material for injection molding (left/right, top/bottom, etc), so I would take the total shot weight of all parts, then divide the weight of part A by the total shot weight. If it came out with two decimal places, I would multiply that amount by 100. I would do the same for the other part (multiplying it by 100).

Example: Part A weighs 10 grams and Part B weighs 15 grams. Total shot weight is 25 grams. To get the amount of resin used for each part, divide 10 by 25 for part A; which equals .4. I would then multiply that by 100 (for 100%) to get 40 and subtract the 40 from 100 to get 60 for Part B.

1 Like

:exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head: :exploding_head:

WOW!! Great out of the box thinking @Beth , now I know why everyone calls you the Co-Part Queen :laughing:.

I am going to start using co-parts again at my current company. This is going to be so helpful. I would say that as long as a company is using MRP, this must be pretty easy to handle.

2 Likes

Let’s go @Beth !!! I am definitely going to need to talk with you once we go live on Kinetic.

1 Like

So I just tried that, and the result is pretty weird. I set the Yields at 100 for copart A and 24 for copart B. I created a job for qty 100 for copart A. In Job Entry, it looks like the job qty is only 1, but below you see the qty 100 and 24 for the coparts in the demand link. Then, if I add a material to the BOM, it’s calculating from the job qty of 1 vs. 100.


Your material will need to be all the material required to make 100 A parts and 24 B parts. Is that how your material is set up? It has to be all the material needed to create one set of parts. Then if you make 2 (sets), the material will double and you will get double the parts. Does that make sense?

1 Like

Wow, agreed, not how I thought of this.

I have done a co-part job once ever, and the instructions I came up with were pretty ludicrous - because I had the math wrong, I see.

So does this then prevent this bogus error that I had made note of?

Because it was fighting me at every step when trying to receive.

Also, thanks to @jkane for the :exploding_head: reaction. And @josecgomez of course.

What’d I do?
Animated GIF

:exploding_head:

That

I assume this is the post where @jkane decided he needed the reaction option.

image

1 Like

ooooooooooh I see I was so confused I mean don’t get me wrong I’ll take credit that isn’t mine with impunity just ask @Banderson but I at least know it :rofl::rofl::rofl:

Drama Why Am I Here GIF by The Bachelorette

I ask myself that about you EVERY DAY! :yum:

all right we are derailing this thread… Back to the topic at hand.

Sorry Not Sorry Friends GIF

Co-parts are soooooooo confusing and I’ve had a lot of practice at tearing my hair out when trying to figure it out! Thank goodness it’s been a few years so my hair has grown back :wink: I’ve had to think outside of the box many times with this feature. There are some drawbacks though…

We have a similar situation with half sheets where we get 23 of part A and 9 of part B. We have them setup as concurrent co-parts. If you use sequential which is the default then it will try to add the quantities together on your job.


This works for accounting to get the right information and for operations to do their reporting.

The BOM is setup for 1 of part A and then these other factors do the rest of the work.

I will add that it is super confusing at first and if we could find another solution we would.

This was my hangup for so long. Thank you for unlocking another tool in the Epicor toolbox.

1 Like