# SAP MM Gap Analysis Examples and Fit-Gap Template > Source: https://netray.co/tools/sap-mm-fit-gap-analysis-template-with-examples > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable SAP MM fit-gap worksheet with realistic example rows, resolution options and effort totals. ## Category sap ## Erp SAP ## Audience - SAP MM consultant - Project lead - Business analyst ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Req ID **Key:** id **Type:** text #### MM area **Key:** area **Type:** select **Options:** - Master data - Purchasing - Inventory management - Invoice verification - MRP - Subcontracting - Valuation - Reporting #### Business requirement **Key:** requirement **Type:** text #### Fit rating **Key:** fit **Type:** select **Options:** - Fit - Partial fit - Gap #### Resolution **Key:** resolution **Type:** select **Options:** - Standard configuration - Process change - Standard Fiori app or report - Enhancement (BAdI, user exit) - Custom Z development - Add-on or third party - Out of scope #### Priority **Key:** priority **Type:** select **Options:** - Must - Should - Could #### Effort (days) **Key:** days **Type:** number #### Day rate **Key:** rate **Type:** number **Format:** currency #### Cost **Key:** cost **Type:** number **Expr:** days * rate **Format:** currency **Rows:** **Id:** MM-001 **Area:** Invoice verification **Requirement:** Block invoices outside price and quantity tolerance by vendor **Fit:** Fit **Resolution:** Standard configuration **Priority:** Must **Days:** 2 **Rate:** 900 **Id:** MM-002 **Area:** Purchasing **Requirement:** PO approval by value, plant and material group **Fit:** Fit **Resolution:** Standard configuration **Priority:** Must **Days:** 4 **Rate:** 900 **Id:** MM-003 **Area:** Purchasing **Requirement:** Landed cost split by freight, duty and insurance on import POs **Fit:** Partial fit **Resolution:** Standard configuration **Priority:** Should **Days:** 6 **Rate:** 900 **Id:** MM-004 **Area:** Subcontracting **Requirement:** Track serial numbers of components shipped to the subcontractor **Fit:** Gap **Resolution:** Enhancement (BAdI, user exit) **Priority:** Must **Days:** 12 **Rate:** 1100 **Id:** MM-005 **Area:** Master data **Requirement:** Block POs when a supplier certification has expired **Fit:** Gap **Resolution:** Custom Z development **Priority:** Should **Days:** 15 **Rate:** 1100 **Id:** MM-006 **Area:** Inventory management **Requirement:** Customer-owned tooling held on our site **Fit:** Partial fit **Resolution:** Process change **Priority:** Could **Days:** 3 **Rate:** 900 **Id:** MM-007 **Area:** MRP **Requirement:** Planner worklist of MRP exception messages by MRP controller **Fit:** Fit **Resolution:** Standard Fiori app or report **Priority:** Must **Days:** 1 **Rate:** 900 **Id:** MM-008 **Area:** Reporting **Requirement:** Weekly report of open POs past due with supplier contact **Fit:** Partial fit **Resolution:** Standard Fiori app or report **Priority:** Should **Days:** 3 **Rate:** 900 **Totals:** #### Total effort (days) **Key:** days **Agg:** sum **Format:** number #### Total estimated cost **Key:** cost **Agg:** sum **Format:** currency #### Requirements **Key:** id **Agg:** count **Format:** integer **Summary:** #### Average effort per requirement **Key:** avg_days **Expr:** sum_days / count **Format:** decimal #### Average cost per requirement **Key:** avg_cost **Expr:** sum_cost / count **Format:** currency **Primary:** true **Notes:** Example rows only. Replace them with your requirements. Rate is a blended day rate for the type of work, so change it per row (configuration usually costs less than custom development). ## Content **Intro:** A fit-gap analysis lists each business requirement for materials management, rates it against standard SAP, and says how every gap will be closed. The worksheet has example rows you can replace, plus an effort and cost total you can export to Excel. **Sections:** #### How to use the worksheet **Body:** Add one row per requirement, written as a business need and not as a solution. Pick the MM area, then rate the fit. Fit means standard SAP does it with configuration or master data. Partial fit means standard covers most of it but needs a process change or a small addition. Gap means standard cannot do it. Choose the resolution, set the priority with Must, Should or Could, and add days and a rate. The totals update as you type. Run it in a workshop and fill the fit column live. **Bullets:** - Write needs, not solutions - Rate fit against your target release, not the old system - Give every Gap a resolution and an owner - Review Must gaps first #### Examples of fit, partial fit and gap in MM **Body:** Tolerance based invoice blocking and PO release strategies are normally fits, handled in configuration. Landed cost for imports is often a partial fit: planned delivery costs and condition types cover most of it, but allocating cost to the right valuation needs design. A requirement to track serial numbers of components sent to a subcontractor is usually a gap, because the standard subcontracting process tracks quantities and batches. Expiry-based supplier blocking is also commonly a gap that needs an enhancement. #### Choosing the resolution **Body:** Prefer the cheapest option that keeps you on the standard upgrade path. In order: configuration, a process change, a standard Fiori app or report you did not know existed, a released enhancement such as a BAdI, a custom development, and only then an add-on. Each step costs more to build and test and also in every later upgrade. For an S/4HANA project, check the simplification list before rating anything as a gap, because some old transactions have replacements that close the requirement. #### Common mistakes **Body:** Teams rate a requirement as a gap because users want the screen to look like the old system. Others skip the effort estimate and find at go-live that custom items are the largest cost. Do not mix scope: keep MM requirements here and track SD, PP and FI items in their own worksheets. Finally, keep the sign-off record, since this list is the contract for what the project builds. **Cta:** If many of your gaps are reports, lookups and approvals around the ERP, a private AI layer can often close them without custom ABAP, and it can run on-prem next to your SAP system. **Faq:** #### What is a fit-gap analysis in SAP MM? **Answer:** It compares each business requirement for procurement and inventory to what standard SAP MM does. Each item is rated fit, partial fit or gap, and every gap gets a resolution such as configuration, process change, enhancement or custom development, with effort. #### What are typical SAP MM gaps? **Answer:** Common ones are supplier certification checks before a PO, serial number tracking in subcontracting, special approval flows beyond release strategies, customer specific labels and documents, and reports that combine several modules. Each can be solved by enhancement, but first check for a standard app. #### How do I estimate effort for a gap? **Answer:** Split it into functional design, build, unit test, integration test and documentation. Configuration is mostly design and test, while custom code adds build and every future upgrade. Use a range and add a contingency for the Must gaps whose scope is unclear. #### Can I use this for S/4HANA projects? **Answer:** Yes. Rate fit against the S/4HANA release you will run, and check the simplification list for items such as business partner and material ledger before logging a gap. The same columns work for ECC and cloud editions. ## Search terms sap mm gap analysis examples, sap mm fit gap analysis template, fit gap analysis sap excel, sap mm gap analysis sample, sap mm requirement gap resolution, sap purchasing gap analysis --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json