Growing strong

We are using AI Core, AI launchpad and SAP Build services to build custom solutions on SAP Eco Systems. We also exploring Joule Skill extensions to extend skills and build new agents. Cloud Foundry is useful as well to deploy Python APIs as well.

What offerings are available on the platform and how easy it is to deploy and use on the platform.

SAP BTP was not something the team could just “pick up” without any training, especially for topics like security, subaccount design, and integrations. Some self‑learning and experimentation helped, but structured online courses and documentation made a big difference, so learning without training is not recommended for most teams.

Yes, a few best practices have helped a lot in keeping our BTP landscape manageable and secure.​Design global account and subaccounts upfront (by landscape, region, and purpose) and stick to clear naming and tagging standards.Apply a strict least‑privilege model for roles, role collections, and spaces, and centralize identity/SSO early.Standardize transports, logging, and monitoring so every app follows the same deployment and operations pattern.

Two things are worth mentioning.​We have set up a standardized subaccount and space structure with common destinations, logging, and monitoring so new apps follow the same pattern instead of one‑off setups.We also customized role collections and IAS/IDP groups to align with our internal job roles, which made access control and SSO much smoother for end users.

No, we have not purchased premium support for SAP BTP. Given our current scale and limited number of mission‑critical workloads, the standard support included in our SAP agreements has been sufficient so far. For now, we prefer to invest in internal skills and good platform practices rather than pay extra for an upgraded support tier.

There was a notable incident during a production deployment where a new BTP integration started failing intermittently and impacting a critical business process. SAP support engaged quickly, pulled in both BTP and backend experts, helped us narrow down the root cause, and provided a clear workaround plus a permanent fix within a short time window. Their responsiveness and willingness to stay on calls until things were stable really stood out as exceptional support.

Focus first on getting the foundations right: destinations, authentication/SSO, and network connectivity, and standardize them so all integrations reuse the same patterns. Whenever possible, prefer standard APIs, events, and connectors over custom point‑to‑point logic, and invest in good monitoring and error handling so integration issues are visible early instead of being discovered by end users.

The main items we could negotiate were around pricing, consumption commitments, and some flexibility in ramp-up. We were able to agree on discounts tied to a multi‑year term, clarify how BTP credits and services could be rebalanced during the contract, and secure reasonable terms for adding more subaccounts and services as our usage grows.

Have a clear roadmap and usage forecast before commercial discussions, so you can challenge proposals and pick the right licensing model instead of just accepting a standard package. Build a good relationship with both the account manager and technical contacts, and document key agreements and follow-ups in writing so expectations, responsibilities, and timelines stay aligned over the long term.

Our primary SAP BTP use case is a “Service Request and Approval Hub” built on BTP to orchestrate workflows across SAP ECC/S4, ServiceNow, and other systems. It provides a Fiori/UI5 front end where users can create and track requests, while BTP handles approvals, integrations, and notifications in the background so processes run end‑to‑end without emails and manual follow‑ups.​