Boomi for SAP: CDC Flow set up guide
This guide describes how to configure the Change Data Capture (CDC) between Boomi for SAP (Producer) and Boomi Data Integration (BDI) (Consumer) using Boomi Event Streams.
Before you begin, review how the following product components work together in the CDC pipeline:
- Boomi for SAP: Create table services and configure SAP events to publish to Event Streams.
- Event Streams: Set up an environment and create a topic to receive SAP events.
- BDI connection: Connect to Boomi for SAP and enable the CDC toggle with the Event Streams credentials.
- BDI Data Flow: Configure the river to consume events and load data to your target.
For connection field reference, refer to Boomi for SAP connection. For Boomi for SAP configuration, refer to Getting started with Boomi for SAP.
End-to-end flow summary
The following table provides an overview of the setup components and the frequency of configuration.
| Step | Component | Purpose | Frequency |
|---|---|---|---|
| 1 | Event Streams Topic | Acts as a shared topic for all SAP events. | One-time |
| 2 | SAP Receiver | Publishes events from SAP to the topic. | One-time |
| 3 | SAP Event | Defines the specific SAP objects that emit events. | Per object |
| 4 | BDI Connection | Connects to SAP and enables CDC mode. | Per connection |
| 5 | BDI Data Flow | Manages the data pipeline to the target system. | Per pipeline |
Maintain a 1:1 relationship between an SAP event in Boomi for SAP and a table service. Reusing the same table service across multiple events causes duplicate CDC messages on the Event Streams topic and inflates message costs.
Step 1. Event Streams topic creation
This is a one-time prerequisite. Before starting, you must create a centralized topic to handle SAP Business Object events. For more information, refer to Topics.
The following table is a specific example of the parameters required for this setup.
| Step | Detail | Parameters |
|---|---|---|
| 1.1 | Create Unique Topic | Use a unique name like bdi_sap_events_environment. (Best practice: one topic per connection). |
| 1.2 | Assign Credentials | Generate a multiple Produce/Consume token for the producer and consumer. |
| 1.3 | Record Connection Parameters | Produce Message URL (Multiple messages). Topic Name: As created in step 1.1 Token: As generated in 1.2 |
| 1.4 | Reuse | BDI uses the Topic name and Token, whereas Boomi for SAP requires the Bootstrap URL and Token to establish the connection. |
| 1.5 | Validate Access | Verify reachability and permissions for producing and consuming messages. |
Step 2. Configure the Boomi for SAP Receiver
This is a one-time prerequisite. The receiver is a reusable component that publishes SAP events to your Event Streams topic. For more information, refer to Setting up the Event Streams Receiver.
The following table provides an example of the configuration values required for a Data Integration CDC setup.
| Step | Reciever Component | Details |
|---|---|---|
| 2.1 | Create Receiver | Boomi Event Streams Name: For example, bdi-receiver-sap |
| 2.2 | Configure Connectivity | Bootstrap URL: Use the URL from Step 1.3. Token: Use the token from Step 1.2. Receiver id: Enter a receiver name. |
Upon completion, you have a reusable receiver that securely holds your Event Streams credentials. All future SAP events will publish through this centralized gateway.
Step 3. Create SAP Events
This configuration defines the specific SAP entities that generates Change Data Capture (CDC) events. For more information, refer to Business objects.
The parameters in the following table serve as an example for your setup.
| Step | Action | Detail & Parameters |
|---|---|---|
| 3.1 | Bind to Receiver | Select the receiver created (for example, bdi-receiver-sap). |
| 3.2 | Business Object | Define the entity to monitor, such as SalesOrder or PurchaseOrder. |
| 3.3 | Operations | Select the lifecycle triggers: CREATED, CHANGED, and DELETED. |
| 3.4 | Configuration | Mode: Real-Time Format: JSON 1.6 Type: Payload |
| 3.5 | Validate | Trigger a change in SAP to verify the message appears in the Event Streams topic. |
Step 4. Set up the BDI connection
Enable real-time data synchronization by linking your SAP connection and Event Streams credentials within the Data Integration interface. For more information, refer to Boomi for SAP connection.
The following table serves as a sample configuration for your setup.
| Step | Action | Detail & Parameters |
|---|---|---|
| 4.1 | SAP connection details | Provide the Connection Name, Host, Port, Username, Password, and SAP Client. |
| 4.2 | Enable CDC connectivity | Switch the Enable CDC Connectivity (Event Streams) toggle to On. Environment Token: Enter the token generated in step 1.2. Event Streams Topic Name: Enter the topic name created in step 1.1. |
| 4.3 | Validation rules | Missing details trigger an error, and invalid tokens or topics lead to an Access Denied status. |
| 4.4 | Notification | A setup warning appears if CDC is enabled without the required Event Streams information. |
Step 5. Configure the BDI Data Flow
Establish the final data pipeline to orchestrate the flow of events from Boomi for SAP to your preferred target. For more information, refer to Configuring schema.
The following table provides a sample configuration for your Data Flow setup.
| Step | Action | Detail & Parameters |
|---|---|---|
| 5.1 | Source & Target | Define Boomi for SAP as the source and select your target system (for example, Snowflake, S3, or Databricks). |
| 5.2 | CDC Options | Manage data synchronization behavior using Includes Migration and Skip Migration. |
| 5.3 | Schema Evolution | Maintain the default Enabled status to automatically detect and apply metadata changes from SAP to the target system. |
