Skip to main content
Question

Cost rollup behavior changed after 26R1 – Use Manufacturing Costs on Purchase Cost Template

  • September 30, 2026
  • 1 reply
  • 49 views

Forum|alt.badge.img+5

Hi,

we are experiencing an issue with multilevel cost calculation for purchased parts containing manufactured parts on lower levels, which appears to have started after upgrading to IFS Cloud 26R1.

The structure is approximately:

Purchased Part → Manufactured Part → Manufactured Part → Purchased Part

The Purchase Cost Template has both Use Manufacturing Costs and Use External Acquired Costs enabled.

Before the 26R1 upgrade, the multilevel cost calculation worked correctly with this configuration. However, after the upgrade, running All Levels Part Cost Calculation into Cost Set 2 does not roll up the lower-level manufactured structure and its costs.

We were able to reproduce the behavior on multiple parts.

As a test, we disabled Use Manufacturing Costs while keeping Use External Acquired Costs enabled and recalculated the same part. Without any changes to the product structure or routing, the complete multilevel structure and costs were rolled up correctly.

Example:

  • Previous Cost Set 1 (calculated before 26R1): 96.14827 CNY
  • New Cost Set 2 with Use Manufacturing Costs = Yes: 19.777 CNY – lower levels missing
  • New Cost Set 2 with Use Manufacturing Costs = No: 96.14827 CNY – complete multilevel structure

The recalculated result with Use Manufacturing Costs disabled therefore exactly matches the previous Cost Set 1 result.

Has there been any change in the Cost Rollup Control logic in 26R1, specifically regarding Use Manufacturing Costs for Purchase Cost Templates?

Is this expected behavior in 26R1, or could this be a regression in the multilevel cost calculation?

1 reply

majose
Hero (Employee)
Forum|alt.badge.img+15
  • Hero (Employee)
  • September 30, 2026

Hi ​@dockal_d 

Cost BOM Explosion logic was restructured heavily a couple of releases back due to changes in how we establish standard cost for Co- and By-Products. Earlier we couldn’t calculate a standard cost for these types of parts using Cost Distribution. Now we can.

 

Unfortunately you have discovered a problem here. Great that you found a workaround.

Anyway, since it is a purchased part and we have both Use Manufacturing Costs and Use External Costs set to true, it feels natural to explode the purchase structure. Right now, looking at your setup, we first test the Use Manufacturing Costs flag, and since it says YES, logic decides to try use a Manufacturing Structure. It should not in this case.

Please log a support case.

Best Regards,

Mats