Logical Flow
The overall logic is to filter and send data from Akeneo to the Integration Suite, then do the mapping and send it to the SAP S/4HANA . The accelerator eases the mapping and synchronization part. The entire logic is described in this page for ease of usage. The accelerator needs to be used in the integration suite and kickstart the entire
Data Flow Details:
- Source: The PIM triggers data output based on the event platform. Included in the package
- Middleware: iFlows in SAP Integration Suite parse the incoming structure, map to the target API schema, and handle routing. Included in the package
- Target: SAP S/4HANA recevie data via outbound IDoc or service call. (Out-of-scope - not included in the package)
System Landscape
| System | Role | Integration Type | Location |
|---|---|---|---|
| Akeneo PIM | Source system for data | Event platform | External Cloud / SaaS |
| SAP Integration Suite (BTP) | Integration & transformation layer | Middleware (iFlow-based) - the accelerator is used in the Integration Suite | SAP BTP (Cloud Foundry) |
| SAP S/4HANA | Target system consuming Material data | Data provider | On-premise / Cloud |
Additionally, for onPrem systems, it is recommended to add an SAP Cloud connector:
| System | Role | Integration Type | Location |
|---|---|---|---|
| SAP Cloud Connector (optional) | Secure tunnel for on-premise S/4HANA | Connectivity agent | On-premise |
More details on each system and accelerator role:
Akeneo PIM (Target System)
- Source of truth for Master data. Product Experience Management platform used for managing or extending Material data operations.
- Send Material Master data through
- Event platform
- Requires authentication (Basic Auth in the package/accelerator)
SAP Integration Suite (Core Integration Layer)
- Acts as the central middleware for data orchestration and transformation.
- Hosted on SAP BTP environment.
- Contains multiple iFlows designed to:
- Receive Material Master data from Akeneo PIM.
- Transform and map data as needed.
- Push data to the third-party system, SAP S/4HANA, via appropriate protocols.
The accelerator is used within the Integration Suite
iFlows (Integration Flows)
- Deployed in SAP Integration Suite.
- Each iFlow is responsible for:
- Handling a specific part of data
- Processing data in real-time
- Managing transformation, routing, logging, and error handling.
The accelerator is a package composed on iFlows
Connectors and Middleware Components
- SAP Cloud Connector (if on-premise S/4HANA is used)
- Open Connectors or custom APIs (for 3rd-party REST/SOAP integrations)
- Message Queuing or Eventing (if asynchronous model is used, e.g., via Event Mesh)
This part is not handled by the accelerator.
SAP S/4HANA (Source System)
- Data is received via:
- IDoc (if traditional interface is used)
- OData or API services (for more modern or RESTful scenarios)
- Typically connected via SAP Cloud Connector or via public endpoints (if whitelisted securely).
This part is not handled by the accelerator.
Integration Patterns
Synchronization compatibility
The accelerator is created to receive event from the Akeneo Event Platform.
Transformation Logic (at iFlow Level)
The accelerator proposes the standard message mapping capabilities and transformation:
- Field-level mapping between S/4HANA IDoc segments and Akeneo
- Unit conversions (e.g., internal vs. external UoM codes).
- Truncation, default values, or enrichment logic as needed.
Security & Authentication
| System | Security Mechanism | Notes |
|---|---|---|
| Integration Suite → Akeneo PIM | Token (based on OAuth2 & Basic Auth) | Token-based preferred for REST APIs |
| SAP S/4HANA | Basic Auth / Certificate | Cloud Connector tunnel if on-prem |
| Data at Rest (temporary) | Encrypted Storage | CPI message stores (short-term only) |
| Transport Security | HTTPS / TLS 1.2+ | Mandatory end-to-end |
Integration segment
- Role-based access control implemented on SAP BTP for iFlow deployment and monitoring.
- Audit Logs enabled via SAP BTP for traceability.
Error Handling Mechanisms
Error Handling
The SAP accelerator provides robust error handling beyond the standard capabilities of the integration suite. Exception subprocesses are used within each iFlow to capture both technical and logical failures. When an error occurs, a detailed message is logged to the Message Monitor. This log includes the error message, a sanitized snapshot of the payload, the timestamp, and the iFlow ID. The accelerator is also configured to handle common issues like connectivity errors, target system timeouts, authentication failures, and data mapping failures. For certain transient errors, an automatic retry mechanism using a Timer event is available. Additionally, integrators can configure optional alerts to be sent via email, Slack, or the SAP Alert Notification Service for immediate notification.
| Handled Scenarios | |
|---|---|
| Connectivity errors | target system timeout |
| Mapping failures | unexpected data types or missing fields |
| Authentication failures | expired tokens |
| Mapping transformation failures (common) |
Success and Logging
Upon successful completion of a process, the logs are stored in the Message Monitor for future reference. The accelerator also manages automatic retries for certain failures using a JMS (Java Message Service) queue, ensuring that messages are reprocessed without manual intervention.
The accelerator - feature coverage
The accelerator covers event Platform configuration, mapping and synchronization. The package has been conceived to handled the main use cases: synchronizing attributes and creating or updating products.
All the structural data needs to be pre-existing. There are no creation except from the values.
| Attribute types | Availability |
|---|---|
| Identifier | Available |
| UUID and SKUs optional | Available |
| Price | Available |
| Text | Available |
| Multi-select | Available |
| single select | Available |
| Measurement | Available |
| Text, Text area | Available |
| Number | Available |
| Images, files, asset | No |
| Reference entitity | No |
| Features available | |
|---|---|
| Filtering |
No
|
| Mapping |
Yes Message mapping |
| Transformation |
Yes Message mapping |
|
Product deletion
|
No |
| Product creation update | on subscription |
| Pre-existing catalog structuration in S/4HANA and PIM | Mandatory |
| Full synchronization | No |
| Delta or differential synchronization | No |
| Manual synchronization | No |
| Scheduled synchronization | No |
| Synchronization logs |
Yes Default in the integration Suite |
| Monitoring |
Yes Default in the integration Suite |