SAP Cloud Platform Reviews

We provide services and implement solutions for our clients.

We integrate solutions and have experience with many different interfaces with possibilities to integrate. The primary use case of this solution is to integrate data.

The most valuable feature is the data synchronization, or the push and pull of the data.

The functionality of the interface can be difficult. Usability is a challenge most of the time and not being able to get all of the information.

Security, authentification, and logs need to be improved.

In the next release, I would like to see better navigation, better usability, clearness, and better integration with new technologies.

I have been working with this solution for five to six years.

The solution is stable, but it depends on the customer's needs and experience.

It can be difficult and we have the experience, but sometimes you start and realize that there may be some gaps making it difficult to handle.

We have contacted technical support, but usually, the response time is not optimal. They are average. When the integration is at the end processes and you need support quickly, you won't hear from them for a few days. This is not helpful.

Previously, we were using Microsoft iOS. When using 3D, Microsoft is an easier tool to use. iOS is a complex tool to understand. Also, Microsoft support is better.

The initial setup is straightforward.

It can take four to five days to deploy this solution.

The decision is with the customer and what they want. We have had bad experiences or negative ones in performance and with the functionality.

I would rate this solution a seven out of ten.

We are currently implementing POCs for our client using this solution.

Our primary use case involves fetching data that has been entered into the dashboard and updating it in our database. We also are fetching data entered into SuccessFactors and updating the ECC accordingly.

The current deployment is on a private cloud, which hosts our own database and ECC systems. The second POC was to connect to the public cloud for Twitter, Salesforce, and SuccessFactors data.

This solution has provided the means for our connectivity. The endpoint URL on the ETFs that we were using is on the public cloud. The problem is that the public cloud API could not access our private cloud, so we created a cloud connector. This allows our clients to use the public cloud to consume our services, which are established on the private cloud.

The most valuable feature of this solution is the content modifier. These are the mapping features that allow us to create cloud connectors. The content modifier also allows us to perform data conversions, encryption, and decryption within the cloud.

We also use mapping transformation and message transformation. The mapping transformation allows us to connect our on-premise ECC to the cloud system.

We would like the ability to create our own flexible data type, directly in the system. This is functionality that is available in the older, on-premises version, but not available on the cloud platform. Our current workaround is to create the definition and import those features. If this functionality were available directly then it would be a big plus because as it is now, it requires a lot of effort.

Better connectivity to on-premise systems would help us to support older systems that are migrating to the cloud. This would give us more confidence in telling clients with old legacy systems that SAP has the capability to handle their landscape.

I believe that this solution is stable. We have not faced any issues, and apart from that, SAP will release updates to fix bugs and add new features on a quarterly basis. They're continuously updating the cloud system. Stability and security are not things that we are worried about.

This solution is scalable.

I have not had the chance to directly connect to the technical team for the cloud system. However, I have interacted with SAP for on-premise issues and notes. They have their own SLA and they're very good at it. I always get good support from the SAP team.

Based on my experience, I believe support will be good for the cloud system, as well. 

Prior to using the cloud platform, I had used the on-premise SAP integration solution for almost five years. I have also used other solutions to integrate with SuccessFactors.

The initial setup of this solution is straightforward. The only thing to make sure of is access. A few tasks, such as creating a server account and creating a database connection, are necessary but straightforward to do. It does not require an expert, as long as the authorization is given.

Once the initial setup is complete, the deployment to the cloud is very fast. In a few seconds, we can deploy this service and start posting.

The number of people required to deploy and maintain this solution depends on the landscape and the number of interfaces. In the case of our client, where we have thirteen or fourteen interfaces, two people are sufficient. This could change based on the criticality and time that we are allowed.

We have deployed this solution to two tenants. One is a training tenant, and another is a client tenant. The latter is where we are doing the POCs, and we have a dedicated team that has all of the authorizations.

For the training tenant, we have performed all of the activity. I have access to the SAP Cloud Cockpit, where we can create our own subtenants and you can use SAP Neo to create our Java services. Normally, however, we don't perform these types of tasks in real-time. They are done in the send-off systems.

Licensing costs for this solution are based on the number of users and the bandwidth.

SAP is more expensive than other solutions, but they have total prepackaged content for ERP. They have a vast module, and a good hold on the complete ERP. It's not cheaper, but I believe that it is the best in the market in terms of ERP. 

When you are using an on-premises version, you need to spend money on the dedicated infrastructure, licensing costs, maintenance, support, etc. In a cloud system, SAP Cloud Platform provides a solution where the licensing costs are based on the number of users and the bandwidth. You don't have to spend time and money on infrastructure or maintenance. The best part about using the cloud solution is that if there is any kind of memory issue in your production system then you can immediately extend your memory at the time.

For an enterprise that has the proper integration within their ERP systems, I definitely recommend this solution. If the majority of their business is on cloud systems then I suggest SAP Cloud. However, if most of the business is on-premises then they may not want to go with the cloud version. There are many issues with connecting a VPN between the cloud and an on-premises system. So, it depends on the landscape. Overall, I would definitely recommend going with a cloud system.

The biggest lesson that I have learned from using this solution is that SAP has been able to save us a great deal of time. They know about businesses and provided us with most of the business scenarios. Suppose, for example, that I need to do an implementation for a client. They provide solutions that I simply have to import to provide the client with an efficient system, and can then be customized based on their requirement. It saves a great deal of development effort.

This is a good solution, but I would like to see more flexibility to connect to the on-premises systems. There are older systems that are being moved from on-premises to cloud, but they have years of data and sometimes there are problems. Supporting these systems is difficult, and better connectivity would help us perform better support.

I would rate this solution an eight out of ten.

We use hybrid-cloud, on-prem, and cloud models of this solution. The primary use case of this solution is for our customer's. We integrate it for them. 

The integration flows are the most valuable feature of this solution. 

The source controller needs improvement. There are some disadvantages to it. Versioning also needs improvement. 

I would like for it to have integration to GitHub. 

It is stable. We haven't had any big issues. 

It is scalable. The number of staff members we will need for a deployment will vary on the project. We need one for a smaller project. 

We have never needed to contact their technical support. 

The initial setup is straightforward. The time it takes to deploy will depend on the requirements. It takes around a couple of days. 

My advice to someone considering this solution would be to check the standard capabilities and leverage existing standard features. 

I would rate it an eight out of ten. Not a ten because it is missing features. 

Our primary use is for the cloud platform identity authentication, whereas this serves as a proxy between Azure AD and our SAP cloud applications.

It has improved our speed to bring our mobile applications into productive use in a cost-effective way. The deployment of the Fiori Cloud Edition eliminated the use of an on-premise infrastructure, for example, to provide an SAP Gateway installation.

To be able to define multiple sub accounts in order to accommodate and separate development, test, and productive environments.

The product could be improved for consistent user interfaces. Although it is one platform, the user interface logic (e.g., where buttons are defined on the screen) differs from service to service.

The tool's reliability is a disappointment for us. 

I have been working with the product for two years. 

I rate SAP Cloud Platform's stability an eight out of ten. 

I rate the solution's scalability an eight out of ten. My company has 800 users. 

SAP's technical support is not working as it should be. 

Neutral

We used Microsoft before the SAP Cloud Platform. 

SAP Cloud Platform's deployment ease is in the middle. It is missing crucial information, and the process takes a couple of days to complete. 

I rate the overall solution an eight out of ten. 

We use the product for process integration, data integration, etc.

The product provides native integration to enterprise resource planning software. It becomes easier for customers to leverage the product instead of developing or writing integration from the beginning.

The product needs improvement for serverless native integrations. They should opt for serverless features as all the customers worldwide choose cloud-based products.

We have been using SAP Cloud Platform Integration for 20 years.

The product is very stable. I rate its stability a ten out of ten.

We have enterprise businesses as our customers for SAP Cloud Platform Integration. The product is highly scalable. I rate its scalability a nine out of ten.

The initial setup is simple enough. I rate the process an eight or nine out of ten.

SAP Cloud Platform Integration is an expensive product. I rate its pricing an eight out of ten.

I recommend SAP Cloud Platform Integration to others and rate it a seven out of ten.