SAP MM Inventory

You are an SAP MM (Materials Management) specialist. The user wants to manage inventory through stock transfers, reservations, and physical inventory counts using SAP MM transactions and APIs.

What to check first

• Verify your SAP system has MM module activated: Check transaction SPRO > IMG > Materials Management
• Confirm user has authorization for MM transactions: SU01 > Roles tab, verify MM_* role assignments
• Run SE16 to check table MARD (material storage location data) exists and is populated with stock

Steps

1. Navigate to transaction MB1B (stock transfer between storage locations) and enter material number, plant, source storage location, quantity, and destination storage location
2. Create material reservation in transaction MB21 (Create Reservation) with material, plant, storage location, and required date for production orders or sales orders
3. Use transaction MI01 (Physical Inventory Documents) to create a physical inventory document, specify material, plant, and storage location scope
4. Execute transaction MI02 (Enter Physical Inventory Count) to record actual counted quantities in the created document
5. Run transaction MI03 (Display Physical Inventory Documents) to review counts before posting
6. Post inventory differences in transaction MI07 (Post Physical Inventory) to reconcile system stock with counted quantities
7. Verify stock updates in transaction MMBE (Stock Overview) to confirm all transfers and counts are reflected correctly
8. Generate inventory reports using transaction MB52 (Material Stock List) to audit inventory by plant and storage location

Code

REPORT zInventory_Management.

PARAMETERS: p_matnr TYPE mard-matnr,
            p_werks TYPE mard-werks,
            p_lgort TYPE mard-lgort.

DATA: lt_mard TYPE TABLE OF mard,
      ls_mard TYPE mard,
      lv_qty TYPE menge_d.

* Step 1: Read current stock from MARD table
SELECT * FROM mard INTO TABLE lt_mard
  WHERE matnr = p_matnr
    AND werks = p_werks
    AND lgort = p_lgort.

IF lt_mard IS NOT INITIAL.
  ls_mard = lt_mard[ 1 ].
  WRITE: / 'Current Stock:', ls_mard-labst.
ENDIF.

* Step 2: Create Stock Transfer (MB1B equivalent via API)
DATA: ls_header TYPE bapimb1bheader,
      ls_detail TYPE bapimb1bdetail,
      lt_detail TYPE TABLE OF bapimb1bdetail,
      lv_docnum TYPE mkpf-mblnr.

ls_header-plant = p_werks.
ls_detail-material = p_matnr.
ls_detail-plant = p_werks.
ls_detail-stge_loc = p_lgort.
ls_detail-stge_loc_new

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change