SAP Business Technology Platform vs. SAP Integration Suite

SAP Business Technology Platform is highly suitable for AI agentic development, particularly when workflows require dynamic orchestration, modular service integration, and real-time decisioning. However, it may be less effective in environments where backend services are fully encapsulated and do not expose interfaces or events that SAP Business Technology Platform can interact with—limiting its ability to orchestrate or extend those services meaningfully.

Incentivized

In our case to have a such a poweful middleware in the cloud, give us a lot of benefits such as maintenance and support. In the integration part to be able to connect SAP and Non SAP applications makes SAP Integration Suite a good investment when our master data in this case is in S4HANA. Less appropriate is that sometimes the updates in production tenant failed and they have to downgrade or repair the issues. Affecting the usage of the tool. I guess SAP team have to be more aware of performing the changes and tested well on development environments and then when they know for sure that is the correct way to go with the update put it in production.

Incentivized

• Services are operated by SAP with outstanding support, always giving a helping hand even if it is custom code or solution provided on the platform
• Services are easily connectable via standard approach to our backend SAP systems in SAP Rise/HEC
• Secure access using identities from our existing identity management helping us to safeguard data security from within SAP systems up to custom frontend applications

Incentivized

• Enhanced API management features that allow now the integration with a multitude of data feeds and rating agencies
• Immediate evaluation of potential issues and configurable thresholds and automatic notifications.
• The application will monitor all aspects of compliance and update them automatically for several jurisdictions at time

• For IAG, if there are multiple roles it can be overwhelming from an UX standpoint.
• Controlling and identifying shadow user creation is not as intuitive.
• Unlocking admin rights to an environment seems very easy if having elevated permissions, this seems like something that should have more controls rather than being able to unlock admin rights yourself.

Incentivized

• Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
• Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
• Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective

Incentivized

Seamless integration with external system and dashboard to monitor the data flow and analysis are very essential for the business. The way the product is designed and modelled lead to minimum business disruptions. Adopting to the new and modern technology was easy. Keeping the central system as clean and adopting project bases development are advantages.

Incentivized

It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.

Incentivized

Okay, so the content that we have built on the platform is limited to specific testing on the iFlows within integration suite. The visualization layer is nice to use and helps with the design elements, however with developers that are more used to markup languages, it doesn't have the same CLI type feel when you want it. Perhaps the majority of users are that deep, but other platforms have a better CLI type developer experience.

Incentivized

The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.

Incentivized

The biggest problem we ran into was communication between SAP Business Technology Platform and onsite resources. Unfortunately our SAP Business Technology Platform and Cloud systems are under different customer numbers. I constantly had to open tickets under each customer number because I was unsure of where the issue lied. And having to create a dummy ticket for our ECC systems to open the ECC connections for another ticket under the Cloud customer is a pain.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Training material in Developers Community or from Learning hub are really good... also most of the time we route through Discovery center... so materials provided by SAP is really good.

Incentivized

Having a full cloud native environment for devlopment of microservices and digitals solutions while having standardized access to our core data on SAP via cloud connector is one of the main benefits of using BTP over others hypervisors. BTP is the standard hyperscaler as soon as something relies on data from SAP systems in our company now

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

Initially, SAP Business Technology Platform works hand in hand with S/4 HANA and the SAP product suite, but also can go and extra mile and integrate with other non-SAP products and services at hand. It's capable enough to understand the ERP use cases component and develop intelligent applications to satisfy the users.

Incentivized

SAP Integration Suite was already part of our SAP stack, part of Business Technology Platform, with out-of-the-box integration with S/4 HANA transactional and ERP system that we are using as our main back-end. Thus, we are achieving significant Total Cost Optimization benefits or running both solutions on the same platform, hosted on Azure cloud.

Incentivized

• Still using traditional devops instead of using build. Very high cost in development.
• Still using Node.js instead of REST ABAP. Additional cost of resources. Migration of current CAP to RAP will be costly and do not have a business case yet. Continue with multi-language is costly.
• Integration suite is power but the migration from PIPO to IS has been more challenging than being advertised.

Incentivized

• In the long run will enable us to undeploy our on premise solution
• As long as integration suite doesn't support all capabilities PO has complete migration is hard
• Will probably be cheaper than our on premise solution when we are completely migrated

Incentivized