SAP Inventory (Stock) Report
An inventory report joins SAP's storage-location stock to material valuation, so stock quantity and value sit on one Excel row by material, plant and storage location.
- PostNow ships this report out of the box – pick it, set filters, run, and it lands in Excel; no SE16, joins or ABAP.
- The data spans several tables. It joins MARD, MBEW, MAKT, MARA, T001W on MATNR + WERKS + LGORT and resolves the text lookups.
- The standard route is manual. Teams use MB52 for a single record, then SE16 or SQVI to stitch tables together in Excel.
- You get clean, labelled columns. MATNR, MAKTX, WERKS, LGORT, LABST, INSME and more, each with a plain-English heading.
- Refreshable, not a one-off dump. Rerun the report to pull the latest, with your own SAP authorizations enforced. Works on ECC and S/4HANA.
What the inventory report shows
A SAP inventory report answers a simple question that SAP makes surprisingly hard: give me every inventory record, with all the attributes that matter, in one place I can filter and share. On screen, SAP shows one record at a time and splits its attributes across several views. This report flattens all of that into a single Excel sheet, one row per record, with the codes turned into readable labels.
Because the output is a plain sheet, it becomes the starting point for the work people actually do with it: a data-quality review, a cleanup before a migration, a hand-off to an auditor, or a source for a pivot. The value is not just the extract, it is that the extract is complete and consistent every time you run it.
The SAP tables behind it
MARD holds stock quantities at storage-location level: unrestricted, quality-inspection and blocked stock, keyed by material, plant and storage location. MBEW holds the valuation: the price control, the moving-average or standard price and the total value, keyed by material and valuation area, usually the plant. The material description comes from MAKT, the basic material data such as material type from MARA, and the plant name from T001W. Joining stock to valuation on material and plant is what turns a bare quantity list into a valued inventory report.
The joins are the whole reason this is worth automating. Miss one and the report is subtly wrong; get the key fields slightly off and rows fan out or drop. Doing it once, correctly, and then reusing it is what turns a fragile spreadsheet exercise into a reliable report.
The columns you get
Every column below is a real SAP field, labelled in plain English, with the table it is read from. These are the fields most teams want on a inventory report; a tool like PostNow lets you add or remove columns without touching the underlying join.
| SAP field | What it is | Source |
|---|---|---|
| MATNR | Material | MARD |
| MAKTX | Description | MAKT |
| WERKS | Plant | MARD |
| LGORT | Storage location | MARD |
| LABST | Unrestricted stock | MARD |
| INSME | Quality inspection | MARD |
| SPEME | Blocked stock | MARD |
| VPRSV | Price control | MBEW |
| VERPR | Moving avg price | MBEW |
| STPRS | Standard price | MBEW |
| SALK3 | Total value | MBEW |
| MTART | Material type | MARA |
Building it yourself: MB52, SE16 or SQVI
MB52 gives a stock list on screen and MMBE a stock overview per material, both handy for a look but shaped for display, not for a flat valued extract across plants. SE16 on MARD gives you the quantities and SE16 on MBEW the values, which you then match in Excel on material and plant, and add MAKT for descriptions. Getting quantity and value onto the same row for a whole plant, refreshable, is the part that eats an afternoon. Anything custom, such as a valuation-class breakdown, means an ABAP report.
None of this is impossible; people do it every month. The problem is that it is manual, easy to get subtly wrong, and stale the moment it is saved. Each refresh means repeating the same exports and the same lookups, and any new column means another round with a developer. For a one-off you can push through it. For a report you run every period, the cost adds up. If you want the general landscape of options first, see our overview of SAP reporting tools and how to get SAP to Excel.
The out-of-the-box way: PostNow's inventory report
PostNow's Report Library already contains this exact report, pre-built. You do not assemble the joins or resolve the texts; that is done for you. You open Excel, log in to postnow.ai from the task pane, pick the inventory report, set your range filters, and run. The governed, joined data lands in the sheet, ready to filter, pivot or share, and you can refresh it whenever you need the latest.
Two things make this different from a SE16 dump. First, it is governed: PostNow enforces your own SAP authorizations, so you only ever see the data you are entitled to, and every row can be traced back to its source. Second, it is repeatable: the same report, the same columns, refreshable on demand, with no ABAP to write or maintain. That is the payoff of teaching the hard version first, then handing you the shortcut.
Filters and selection you'll want
A good inventory report is only as useful as the selection you can put on it. The filters most teams reach for are:
- Plant (WERKS)
- Storage location (LGORT)
- Material range (MATNR)
- Material type (MTART)
- Stock on hand (LABST > 0)
- Price control (VPRSV)
You set these once as your selection, then reuse or adjust them each run. Because the selection travels with the report, a monthly extract becomes a single refresh rather than a rebuild.
ECC vs S/4HANA
MARD and MBEW persist in S/4HANA. With the material ledger mandatory, valuation may carry additional currencies and actual-costing values, but the stock and valuation tables read the same way, and PostNow pulls them through standard interfaces on both ECC and S/4HANA.
The practical takeaway is that a report built on the tables and read through standard interfaces survives a migration far better than one wired to a specific screen or a custom program. When you eventually move from ECC to S/4HANA, a table-based inventory report keeps working, which is one less thing to rebuild in an already large project.
Frequently asked questions
How do I get a inventory report out of SAP into Excel?
You can export the underlying tables with SE16 and stitch them together in Excel, build a query in SQVI, or ask a developer for an ABAP report. The quickest governed route is a tool that already has the report built: in PostNow you log in to postnow.ai from the Excel task pane, pick the inventory report from the Report Library, set your filters and run, and the joined data lands in the sheet.
Which SAP tables hold inventory data?
The data is spread across several tables that have to be joined on their key fields: MARD, MBEW, MAKT, MARA, T001W. The report links them on MATNR + WERKS + LGORT and resolves the text tables so the output reads in plain language.
Is there a standard SAP report or transaction for inventory?
There are standard transactions (MB52 and others), but they are built for on-screen display or for a fixed layout, not for a clean, refreshable Excel extract with exactly the columns you want. That is why most teams fall back to SE16 exports or a custom report.
How do I export inventory data to Excel without ABAP?
Use a tool whose SAP connection is set up once and then reads through standard interfaces, so no ABAP is needed for day-to-day reporting. PostNow reads the inventory tables, performs the joins and text lookups, and writes the result straight into Excel, refreshable on demand, with your own SAP authorizations enforced.
Can I refresh or schedule the report?
Yes. Because the report keeps its connection and selection, you can refresh it to pull the latest data at any time rather than rebuilding the extract. This is the main advantage over a one-off SE16 dump, which is stale the moment it is saved.
Does it work in S/4HANA?
MARD and MBEW persist in S/4HANA. With the material ledger mandatory, valuation may carry additional currencies and actual-costing values, but the stock and valuation tables read the same way, and PostNow pulls them through standard interfaces on both ECC and S/4HANA.
How do I get stock quantity and value in one SAP report?
Quantities live in MARD at storage-location level and values live in MBEW at valuation-area level. A report that joins them on material and plant puts unrestricted, blocked and inspection stock next to the moving-average or standard price and total value, so quantity and value sit on one row.
Can I report inventory across several plants at once?
Yes. MARD holds one row per material, plant and storage location, so a report can span any set of plants. Filter by plant, storage location and material type to get exactly the stock you want to review or reconcile.