InvcDtl and Part Tran History Costs Issue

I have a tricky finance question, and I am not a finance person. We are looking at a report I created to help identify costs on our jobs. This comes from an old post here: Unit Cost Truth - Kinetic ERP - Epicor User Help Forum

The problem we face today is that a handful of discrepancies are popping up between the costs on the InvDtl table, and the costs on the Part Transaction History. Notably, we have received parts on a subcontract PO for $18 per piece. I can see that on the PO, and in Part Trans History. When I run my report to pull invoice data, I am getting a higher value for subcontract unit cost at about $53. We can’t tell why this increase is happening. I can see it in the Part Tran.

Would any finance folks be willing to chat with me for a few minutes about some specifics to see if we can make sense of this?

Here is a copy of my BAQ that pulls in the Invoice Details:
ProfitByPart.baq (28.0 KB)

Here is a snippet of our Part Transaction history showing the sub unit cost received at $18, then shipped at $53. We can’t figure out what caused it to change to $53.

Date Type Quantity Running Total Trans Quantity PO Order PO Pack ID Ship Pack ID Invty Amount Mtl Unit Cost Lbr Unit Cost Bur Unit Cost Sub Unit Cost Mtl Bur Unit Cost Mtl Mtl Unit Cost
4/9/2025 MFG-CUS 50 5 50 0 33973 118348 FALSE 3276.02 10.33274 0.45171 1.35309 53.38286 0 10.33274
4/9/2025 MFG-CUS 40 5 40 0 33973 118348 FALSE 2620.82 10.33274 0.45171 1.35309 53.38286 0 10.33274
4/9/2025 MFG-CUS 25 5 25 0 33973 118348 FALSE 1638.01 10.33274 0.45171 1.35309 53.38286 0 10.33274
4/7/2025 MFG-STK 5 5 5 0 0 0 TRUE 109.85 3.37987 0.14782 0.44259 18 0 3.37987
3/27/2025 PUR-SUB 119 0 119 130945 0 27972 0 FALSE 2142 0 0 0 18 0 0
3/22/2025 PUR-SUB 1 0 1 130945 0 18419 0 FALSE 18 0 0 0 18 0 0
  1. “Date” is what, tran or sys date?
  2. This is a single job, right?
  3. And it has 2 or more demand links? One to stock and one or more to order?
  4. What is/are your costing method(s)?
  5. Do you use - what’s it called - Split Mfg elements? (company or site config somewhere)

But it is odd - if anything I expected the MFG-CUS to be as expected and the MFG-STK to be the oddball. But it’s opposite.

EDIT: It’s called “Enable Mfg Cost Elements” and is on Company Config.

The job field is JobHead.SplitMfgCostElements

1 Like

Date is the Date column From Part Transaction History Tracker. I think it is PartTran.TranDate.
This is a single job. There is demand from a sales order, and a stock line.
We use Last cost method. We do not use split mfg elements. (It is not checked in Comp config).

1 Like

I ask because PartTran.SysDate is the real-life date it happened; TranDate can be backdated. So I wonder if the transactions happened in a different order in real life. (Doubt it, but have to ask.)

For the PUR-SUB, were there other PUR-SUB transactions (on different jobs even) for the same part number? Especially between 3/27 and 4/9 (assuming those are the real-life dates).

Even still, I expected that the MFG-CUS ignores that sort of thing and would just push the actual job costs on through.

But here we do one shipment per job, and you have 3 plus the MFG-STK.

And even with THAT, I’d expect the unit costs to be zero, not $53.

Sorry to stop there, but I have to leave for the day.

1 Like

I did find that Tran and Sys dates are a bit different, but I am not sure it helps resolve the issue.
hmmmm… :thinking:

Our other PUR-SUB transactions are all back in 2018 since we haven’t run this jobs since then.
Thanks for looking at this with me! I appreciate it. Have a great weekend!

1 Like

Apparently the split merge thing only works correctly if the related calandar is using consecutive hours that are enabled… But you are not using it.

Other thought, what are you last run parameters of your capture COS/WIP?

1 Like

Is there a way to look this up, or would finance have to remember what they choose? In COS/WIP the little text box shows:
Starting 4/1/2025
Ending 4/30/2025
Post to General Ledger = NO
Post Cost of Sales / MFG Variance = YES

Falling asleep…

  1. Should be able to use “Save default” to remember the parameters
  2. Noticed the post to GL = false…
  3. Is it possible that an earlieat apply date was set preventing some of them posting…

Cheers

1 Like