User Documentation
Auto Light Dark
Auto Light Dark

ABAP (Inventory)

The ABAP section lists the integration objects read from a connected SAP ABAP system: the interfaces the system exposes or calls, and the configuration around them.

Purpose: See which integration technologies an ABAP system actually uses, and open the interface behind each object. The catalogs also help you identify which services a communication user can reach, which RFC destinations are not referenced and which collected objects generated an interface.

Navigate to Inventory → by Data Source → SAP → ABAP → <data source> to open the catalogs of one system.


Working with the Catalogs

image-20260929-095246.png
The catalogs of one ABAP system, listed under its entry in the sidebar

Three data source types can appear under ABAP, each with its own catalogs:

Data source

Catalogs

ABAP system

The catalogs described below, from IDocs to ICF Services

ABAP BTP

Communication Arrangements, Communication Systems

ASAPIO

Interfaces, Connections

Which catalogs an ABAP system shows depends on what was collected, so two systems can offer a different set.

Catalog toolbars provide:

Control

What it does

Search

Searches the main columns. Offered in every catalog except the two ASAPIO ones

Filter

Narrows the list by the values of selected columns. The panel names the fields it offers

Reload

Reads the catalog again

RFC Destinations has one switch of its own, No Usage, described in that section.

The Interface column opens the interface that was generated from that object in Inventory → Interfaces, with its type, sender and receiver, tags, properties, End-to-End integration and description. It is only shown where such an interface exists.

Where a catalog has a detail view, the first column opens it, and its header links to the generated interface. Empty cards are left out, so two entries of the same catalog can look different.


ABAP System Catalogs

IDocs

image-20260929-113505.png
IDoc catalog: one row per partner profile, with the Interface column on the right.

Intermediate Documents exchanged with partner systems through ALE and EDI.

What you see:

Column

Content

Partner / Type, Function

Partner number, partner type and partner function

Message / Code, Function

Message type with message code and function

Direction / Mode, Pkg. Size Code

Inbound or outbound, processing mode and package size

IDoc Type / Extension

Basic type and extension

Receiver / Port

Receiving system and port

Interface

Opens the generated interface

Click the Receiver to open the RFC destination behind the port.


OData APIs (V2)

OData V2 services registered in the SAP Gateway.

image-20260929-113540.png

What you see: Name / Description, Version, Changed on / by, Interface

image-20260929-113602.png

Detail view: Basic Data with technical name, description and version · Administration with the last change · a third card with the service Address.


OData APIs (V4)

OData V4 services from the SAP Gateway catalog, which organizes them in service groups.

image-20260929-113729.png

What you see: Name / Description, Version, Alias, Interface

image-20260929-113759.png
Detail view of an OData V4 service with its Service Groups.

Detail view: Basic Data with name, description and version · Administration with repository, service alias, system alias and system description · a third card with the service Address · Service Groups with the groups the service belongs to, if it has any.


SOAP Services

Web services configured in the SOA Manager.

image-20260929-113849.png

What you see: Interface / Type, State, Changed on / by, Interface

image-20260929-113910.png

Detail view: Basic Data with type, state and default logical port · Administration with the creation and change history · Properties with the settings of the service binding, each with name, type, subject and value.

The binding property named Destination is what ties a SOAP service to an RFC destination — see RFC Destinations below.


SOAP XI

Interfaces of the XI runtime, used for communication with SAP PI, PO or Cloud Integration.

image-20260929-113938.png

What you see: Interface / Namespace, Sender / Party, Receiver / Party, Direction, QoS, Interface

The QoS column shows the quality of service of the message, for example EO for exactly once.


RFC Destinations

Remote Function Call endpoints the system uses to reach other systems.

image-20260929-114001.png
RFC Destinations catalog with the No Usage toggle.

What you see: Name, Type, Changed on / by, Interface

Switch on No Usage in the toolbar to list only destinations that are not referenced by an IDoc partner profile, an Integration Engine interface or a SOAP service binding. These are candidates for cleanup.

image-20260929-114124.png
Detail view of an RFC destination with its options and the objects that use it.

Detail view: Basic Data with the type, and for qRFC destinations also state, maximum connections, timeout and host · Administration with the creation and change history · Options with the configured key/value options · up to three Where-Used cards: the IDoc partner profiles, the Integration Engine interfaces and the SOAP services that use the destination. Each entry opens the matching catalog with the object already searched for.

A Where-Used card shows the result of the last analysis. If none has run yet, use Reload inside the card, the result is then kept for the next visit. A card that stays empty after Reload means that no IDoc partner profile, Integration Engine interface, or SOAP service binding refers to the destination - the same result shown by No Usage for the complete list.


Communication Users

The users that inbound communication runs under.

image-20260929-114800.png
Detail view of a communication user with its Where-Used card

What you see: User ID, Type, Class

image-20260929-114739.png

Detail view: Basic Data with user ID, type and class · Administration with the lock state and the last logon · Where-Used with one row per service the user reaches, showing the role, the service, its type, the authorization resource and the interface behind it.

The card lists the roles assigned to the user and, where the system supplies it, the service behind each role. Role, service and interface each open the corresponding entry. Like on RFC Destinations, Reload inside the card runs the analysis. A user without roles keeps an empty card - that is the result, not a failed run.


Roles

The authorization roles of the system.

image-20260929-114649.png

What you see: Role, Valid from, Changed on

image-20260929-114703.png
Detail view of a role with its services and assigned users.

Detail view: Basic Data with the role · Administration with valid from, valid to and the last change · Services with the OData and SOAP services the role covers · Assigned Users. Each service opens its catalog entry, each user opens the communication user.

Roles and Communication Users are collected together and therefore always appear as a pair. The catalog lists the roles that are assigned to a communication user, which is why it is usually much shorter than the role list in the system itself.


File Accesses

File operations found in ABAP programs, the basis for file interfaces.

image-20260929-132807.png
File Accesses catalog with the program, its activity and the generated interface.

What you see: Program Name, Activity, App Name, App Type, Interface

Activity is the operation the program performs on the file: Read, Write, Execute, Import, Export, Backup or Restore. App Type says where the access comes from — a transaction or an RFC function module. Both read Unknown when the trace does not resolve them.


Configuration in the ABAP System

To read the access to files via ABAP-statement OPEN DATASET, the following configuration is required by activating the aggregated authorization trace (transaction code: STUSOBTRACE).

  • Set the filter Authorization Object S_DATASET

  • Set the profile parameter auth/authorization_trace = Fwhile the system is running via transaction code RZ11

image-20251216-144528.png
Transaction STUSOBTRACE

Caution: Activating the authorization trace without filters has a negative effect on performance!

Collected File Accesses are generating Interfaces during the run of the INVENTORY job.


File Paths

The logical file paths of the system and the physical paths behind them.

image-20260929-115621.png

What you see: Logical Path / Description, Physical Path, Type

The physical path can contain placeholders and is resolved per operating system. The Type column identifies the operating system.


Content Repositories

The content repositories the system stores documents in.

image-20260929-114826.png

What you see: Repository ID, Type, Subtype, Created (User / Time), Changed (User / Time), HTTP Details

The HTTP Details column counts the configurations of that repository and opens them: repository ID, version, server, HTTP port, HTTPS port and type / subtype.

image-20260929-114908.png

That view is not part of the navigation and is only reached from here, its repository ID leads back to the repository.


Integration Engine

The configuration of the local Integration Engine.

image-20260929-114935.png

What you see: Name / Description, Service / Party, Action / Namespace, Destination

Click the Destination to open the RFC destination behind it.


Database Connections

The database connections maintained in the system.

image-20260929-115000.png

What you see: Connection Name, Database Type, User Name, Connection Information, Permanent, Connection Limit


ICF Services

The services published in the Internet Communication Framework, the basis for HTTP and REST calls.

What you see: Name, Interface


ABAP BTP Catalogs

Communication Arrangements

Available on an ABAP BTP data source. The arrangements that connect a communication scenario with a remote system. Their inbound and outbound services become the interfaces of the system.

image-20260929-115035.png

What you see: Name, Communication Scenario, System

image-20260929-115118.png
A communication arrangement with its inbound and outbound services.

Detail view: Basic Data with communication scenario and communication system · Administration with the creation and change history · Description, where one is maintained · Properties with the channel settings such as protocol and topic space · Inbound Services with number, service, type and the interface behind it · Outbound Services with number, service, status, URL path / port, active flag and the interface behind it.

The System column and the communication system in the detail view open the communication system.


Communication Systems

Available on an ABAP BTP data source. The remote systems the arrangements point to.

image-20260929-115157.png

What you see: Name, System ID, Host Name, TCP Port

image-20260929-115214.png

Detail view: Basic Data with name, system ID, host name, the host name used for the UI, TCP port and the logical and business system ID · Administration with the creation and change history, the Cloud Connector and its location ID · Description, where one is maintained · Communication Arrangements that use this system, each opening the arrangement.


ASAPIO Catalogs

Interfaces (ASAPIO)

Available on an ASAPIO data source. The outbound interfaces configured in the add-on.

image-20260929-115246.png

What you see: ID, Connection ID, Direction, Active

image-20260929-115325.png
Detail view of an ASAPIO interface, the connection ID opens the connection.

Detail view: Basic Data with ID, load type, data layer, message type, active flag and direction · Connection with the connection ID, ASAPIO payload and payload version, last run, table view and events · Header Attributes with the name and value of each attribute.

The Connection ID opens the connection the interface runs through.


Connections (ASAPIO)

Available on an ASAPIO data source. The connections the ASAPIO add-on uses to reach a broker or target system.

image-20260929-115402.png

What you see: ID, Type, RFC Destination

image-20260929-115439.png
Detail view of an ASAPIO connection with the interfaces that use it.

Detail view: Basic Data with ID, type and RFC destination · Connection with SSL, hostname and port · Interfaces with the name and direction of every interface that uses this connection.

Two links lead out of this catalog:

  • The Type opens the connector behind the connection — the add-on component for that technology, with its ID, whether it is active and installed, and all connections that run through it. The connector has no entry of its own in the navigation and is only reached from here.

  • The RFC Destination in the detail view opens that destination in the RFC Destinations catalog of the ABAP system, provided the ASAPIO data source is linked to that system and the destination was collected there.



Last Updated: September 29, 2026