SAP Business Technology Platform (SAP BTP) is the company's Platform-as-a-Service (PaaS) offering, that brings together intelligent enterprise applications with database and data management, analytics, integration and extension capabilities into one platform for both cloud and hybrid environments, including hundreds of pre-built integrations for SAP and third-party applications.
N/A
Upsun
Score 10.0 out of 10
N/A
Platform.sh helps companies of all sizes, from SaaS entrepreneurs looking to build, run, and scale their websites and web applications.
Out of the box Power Platform is more user friendly. The limitations with Power Platform is connecting to more solutions than basic SharePoint, SQL or data verse. When dealing with SAP data it is easier using BTP. approvals are similar in both systems without one being …
Oracle was at my previous company and SAP Business Technology Platform is at my current company. Both suites are a little difficult to use and have a large learning curve for accounting folks. Both need another app to read GL data and to upload journals. Oracle gave the ability …
We've done a little bit of development on AWS on their platform. It's good. It might be a little cheaper, but again, it doesn't connect as natively to SAP applications.
Uipath is more used in our org. SAP Business Technology Platform is relatively new to compare currently. Do not have exposure to answer this q fully at this point of time with me. Will possibly have more info later as we work more with SAP Business Technology Platform and have …
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. …
If you want to use a well-designed SAP technology to shift into the cloud, you will be more than satisfied with the BTP services overall. There are some improvements for beginners to help them get a better overview of what to do and how to start with their account. My recommendation is to take a foundation training course from the SAP learning hub to prepare for the first steps.
In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.
All the documentation around it is geared towards the enterprise use case, unlike some other hyperscalers' platforms.
The SAP Business Technology Platform is very good because it's got the SAP customer and their business processes in mind. Probably my favorite thing about it is how easy it is to get up and running with a new use case and how well it natively connects to an SAP solution.
The Automation Integration service has some outdated workflows
New services should be available as entitlements as soon as they are released for a particular region without having to buy them from SAP for zero dollars
Any subaccount should be able to change the IAS tenant. Currently, if you set it up for a particular IAS, you cannot change to another tenant and are required to recreate the services in a new subaccount.
Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.
I think its important to renew the BTP as it's the way to use SAP products in the feature. Java and R/3 systems are obsolete soon and you have to use the cloud products even to be in support and maintenance in the future. Therefore it's needed for every company to read into the BTP.
The development and deployment of applications require too many services. So, sometimes it is challenging as there are multiple services. The monitoring and logging mechanisms are not very apparent. This makes it difficult to choose the services required during design. Applications that use AI for eg., extraction or chatbots, are great use cases to build on BTP. Also custom applications that require a ERP integration but are not enhancements, are good use cases for development on BTP.
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.
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.
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
SAP Business Technology Platform is easily connectable using standard solutions to the onpremise backend SAP systems. Services can be linked with each other and with SAP systems in a managed and secure way, while with the other products getting the data, access and networking done is cumbersome. Also we can make sure to have all cloud environments in the same region using the multi cloud approach wich reduces latency problems.
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.
