## 5.6.1.2 Add an Integration Dependency Using a Simplified Business Eventing Template
## Prerequisites
- An SAP Cloud system is registered in the Systems page in SAP BTP cockpit and has a catalog of events that it plans to publish. Refer to the product documentation for the publishing system for more details. For example, an SAP SuccessFactors system can be configured to publish events. See SAP Cloud Application Event Hub Service Guide: Integration Use Cases.
- The SAP system you plan to use as the subscriber is registered in the Systems page. If you want to use SAP Integration Suite integration flows to consume events from SAP Cloud Application Event Hub, then the tenant with the integration flow must be registered in the Systems page. See Integration Example using SAP Integration Suite.
- Your subscribing system is listed in the Systems page of your global account in SAP BTP. For example, you have a system of type SAP Integration Suite listed in the Systems page. It appears as auto-discovered.
## Context
You can subscribe to events with extension applications. For example, you use SAP SuccessFactors to publish events and an Integration Suite tenant to consume them. The SAP SuccessFactors system is publishing these events and you add the event types that you want this system to receive using the Simplified Business Eventing Template of the integration dependencies. Integration dependencies are exposed as available event subscriptions in SAP Cloud Application Event Hub. The Simplified Business Eventing Template helps you write simplified integration dependencies specifying only event-specific information.
## Procedure
1. In the cockpit, navigate to your global account, and then choose System Landscape Systems .
2. On the Systems page, select a system of type Integration Suite to which you want to add an integration dependency and open its system details.
3. In the Integration Dependencies tab, choose Add .
4. Select Simplified Business Eventing Template to identify the system that is publishing events and add the event types that you want to receive. Integration dependencies are exposed as available event subscriptions in SAP Cloud Application Event Hub.
5. Define a name and a description for the new integration dependency.
##  Note
The version is assigned automatically when adding a new integration dependency. If you add a new integration dependency using the same name as an existing integration dependency, the version of the new integration dependency will be automatically increased.
6. In the Publishing System Namespace field, provide the system namespace of the system that is publishing events. You can find the system namespace in the System Details of the system.
The system namespace has to follow these rules:
- Use only lowercase ASCII letters (a-z) and digits (0-9)
- Include at least one character
- Use the dot (.) only to separate fragments
- Include only two fragments separated by a dot Example: sap.foo
7. In the Event Type field, list the event types published by the system that you want to make available to your subscribing system.
You can write or paste the event types separated by comma, semicolon or new row. Preferably, each event type should be on a new row. You have a counter giving the number of event types that are already filled in.
8. Choose Next Step .
9. Check if all the event types are configured properly and choose Add .
##  Note
Once you add an integration dependency to a system, you can no longer edit it and add or delete event types. You can only delete the integration dependency itself.