Skip to Content

The auto generated PR from Third-party sales order was not included in MRP

Dec 19, 2017 at 05:55 AM


avatar image

We use the third-party SO to generate PR automatically, and set the SO not included in MRP calculation. (So the SO and auto generated PR both not included in MRP). But when we convert SO to DN, the DN was included in MRP, then after MRP run, system generate an PR automatically, this means the PR was duplicated. Then we change the settings of requirement class, to let the SO included in MRP, but still the PR was not included in MRP, after MRP run, system generate a duplicated PR as well.

10 |10000 characters needed characters left characters exceeded

Does DN mean outbound delivery (VL01N)?

As far as I know, standard third-party order processing does not involve shipping activities from your end, but this is the only context where I have encountered this abbreviation.

If this is not the standard TPOP that most people know about (with TAS and CS), it may be a good idea to explain a bit more about the setup so that members can respond with valid suggestions.


Hi Veselina

We use the individual procurement (with TAB), so we will have the DN(VL01N). Thanks for your comments.

* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Caetano Almeida
Dec 19, 2017 at 01:27 PM


Third-party purchase requisitions are not relevant to MRP. In order to ensure that MRP will not generate a new requisition to cover the sales order, you should ensure that the sales order is not relevant to MRP, by changing the requirement type/class settings.



Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Caetano,

Thanks very much for your reply, It's not TAS, we use the TAB to generate individual PR. And the issue was this PR not included in MRP calculation.



I understand your issue and this is a standard system design in this case. This requisition is not relevant to MRP by default and the solution is to make the sales order not relevant to MRP.