MRP generating Duplicate Demand - Issue/ Bug

Get Help & Support Software Bugs / Issues
1

Hello Cetec Support Team

We hope this email finds you keeping well!

I wanted to reach out to you regarding an issue/ bug we find with MRP that is driving demand for BOMs that are set as ‘Recursive’ when loading the forecast on CETEC and running MRP.

Here is an example of PART# BOMA-0055.

The Sept 2025 Forecast 17915 calls for Qnty: 9 (Demand) for Parent BOMA-0055

Forecast 17915 for BOMA-0055

Parent BOMA-0055 has children sub-Asslys MCHM-0732-04 (Qnty: 1 Ea) and MCHM-0123-22 (Qnty: 1 Ea).

ROP is set as ZERO for Parent BOMA-0055.

Now, lets go to the waterfall for Parent BOMA-0055. The Forecast# 17915-1 in Sept 2025 is calling for Qnty: 9 and QoH drops from 22 to 13.

BOMA-0055 Waterfall

Now lets go to the children sub-asslys and their corresponding Waterfalls:

MCHM-0732-04 waterfall is as below. ROP is set as ZERO:

MCHM-0732-04 Waterfall

You can see above Forecast 17915-1 for Sep 2025 is driving demand for MCHM-0732-04, ALTHOUGH, it has already consumed Parent BOMA-0055 previously from QoH: 22 to QoH: 13.

Now lets go to the next child sub-asslys and their corresponding Waterfall:

MCHM-0123-22 waterfall is as below. ROP is set as ZERO:

MCHM-0123-22 Waterfall

You can see above Forecast 17915-1 for Sep 2025 is driving demand for MCHM-0123-22, ALTHOUGH, it has already consumed Parent BOMA-0055 previously from QoH: 22 to QoH: 13.

Thus, CETEC MRP is driving duplicate demand for the children M-0732-04 & MCHM-0123-22.

Can you please help explain why this is the case, and how we may prevent the system from driving duplicate demand for a Child Sub-Assly/ Component, where the Forecast has already consumed the Parent finished goods QoH?

Is there a setting for this or is this a CETEC bug?

Kindly treat this as URGENT! We cannot run MRP as a result.

Thanks in advance,

KR

2

@cetecerp23 @cetecerp2 @cetecerp19 @cetecerp32 @cetecerp7 @cetecerp26
Can you please help us with the MRP question.

We are unable to run MRP because of duplicate demand for sub-assly/ components that Cetec is generating.

Your immediate help is required.

KR

3

@karthik

I looked into this and found that there may be some confusion on how recursive forecasts function.

A recursive forecast is treated as if you selected Build = Yes when creating an order. Here’s documentation on that process: Enter an Order for a Multi-level BOM - Use Build YES This means there is separate demand for all of the sub assemblies and each sub assembly is expected to be built. MRP and the waterfall won’t take into account whether or not there is QOH for the sub assemblies to where it can be consumed. MRP generates demand for all of the sub assemblies as well to be sure you can order product in time for the order. If you had to use the QOH for another order you would then not have parts for that order because you didn’t order or build any.

The potential way to model your data to only have demand for certain sub assemblies would be to create build forecasts without the recursive function and then create separate orders or forecasts for the sub assemblies you would like to build.

It may also be better to create orders in the system for a lot of your forecasts. You could create orders for the top level and then MRP would generate demand for any parts that you don’t have enough of.

Here’s a bit of documentation on MRP as well: How To Run MRP How To Create a Work Order Using MRP - Build

Please let us know if you have more questions.

Thanks,

Cetec ERP Support