# SAP MM BPML Template: Business Process Master List for Materials Management > Source: https://netray.co/tools/sap-mm-bpml-business-process-master-list-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable MM business process master list with process IDs, transaction codes, owners and in or out of scope status, exportable to Excel. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP project team - Business process owner - MM functional consultant ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Process ID **Key:** pid **Type:** text #### Level 1 area **Key:** l1 **Type:** select **Options:** - Master data - Procurement - Inventory management - Invoice verification - Valuation - Consumption based planning #### Process (level 2) **Key:** process **Type:** text #### Key transactions **Key:** tcodes **Type:** text #### Process owner role **Key:** owner **Type:** text #### Scope **Key:** scope **Type:** select **Options:** - In scope - Out of scope - To be confirmed #### Fit to standard **Key:** fit **Type:** select **Options:** - Standard - Configuration - Enhancement - Gap #### Estimated users **Key:** users **Type:** number **Format:** integer #### RICE objects **Key:** rice **Type:** number **Format:** integer **Rows:** **Pid:** MM-001 **L1:** Master data **Process:** Create and maintain material master **Tcodes:** MM01, MM02, MM03 **Owner:** Material master data steward **Scope:** In scope **Fit:** Configuration **Users:** 12 **Rice:** 2 **Pid:** MM-010 **L1:** Procurement **Process:** Purchase requisition to purchase order **Tcodes:** ME51N, ME21N, ME28 or ME29N **Owner:** Procurement manager **Scope:** In scope **Fit:** Standard **Users:** 45 **Rice:** 3 **Pid:** MM-011 **L1:** Procurement **Process:** Request for quotation and vendor selection **Tcodes:** ME41, ME47, ME49 **Owner:** Strategic buyer **Scope:** To be confirmed **Fit:** Standard **Users:** 8 **Rice:** 0 **Pid:** MM-012 **L1:** Procurement **Process:** Outline agreement (contract) management **Tcodes:** ME31K, ME32K, ME33K **Owner:** Strategic buyer **Scope:** In scope **Fit:** Configuration **Users:** 10 **Rice:** 1 **Pid:** MM-020 **L1:** Inventory management **Process:** Goods receipt against purchase order **Tcodes:** MIGO, MB51 **Owner:** Warehouse supervisor **Scope:** In scope **Fit:** Standard **Users:** 60 **Rice:** 2 **Pid:** MM-021 **L1:** Inventory management **Process:** Physical inventory count and posting **Tcodes:** MI01, MI04, MI07 **Owner:** Inventory control lead **Scope:** In scope **Fit:** Configuration **Users:** 15 **Rice:** 1 **Pid:** MM-030 **L1:** Invoice verification **Process:** Logistics invoice verification **Tcodes:** MIRO, MR8M, MRBR **Owner:** Accounts payable lead **Scope:** In scope **Fit:** Standard **Users:** 14 **Rice:** 2 **Pid:** MM-040 **L1:** Consumption based planning **Process:** Material requirements planning run **Tcodes:** MD01N, MD04, MD07 **Owner:** Production planner **Scope:** In scope **Fit:** Configuration **Users:** 9 **Rice:** 1 **Totals:** #### Total estimated users **Key:** users **Agg:** sum **Format:** integer #### Total RICE objects **Key:** rice **Agg:** sum **Format:** integer #### Processes listed **Key:** pid **Agg:** count **Format:** integer **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use this BPML **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What does BPML stand for in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap mm bpml template, sap bpml template excel, business process master list sap, sap mm business process list, sap mm process hierarchy, sap activate bpml, sap mm scope list, sap mm process owners --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json