Skip to main content

24.2.1

On the first receipt (i.e., partial) of a FIFO shop order where the operations are using a Fixed Resource Share and are being reported through auto reporting, I cannot determine how the Machine Cost is calculated.

Setup:

  • Manufactured part = FG1, valuation method = FIFO.
  • Routing op 10, WC A, 1 unit/hour, fixed resource share = 0.3.
  • Routing op 20, WC B, 1 unit/hour, fixed resource share = 0.3.
  • Work Center A, cost = 30.00/hour, no overheads
  • Work Center B, cost = 20.00/hour, no overheads
  • FG1 product structure consists of only one component (COMP1, valuation = FIFO), QPA = 1, Estimated Material Cost = 1.00, Cost Set 1 = 1.00. Nothing on the Produced Parts tab.
  • FG1 Cost Set 1 = 16.00, template M-110 with only standard buckets.
  • Zero on-hand inventory of FG1.

Execution:

  • Shop Order lot size = 5. This is the only shop order in the system for FG1.
  • Receive (1), backflushing and auto report operations.
  • OOREC transaction for 44.00 shows Cost Buckets:
    • 110 = 1.00
    • 300 = 43.00

Where did this 43.00 come from?

Forgot to include a screen shot of the WIP Status for this shop order.

 


Hi Matt,

When it comes to inventory valuation methods FIFO/LIFO but also Standard Costing with Part Cost Level set to Cost per Batch, system tries to smooth the actual cost reported so far with the expected remaining cost. Otherwise it could be super-nervous. One OOREC transactions goes sky high and then next one very low.

So system takes the 15 (actual cost) and add 4* 30 + 4 *20 (expected remaining cost) = 215 

And then divides this with 5 => 43

But when calculating the expected remaining machine cost in the FIFO/LIFO method system don’t consider the resource share :-(

It should! So we have a bug here Matt, and I am really sorry for that. Can you please report a support case for it.

Best Regards,

Mats - with an ‘s’ at the end


@majose CS0345530 has been entered.


From IFS R&D:

This is to inform you that this core product error is now planned to be resolved in the following updates:
24.2.6 - 24R2 SU6, 25.1.0 - 25R1 GA, 25.2E.0 - 25R2 EA.

Please note this is for planning purposes only and is subject to change. Once the error is resolved, we will confirm which updates include the fix.


Reply