MD61 — Create Planned Independent Requirements

MD61 maintains planned independent requirements: quantities and dates that represent expected demand, entered manually or loaded from a planning tool, used to drive net requirements calculation in MRP for materials without enough firm sales orders to plan against. The structural fact that explains most confusion: PIRs live inside a planning version (00 is the only active version that MRP actually reads; all others are inactive/simulative copies used for what-if planning), and within that version they are split into date buckets whose granularity depends on the period pattern chosen on entry. A PIR that seems to have disappeared from the requirements list has usually been consumed by an incoming sales order under the applicable consumption strategy, not deleted - the record in the background table is reduced, not removed, until it reaches zero.

MD61 sits at the front of the planning chain, before MD02/MD01 (MRP run) and before MD04 (result inspection). It is reached for manually created or manually adjusted demand plans on make-to-stock or planning-strategy materials - typically for materials not managed through an external demand planning or IBP feed. Consultants use it during initial ramp-up of a new material's demand plan, during month-end reforecasting when the planning tool interface has not run, or when testing an MRP scenario in an inactive planning version before releasing it to version 00. Once a forecasting or IBP integration is live, MD61 is used mainly for exception handling and version comparison rather than routine entry, since the interface populates PBIM/PBED directly.

Query PBED filtered by material and plant, restricted to the planning version in question (00 for active), and sort by date. Compare the raw quantity field against what MD04 shows in the stock/requirements list for the same material/plant/version - a mismatch usually means MD04 is showing consumed remaining quantity while PBED still holds the original entry, or MRP has not been rerun since the PIR was changed. Cross-check PBIM for the requirements type actually stored against the requirements type expected from the material's planning strategy in the material master.

The transaction and underlying tables are unchanged on S/4HANA; MD61 still runs as a classic GUI transaction, typically embedded in the Fiori launchpad rather than replaced by a dedicated Fiori app for manual PIR entry. Organizations using SAP IBP for demand planning push forecasts into the same PBIM/PBED structures through integration, reducing manual MD61 use to exception handling, but the transaction itself has not been restructured.

This is functional PP/demand planning territory, owned by whoever maintains the demand plan or forecast interface. ABAP involvement is limited to custom interface programs feeding PBIM/PBED; Basis is not normally involved. A good handover includes material, plant, planning version, the period pattern used, and the timestamp of the last MRP run against the same version.

MD62 is the mass-change counterpart to MD61 and is the first place to check when a bulk update to existing PIRs behaves differently from a fresh MD61 entry. MD04 and MD05 are the diagnostic views to confirm whether a PIR entered in MD61 is actually visible to and consumed correctly against MRP results. MD02 and MD01 are the downstream transactions that actually net the PIR against stock and orders - any apparent MD61 discrepancy that persists after rerunning one of these usually points back to version or requirements-type mismatch rather than an MD61 defect.