User Documentation
Auto Light Dark
Auto Light Dark

Catalog (End-to-End)

The Catalog lists the End-to-End integrations in your landscape. Each integration represents an ordered chain of interfaces that carries a business process from its initial sender to its final receiver.

Purpose: Review the integrations proposed by the cockpit, confirm the ones that actually exist and arrange their interfaces in the order in which they run.

Navigate to Inventory → End-to-End → Catalog to open the list.


Catalog

image-20261030-145048.png
The End-to-End catalog: the icon in front of each name separates confirmed integrations from proposals.

The list displays Name / Description, Sender, Receiver, Tags and Interfaces. The Interfaces column shows the number of interfaces in the chain, which may differ from the number of steps because parallel branches are counted separately. The cell is empty if an integration does not contain any interfaces yet. Use Configure columns to add columns or hide existing ones.

The list is sorted by name, so proposals and confirmed integrations appear alongside each other. Use the Proposals switch to display only proposals.


Proposals and Confirmed Integrations

Every integration in the list is either a proposal or a confirmed integration. The small icon in front of the name tells them apart:


image-20261030-150046.png

Circle with a check mark
A proposal. The cockpit created it automatically. Hovering over the icon shows Automatically generated proposal.

image-20261030-145934.png

›
A confirmed integration. Someone created it with Add, or confirmed a proposal with Save.

The cockpit creates proposals when the E2E task of a data source runs:

  • From the message logs — For SAP Integration Suite (Cloud Integration and Edge Integration Cell), interfaces that the same messages run through become one proposal.

  • From an ID — Interfaces with the same value in the Interface ID property become one proposal. The property is selected under Settings → End-to-End → Generation.

  • For single interfaces — Every interface that is not yet part of any integration gets a proposal containing only that interface.

The cockpit then completes each proposal with the interfaces that run before and after it.

A proposal is not final. Each time the E2E task runs, the cockpit can add interfaces to it again and change its numbering — even after Save as draft. To keep your changes, click Save. This turns the proposal into a confirmed integration, which the cockpit never changes automatically.


Toolbar

image-20261030-145533.png
The catalog toolbar: switches to filter the list on the left, additional actions on the right.

Control

What it does

Proposals

Displays only integrations generated by the cockpit that have not yet been confirmed.

Recently Added

Displays only integrations added within the period configured under Settings → Dashboard on the Inventory tab.

Mass maintenance for properties and tags

Switches the list to selection mode. Select rows to apply mass maintenance or delete them.

Add

Create End-to-End Integration — prompts you to enter a name and opens the new integration.

Search

Searches by name and description.

Filter

Opens the filter panel (see below).

Configure columns

Adds columns or hides the standard ones.

Download

Downloads the list as CSV or Excel.

Reload

Reloads the list.

Mass maintenance, Add and the delete action are only available to users with write permission.

The filter panel offers thirteen criteria:

What you filter on

Criteria

The integration itself

Sender / Receiver, Data Source, Environment, Tag, Property, Object

Values derived from its interfaces

Adapter, Authentication, Robustness, Complexity, Frequency, Timing, Last Traffic

The second group is particularly useful for questions such as which integrations still run without authentication or which ones have not carried a message in months.


End-to-End Detail View

image-20261030-153119.png
The detail view: the Interfaces card holds the chain, the cards above it describe the integration as a whole.

Click an integration name to open its detail view. The page consists of the following cards:

Card

Content

Basic Data

Name, sender and receiver. An integration can have multiple receivers. The first receiver is the main receiver. Additional receivers are listed below it.

Reporting

Values derived by the cockpit from the interfaces in the chain, such as adapter, authentication and average robustness.

Sender / Receiver System Properties

Read-only properties of the sender and all receivers. Only displayed if the respective systems have properties.

Tags, Properties

Custom classifications of the integration.

Interfaces

The interface chain itself — see Step Order below.

Objects

Business objects associated with the interfaces, as well as objects assigned directly to the integration.

Description

Free-text description of the integration.

Visualization

A diagram of the chain — see Visualization below.

The page header provides the following actions for the entire integration:

  • To-do — Opens the configuration checklist (see below).

  • Move to Prod — Opens Move to Production. Only available while the integration is not yet in production.

  • Find E2E predecessors & successors — Extends the integration with interfaces that call the integration's interfaces or are called by them, and renumbers the chain.

  • Copy — Creates a copy of the integration.

  • Show Changes — Displays the change history.

Move to Prod, Find E2E predecessors & successors and Copy are only available to users with write permission.

Find E2E predecessors & successors places the interfaces it finds at the corresponding positions in the chain. Interfaces found at the same position become parallel branches within one step, for example 3.1 and 3.2. Cloud Integration resources are also added if they are selected under Settings → End-to-End → Expand.


Basic Data

image-20261030-153710.png
Basic Data with a main and an additional receiver: their order decides which branch ends where.

Basic Data holds the name, the sender and the receivers of the integration. The first row under Receiver represents the main receiver. Each subsequent row represents an additional receiver. Use + to add a row and − to remove one. Removing the main receiver promotes the next receiver to the main position. Empty rows and duplicate receivers are removed when you click Save.

The order of the receivers matters: the visualization connects the interfaces of the last step to the receivers in exactly this order.

If an integration has no sender, the sender of its first interface is proposed. If it has no receiver, the receivers of the interfaces in the last step are proposed. This only works for interfaces whose sender and receiver are linked to a system, not just given as a name. The first one becomes the main receiver, and the others are added as additional receivers. These proposals are stored when you click Save.


Reporting

image-20261030-153741.png
The Reporting card: the adapters and authentication types of all interfaces, and their average robustness.

The Reporting card summarizes the interfaces in the chain. It displays all Adapter and Authentication values used by the interfaces, as well as their average robustness score under Robustness (Avg).

A Robustness (Avg) value of 0.00 means that none of the interfaces has a robustness score yet. It does not mean that the integration is poorly built.


Configuration Checklist

image-20261030-153238.png
The configuration checklist opened from the To-do badge, listing the checks that are still open.

The To-do badge in the header provides a quick overview of the outstanding configuration tasks. Its color indicates the status:

Color

Meaning

Green

All checks have passed.

Yellow

Some checks have passed.

Red

No checks have passed.

Gray

No checks are enabled.

Opening the badge displays the individual checks and a counter showing done / total:

  • Sender and Receiver — Is a system assigned to both ends of the integration?

  • Properties — Have all property types marked as required been filled in? If no required types are configured, assigning any property is sufficient.

  • Tags — The same check applies to tags.

  • Objects — Does the integration contain at least one business object?

  • EAM — Is the integration linked to an entry in your enterprise architecture tool?

If required property types or tags are configured, the checklist lists each of them below the check, and the dot in front of each name shows whether it is filled. The check then reads All set, Partial or Incomplete.

Which checks are displayed, and which properties and tags are considered required, is configured under Settings → To-do. Checks that are not required can be disabled there and are then excluded from the integration's checklist.


Step Order

image-20261030-153338.png
Editing the step number: step 1 runs alone, step 2 splits into two parallel branches.

The # column defines the position of each interface in the chain and supports decimal numbers. Click a value in this column to change the order. Both a period and a comma are accepted as decimal separators. Any entry that is not a number is discarded when you leave the field.

Each whole number represents one step. Interfaces that run one after another are numbered 1, 2, 3. Interfaces that run in parallel within the same step share the same whole number and are distinguished by their decimal values. For example, 2.1 and 2.2 represent two parallel branches of step 2.

This numbering is reflected in the End-to-End Visualization, which displays one column per whole number and sorts the branches within each column by their decimal values.

The following rules apply when saving:

  • A step containing a single interface retains its whole number. For example, 3 remains 3.

  • Two interfaces with the same whole number retain their numbering. For example, 3 and 3 are valid and indicate that both interfaces run in parallel.

  • If one of the interfaces has a decimal value, the entire step is renumbered into consecutive slots. For example, entering 3 and 3.2 results in 3.1 and 3.2.

  • If a step contains ten or more parallel interfaces, the numbering automatically switches to finer decimal increments — 0.01, then 0.001 — to prevent the sequence from overlapping with the next whole number. All interfaces in that step are displayed with the same number of decimal places, for example, 16.01 to 16.10.

A newly added interface is numbered based on the total number of interfaces in the chain, not the highest existing step number. For example, in a chain numbered 1, 2, 5, 7 and 8, the sixth interface is assigned step 6. This places it in the middle of the chain rather than at the end. Check the # column and adjust the numbering before saving.


Adding and Removing Interfaces

image-20261030-153432.png
The Add Interfaces dialog: the colored dot shows how recently each interface was changed.

Click Add in the Interfaces card to open the interface list. Two switches help narrow down the results:

Switch

What it does

No End-to-End

Displays only interfaces that do not yet belong to any integration.

Recently Added

Displays only interfaces added within the period configured under Settings → Dashboard on the Inventory tab.

The colored dot in front of each name indicates how recently the interface was updated: green if it was changed within the last two days, yellow if it was changed within the last week, and red if the last change was more than a week ago. A red dot can also indicate that the raw interface data is no longer available in its source. The tooltip on the dot explains which applies.

Select the interfaces you want to add and confirm by clicking Add. The selected interfaces are appended to the chain.

Remove removes the selected interfaces from the chain. How the numbering changes depends on which interfaces you remove:

  • Removing a parallel branch: The numbering within that step is adjusted to close the gap. For example, removing 2.2 from 2.1, 2.2 and 2.3 leaves 2.1 and 2.2.

  • Removing an entire step: The step number remains unused. For example, removing step 2 from steps 1, 2 and 3 leaves steps 1 and 3. Adjust the numbering manually in the # column if you want consecutive step numbers.

In the Receiver column, +N more indicates that an interface has additional receivers. Click it to display them.

Below the Interfaces card, an accordion lists the interfaces and End-to-End integrations that share an ID property value with the current integration. Each entry represents one ID. Use Add interface to dataflow to append one of these interfaces to the chain. This also works if the interface is already part of the chain, as the same interface can be used in multiple steps.


Visualization

image-20261030-153526.png
The visualization at the bottom of the detail view. Step 2 splits into the parallel branches 2.1 and 2.2, and each branch ends at its own receiver.

The visualization at the bottom of the detail view shows the selected integration, starting with its sender. It uses the same elements as Reporting → Landscape → Visualization → by System → End-to-End: the sender on the left, the integration displayed as a frame with one column per step, and the receivers on the right. The diagram reflects the saved state of the integration and is only drawn once the integration has both a sender and a receiver.

The connections between the elements follow the # column:

  • The sender is connected to every interface in the first step.

  • If two consecutive steps are both divided into branches, the branches are connected individually: 2.1 to 3.1 and 2.2 to 3.2.

  • If at least one of two consecutive steps is not divided into branches, every interface in one step is connected to every interface in the other.

  • The interfaces in the last step are connected to the receivers in the order defined under Basic Data: the first interface connects to the main receiver, the second to the first additional receiver, and so on. If there are fewer interfaces than receivers, an interface connects to multiple receivers. If there are more interfaces than receivers, multiple interfaces connect to the same receiver.

Cloud Integration resources, such as value mappings, credentials and destinations, are not displayed as separate steps. Instead, they are shown below the interface to which they belong.

To display two branches that each end at their own receiver, number the interfaces in the last step as x.1 and x.2, and list the receivers under Basic Data in the same order.


Saving

image-20261030-153626.png
Save as draft is only offered while the integration is still a proposal.

Button

What it does

Save

Saves the integration and confirms a proposal, changing it from a suggestion to a confirmed integration.

Save as draft

Only available for proposals. Saves your changes without confirming the proposal.

Cancel

Returns to the previous view without saving changes.

Delete

Deletes the integration. The confirmation message warns you if the integration shares an ID with another interface or integration.

Both save actions sort the chain by step number. The order displayed after saving is therefore the same as the order used in the visualization.

Users without write permission only see the Cancel button.



Last Updated: October 30, 2026