## 4.2.13.8.7.2.1  Configuring Inbound Event Topic Bindings
## Prerequisites
- You have established a connection through the configuration of the communication arrangement in the previous steps. For more information, refer to Communication Arrangements [page 1125].
- •
- The Enterprise Event Enablement - Configure Channel Bindings app is visible. If the Enterprise Event Enablement - Configure Channel Bindings app is not visible, add the Enterprise Event Enablement business catalog to the SAP\_BR\_ADMINISTRATOR role using the Maintain Business Roles app. The change in your role becomes effective after you have logged out and logged in again.
## Context
You can configure event consumers delivered by SAP manually.
## Procedure
1. Log on to the SAP Fiori launchpad in the ABAP environment system.
2. In the Communication Management app, select the Enterprise Event Enablement - Configure Channel Binding app.
3. Choose a channel name (created in Creating Communication Arrangements [page 1125]).
4. In the Inbound Topic Bindings tab, you can do the following:
| Option                                           | Description                                                                                                                           |
|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
| Create a new topic.                              | 1. Choose Create . 2. Enter a topic name. 3. Choose Create to save your entries. The new topic is listed in the Inbound Topics table. |
| Delete an existing topic created by an end user. | 1. Select the checkbox of the topic you want to delete. 2. Choose Delete .                                                            |
| Define table parameters.                         | Click the gear icon to define the table parameters.                                                                                   |
## Next Steps
The Inbound Topics table contains all inbound event topic bindings that exist for the selected channel and communication arrangement. The fields can have the following values:
## Status: Ok
| Status: Incomplete                      | No topic consumer exists for current topic binding.                                                                                                                   |
|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Status: Invalid                         | The current topic binding is invalid for at least one topic consumer. This means either the topic filter doesn't exist or the corresponding destination is incorrect. |
| Topic                                   | Is the topic presentation.                                                                                                                                            |
| Maintained by: End User                 | The event inbound topic binding was created manually by a user.                                                                                                       |
| Maintained by: Communication Management | The event inbound topic binding was created automatically during the configuration of a generated event consumption model.                                            |
<!-- image -->
##  Note
In case invalid bindings maintained by an end user exist, you can delete this binding by:
- choosing Delete invalid bindings on top of the page or
- selecting the respective topic and choosing Delete .
##  Note
To enable the consumption of events, the AMQP protocol replaces the MQTT protocol. New communication arrangements use the AMQP protocol by default. Existing communication arrangements can be updated via the service key. To do so, refer to Maintaining Communication Arrangements [page 1128]
.