SAP Interface Inventory Register Worksheet
Most SAP landscapes accumulate interfaces faster than anyone documents them. This worksheet gives you a simple register you can fill row by row, sort and export, so upgrades, outages and migrations start from a known list.
| Interface ID | Interface name | Other system | Technology | Direction | Frequency | Criticality (1-5) | Owner | Last reviewed | |
|---|---|---|---|---|---|---|---|---|---|
Add one row per interface and message type. Sort by criticality before reviews and revisit anything not reviewed in the last 12 months. Export to Excel to share with auditors or for a middleware migration plan.
Interface landscape review
Share your register and get a short review of monitoring gaps and retirement candidates.
Optional. The tool and every export work without this. No spam.
How to use the register
Start with what you can verify. Pull IDoc partner profiles from WE20, RFC destinations from SM59, active OData services from the Gateway service maintenance and scheduled jobs from SM37, then add one row per interface. Use a stable interface ID so tickets and monitoring alerts can reference it. Assign an owner who can answer when something breaks at night, not a distribution list. Criticality is a business judgment: 5 means orders or production stop within hours, 1 means a report is late. Export the sheet after each review cycle and keep the file with your change records.
- One row per interface and message type
- Name a person or team as owner
- Rate criticality by business impact, not by volume
- Record the last review date
Why technology and frequency matter
Technology tells you how to monitor and recover. IDoc interfaces are watched in WE02 and BD87, RFC and qRFC problems appear in SM58 and SMQ1 or SMQ2, OData issues show up in the Gateway error log, and CPI flows have their own message monitor. Frequency tells you how quickly a failure becomes visible. A daily file load can fail silently for a day, while a real time order interface shows backlog within minutes. Having both on one line lets you decide which interfaces deserve proactive alerts.
Using the register for upgrades and migrations
When you plan an S/4HANA conversion or move middleware, the register becomes the scope list. Filter by technology to find interfaces that depend on retired objects or custom ABAP, and by criticality to schedule regression tests. Interfaces with no owner or no review in a year are candidates for retirement. A common finding is that a handful of interfaces carry most of the business risk while many others have not run in months. Document that finding here instead of in someone's memory.
- Confirm which interfaces actually ran in the last 90 days
- Flag interfaces using custom function modules
- Link each row to its test case
Frequently Asked Questions
How do I find all IDoc interfaces in SAP?
Start with WE20 for partner profiles and WE02 or table EDIDC for actual traffic by message type and partner. Traffic data is more reliable than configuration because it shows what really runs, not what was once set up.
How often should the register be reviewed?
At least once a year and before any upgrade, migration or major middleware change. Critical interfaces with a score of 4 or 5 deserve a lighter review each quarter.
Should I include non SAP to non SAP flows?
Only if they pass through your SAP landscape or middleware. The register is most useful when its boundary is clear: everything that reads from or writes to your SAP systems.
Can I import an existing Excel list?
You can retype or paste rows into the editable table, then export the result. Keep your column names consistent so the file can be loaded into a CMDB or ticketing tool later.
If you want the register generated from your system data instead of typed by hand, Netray can build a read-only extraction for IDoc traffic and RFC destinations.
Related Tools
SAP Integration Test Case Matrix Worksheet
An editable test matrix for SAP interface testing, with scenario, expected result, pass flag and defect count rolled up to a pass rate.
SAPSAP Interface Volume and Storage Sizing Worksheet
An editable worksheet that turns messages per day, average size and retention into daily megabytes, peak hourly load and total storage.
SAPSAP IDoc Partner Profile (WE20) Setup Template
A fill-in setup sheet for WE20 partner profiles, WE21 ports and the inbound and outbound parameters behind each IDoc partner.
SAPSAP Integration Technical Specification Template
A technical specification document for one SAP interface: purpose, data flow, technology, error handling, security and monitoring.