Am I Crazy?/ BOM Cost Report Extended Labor Cost

Does anyone know what is causing this issue with certain assemblies in our standard BOM Cost Report?

Each report is being ran for a part with only one approved revision on a “Single-Level” parameter. Notice under this image where the unit cost (0.8174) multiplied by the quantity (1.5300 GAL) equals the extended cost (1.2506). This behavior is replicated further in the highlighted fields further down.

However in this scenario, the unit labor cost (2.4984) multiplied by the quantity of (133.9990 YDS) equals (283.3558). 2.4984 x 133.9990 = 334.7831. What is causing the extended cost to display such a smaller amount than what should be calculated? The only difference is we have setup hours along with a costing lot size for PS-864 assembly. Any help is greatly appreciated.

1 Like

Is it possible that job was started and some of the labor previously captured?

This report runs strictly off Routings/BOM’s for the parts? It isn’t a job costing report. Maybe I am not understanding correctly.

Ah that’s my bad. I was thinking of it like the COS/WIP.

In looking at the report and your numbers, aren’t you crossing Material and Labor? I don’t know why in the first example the math works out that you multiply the GAL times Labor Cost it equals the Extended Labor Cost. If you look at the Material Cost column the math works here as well. When you jump to the second example, the math works for Material Cost as it should and doesn’t for Labor as they are two different things.

Not 100% sure what you mean by crossing the material and labor?

The assumption is not always that producing 1 unit of material takes 1 unit of labor. It looks like that is the case for you (1 unit/hr)

1 Like

Actually, maybe that’s your issue. Can you confirm that operation has 1 unit/hr or 1 hr/unit as the ProdStandard?

PN159 has prod std <1 hours/unit

LT149 does have prod std =1 hours/unit

PS-864 (example with different behavior) has 2 operations where standards also are <1 hours/unit, but as you can see does include some setup hours.

I would guess the setup hours make the difference. I’m fairly certain that the per unit labor cost of setup decreases as the quantity of units increases. Not positive about that, you may want to do some testing.

For this one, that’s for production of 1 YD of that part?

Correct.

That makes me think it’s got to be the Setup Hours. Since setup hours are not multiplied by quantity as ProdStandard / Production hours are, the per unit labor cost of 1 unit will be higher than the per unit labor cost of 133.9 units. I’m guessing that’s what happened here. Can’t be sure without testing or playing with it.

Setup hours and whatever you have for costing lot size right? Or does that not come into this report?

It does come in for calculating the labor cost for the part, but I didn’t think would have anything to do with the extended cost. But I am going to do some digging and see if I can figure out the math behind it.

Any fixed costs (like setup) are going to be spread across (divided) by your costing lot size, to come up with your per unit labor fixed cost.

1 Like