SAP System Landscape Inventory Worksheet
Many SAP teams cannot answer the simple question of which systems they run, who owns them and when they were last patched. This worksheet is the single list to start from.
| SID | Description | Tier | Product | Release or stack | Database | Host or cloud instance | Named users | System owner | Last kernel or SPS update | Backup tested | |
|---|---|---|---|---|---|---|---|---|---|---|---|
Add one row per system and client you want tracked. Use the release field for your own convention, for example product version plus feature pack or support package level. Check values against your system status screen (System, Status).
Keep your SAP landscape inventory current
Optional: we can discuss pulling system and user counts automatically into a living inventory.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per SAP system. The SID, product, release and database can be read from the System Status screen of each system. Host, owner and backup status come from your infrastructure and operations records. Export to Excel and keep the file under change control, or paste it into your CMDB. Review it quarterly, and after every system copy, upgrade or decommission.
- Include satellite systems such as Gateway, GRC and Solution Manager
- List non-production systems, since they often hold copied production data
- Record an owner by name, not only by team
- Mark whether the last backup restore was actually tested
Why an inventory matters
Patching, access reviews, licence audits and incident response all start with a list of systems. Without it, a sandbox that was copied from production two years ago remains unpatched and holds real customer data. Security notes, kernel updates and support packages must be tracked per system. The inventory is also the base for scoping an access review or a migration.
Reading the summary
Named users per system show where access reviews cost the most effort and where licence exposure sits. A production system with a small user count and no tested backup is a bigger risk than a large development system. Sort the exported sheet by last update date to find the systems furthest behind.
Common mistakes
Common gaps are leaving out client-level details when clients have different purposes, missing technical systems such as the web dispatcher, and not recording the owner. Another is letting the sheet go stale after a project ends.
Frequently Asked Questions
Do I need one row per client?
If clients serve different purposes or hold different data, yes. Add the client number to the description. For systems with a single active client one row is enough.
Where do I find the release information?
In the SAP GUI under System, Status, which shows product version, kernel and database. Solution Manager can also report this centrally if it is set up.
How often should the inventory be reviewed?
Quarterly is a reasonable rhythm, plus after any upgrade, copy or retirement. Treat it as a controlled document if auditors request it.
Can I use it for cloud-hosted SAP?
Yes. Put the cloud instance name or hosting provider reference in the host column and add your hosting contact as the owner of the infrastructure side.
If you need your ERP landscape documented and queryable in one place, Netray can connect read-only to your systems and help keep the inventory current.
Related Tools
SAP Profile Parameter Change Log Worksheet
An editable log of SAP profile parameter changes with old and new values, reason, approver and restart requirement.
SAPSAP Go-Live Security Readiness Checklist
A checklist of security and Basis items to confirm before an SAP system or release goes live, with critical items flagged.
SAPSAP SoD Mitigating Control Register Worksheet
An editable register of accepted SoD conflicts and the compensating controls behind them, with risk score and review dates. Exports to Excel.
SAPSAP User Access Review Sample Size Calculator
Work out a defensible sample size for testing user access, role assignments or change records, using attribute sampling.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)