SAP MM BPML Template: Business Process Master List for Materials Management
A business process master list (BPML) is the one table that says which processes the project covers, who owns them, and how each fits standard SAP. This worksheet is a starting BPML for the Materials Management scope that you edit row by row and export to Excel.
| Process ID | Level 1 area | Process (level 2) | Key transactions | Process owner role | Scope | Fit to standard | Estimated users | RICE objects | |
|---|---|---|---|---|---|---|---|---|---|
Replace the sample rows with your own scope. Process IDs follow the common area-number pattern but you can use your own scheme as long as it is unique. RICE means reports, interfaces, conversions, enhancements, forms and workflows. Check each transaction code exists in your release, as some move to Fiori apps in S/4HANA.
Get your MM scope sanity checked
Share the exported BPML and we will point out missing processes and risky gaps. Optional.
Optional. The tool and every export work without this. No spam.
How to use this BPML
Keep one row per level 2 process. Give each a unique process ID, pick the level 1 area, list the main transactions or Fiori apps, and name a role (not a person) as owner. Set scope to in, out or to be confirmed in your first workshops, and set fit to standard, configuration, enhancement or gap once the fit-to-standard sessions are done. Add rows for your own processes such as subcontracting, consignment or stock transport orders.
- Process ID: unique, never reused
- Owner: a business role who signs off the design
- Fit: drives the RICE and build estimate
Why the BPML matters
Everything downstream hangs off this list: test scenarios, training material, authorisation roles, data migration objects, and the RICE inventory. If a process is not listed, it will not be designed or tested, and it will surface as an issue during user acceptance. The worksheet totals the user count and RICE objects so you can see early where the build effort sits.
Reading the totals
Sort by fit to see how much of the scope is standard against gap. A BPML with many enhancement rows in procurement usually points to approval or pricing requirements that deserve a second look before they are built. A large number of to be confirmed rows late in the design phase is a schedule risk and should be raised to the steering committee.
Common mistakes
Do not copy a vendor BPML of hundreds of rows without trimming it, since unused rows create false test and training effort. Do not use the person's name as owner. And do not mix levels, for example putting a transaction code in the process column. Keep level 2 as a business activity such as goods receipt, and put the transaction in its own column.
Frequently Asked Questions
What does BPML stand for in SAP?
Business Process Master List. It is the structured list of end to end processes and sub-processes in a project scope, with IDs, owners and fit status. SAP Activate based programs often derive it from the SAP Best Practices scope items.
How many MM processes should it contain?
It depends on scope. A typical manufacturing MM scope runs from a few dozen to roughly one hundred level 2 processes. The right number is the number you will design, test and train, not the number in a vendor catalogue.
Should it list transaction codes or Fiori apps?
List whichever your users will actually use. In S/4HANA many processes have both a GUI transaction and a Fiori app, so add both where needed and tag the primary one for training and authorisation design.
Who maintains the BPML?
The functional lead for each area maintains the rows, and the project manager controls changes to scope. After go-live the list becomes the base for the process catalogue and the regression test set.
Once the BPML is agreed, Netray can help you connect it to a private AI layer that answers process and transaction questions from your own documentation, running on your infrastructure.
Related Tools
SAP MM Transaction Codes Reference
Searchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
ERP Migration & SelectionSAP Global Template Rollout Plan Template
Fill-in rollout plan for an SAP global template: scope, local deviation rules, wave plan and governance, laid out so each block becomes one slide.
SAPSAP MM Tables and Key Fields Reference
Searchable list of the core SAP MM tables with their primary key fields and what each stores, including S/4HANA changes.
SAPSAP PO Item Category, Account Assignment and Special Stock Reference
Searchable list of the codes you choose on a PO line: item category, account assignment category and special stock indicator.
More SAP tools
See allKeep exploring
Free tools
- SAP MM Transaction Codes ReferenceSearchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
- SAP MM and QM BAPI and API List ReferenceA searchable list of the common SAP MM and QM BAPIs and S/4HANA OData APIs, what each does, and whether it needs a commit.
- SAP MM Output Form Templates ListA searchable starter list of SAP MM output documents and the output type, application and form technology behind each one.
ERP fixes and how-tos
- SAP PP, PM and MM API: Production Orders, Maintenance Orders and Material MasterWhich SAP APIs cover production orders, maintenance orders and material master (MM02)? OData service names, BAPI alternatives and a sample GET call.
- SAP MM Error Messages List: Reading Codes and Changing Message SeverityHow to read SAP MM message numbers (M7, M8, ME, MEPO), find any message text in SE91, and change message severity with OMT4 and OBA5 customizing.
- SAP MM Errors and Solutions: The Common Ones, by Process StepCommon SAP MM errors by process step, with cause and fix: stock deficit, closed periods, release strategy, blocked invoices and account determination.