SAPFree worksheetPDF, Excel, Word exportSAP

SAP MM Gap Analysis Examples and Fit-Gap Template

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.

Download:
Req IDMM areaBusiness requirementFit ratingResolutionPriorityEffort (days)Day rateCost
$1,800
$3,600
$5,400
$13,200
$16,500
$2,700
$900
$2,700
Total effort (days)
46
Total estimated cost
$46,800
Requirements
8
Average effort per requirement
5.75
Average cost per requirement
$5,850

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).

Review your fit-gap list

Optional: send your gap list and we will mark which items could be solved by a read-only AI layer instead of custom ABAP.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

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.

  • 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

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

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

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.

Frequently Asked Questions

What is a fit-gap analysis in SAP MM?

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?

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?

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?

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.

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.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP