Skip to main content
Question

MRP / DOP - Do not consider unreleased Dop orders

  • August 29, 2024
  • 1 reply
  • 52 views

Forum|alt.badge.img+8

Hello, 

My client uses both DOP and MRP for his manufacturing.

Configured parts are managed with DOP. 
Not configured manufactured parts & purchased parts are handled by MRP.

 

Example :

TOP PART - Configured - DOP

→ COMPONENT1 - Purchased - MRP

→ SUBPART - Manufactured/Not configured - MRP

     → COMPONENT2 - Purchased - MRP

 

With this, DOP will create a Shop order for TOP PART at DOP Release, and MRP will handle the creation of Purchase requisitions / Shop order requisitions should there be shortages.

 

However, we discovered that when we create a DOP structure (DOP header in  status “Unreleased”), and then run the MRP at this moment, purchase requisitions will be created for shortages.

This is dangerous because the structure of an unreleased DOP header can still evolve before being released is case of customizations of a product for example.

→ Is there a way to make unreleased Dop orders not visible by the MRP ?

Thank you,

PL

1 reply

Manxmano
Sidekick (Customer)
Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 27 replies
  • January 8, 2025

This is also causing a problem for my client.

In fact, it is even worse than you say. What I have observed that that even with no DOP structure (let alone a released structure) purch reqs are created for the MRP planned components in the structure.

I don't really understand why, without a DOP structure, reqs are being created for the MRP planned parts. Could this be a bug?

Yes, the CO line “Release to Material Planning” is ON but I would have thought that without the DOP structure this demand should not be seen by MRP. But it is.

As you say, the planner will be managing the DOP and this demand should not be considered until the DOP structure is released.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings