# SAP Interface Inventory Register Worksheet

> Source: https://netray.co/tools/sap-interface-inventory-register-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable register of every interface touching SAP, with technology, owner, frequency and business criticality, ready to export to Excel.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- SAP integration architect
- SAP application manager
- Interface developer

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Interface ID

**Key:** id

**Type:** text

#### Interface name

**Key:** name

**Type:** text

#### Other system

**Key:** peer

**Type:** text

#### Technology

**Key:** tech

**Type:** select

**Options:**

- IDoc
- RFC/BAPI
- OData
- SOAP
- REST API
- File
- SAP CPI
- SAP PO

#### Direction

**Key:** direction

**Type:** select

**Options:**

- Inbound
- Outbound
- Bidirectional

#### Frequency

**Key:** freq

**Type:** select

**Options:**

- Real time
- Hourly
- Daily
- Weekly
- On demand

#### Criticality (1-5)

**Key:** crit

**Type:** number

#### Owner

**Key:** owner

**Type:** text

#### Last reviewed

**Key:** reviewed

**Type:** date

**Rows:**

#### Customer PO to sales order

**Id:** IF-001

**Peer:** EDI VAN

**Tech:** IDoc

**Direction:** Inbound

**Freq:** Real time

**Crit:** 5

**Owner:** Order to cash team

**Reviewed:** 2026-09-15

#### Advance ship notice

**Id:** IF-002

**Peer:** EDI VAN

**Tech:** IDoc

**Direction:** Outbound

**Freq:** Real time

**Crit:** 4

**Owner:** Logistics IT

**Reviewed:** 2026-09-15

#### Material master to MES

**Id:** IF-003

**Peer:** Shop floor MES

**Tech:** SAP CPI

**Direction:** Outbound

**Freq:** Hourly

**Crit:** 4

**Owner:** Plant IT

**Reviewed:** 2026-08-02

#### Production confirmations

**Id:** IF-004

**Peer:** Shop floor MES

**Tech:** RFC/BAPI

**Direction:** Inbound

**Freq:** Real time

**Crit:** 5

**Owner:** Plant IT

**Reviewed:** 2026-08-02

#### Bank statements

**Id:** IF-005

**Peer:** Bank host

**Tech:** File

**Direction:** Inbound

**Freq:** Daily

**Crit:** 3

**Owner:** Treasury

**Reviewed:** 2026-07-20

#### Supplier portal PO view

**Id:** IF-006

**Peer:** Supplier portal

**Tech:** OData

**Direction:** Outbound

**Freq:** On demand

**Crit:** 2

**Owner:** Procurement IT

**Reviewed:** 2026-06-11

**Totals:**

#### Interfaces

**Key:** id

**Agg:** count

#### Average criticality

**Key:** crit

**Agg:** avg

**Format:** decimal

#### Highest criticality

**Key:** crit

**Agg:** max

**Format:** integer

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the register

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

- Confirm which interfaces actually ran in the last 90 days
- Flag interfaces using custom function modules
- Link each row to its test case

**Cta:** 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.

**Faq:**

#### How do I find all IDoc interfaces in SAP?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

sap interface inventory, sap interface list excel, interface register template, sap integration landscape inventory, sap interface catalog, sap idoc interface list, interface documentation template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
