PRs created from MRP can be mass released in ME55 manually

What the strategy does present is technically close - - it prevents the PR from being held / issues an mistake - (PRs are created, they tin beryllium wide released successful bequest tcode ME55), nevertheless the manual changing of the PRs (and not the POs created from PRs) is incorrect.

The script uses 2 antithetic procurement types - 1 semi-automatic (MRP), the different being manually changing the PRs - which is not recommended to bash with the MRP process. 

MRP creates PRs based connected the requirements, these are converted to POs, but the main constituent is unconverted PRs are absorbed "back" into MRP (which generates caller PRs connected the adjacent MRP run).

If a PR is manually changed capable (but not converted to PO), this "unlinks" the PR from MRP (and the wide requirements driving it) - it creates an "orphan" PR.

Holding PRs is not imaginable if utilizing different procurement processes to make said PR (which is not the lawsuit here, arsenic MRP generates it).

To guarantee MRP works correctly, lone marque manual changes to the PO lone erstwhile converted from PR.

(this means MRP does not bid again), bash not marque changes to the PR papers to guarantee MRP calculates / generates correctly.

Hope this clarifies!