Menu
Topic

Cloud

Runtimes, architecture, operations, Kyma & Cloud Foundry.

Picked up · Cloud

SAP Cloud ALM: the ITSM Console shows every call to the ticketing system

Ticket not created, alert not raised, mapping empty. With SAP Cloud ALM connected to ServiceNow or Jira Service Management, that used to mean digging through logs, matching timestamps and, when in doubt, opening a support case with SAP. The new ITSM Console under External API Management now shows …

community.sap.com ↗picked up by SigiDEENPicked up · Cloud

Neo ends in 2028: AI skills to help with the move to Cloud Foundry

Neo reaches end of life for external customers in 2028. That sounds a long way off. It isn’t.

community.sap.com ↗picked up by SigiDEENPicked up · Cloud

One Kyma cluster, several subaccounts: mapping namespaces cleanly

A Kyma cluster for every application is a fine idea with a hefty price tag. By default, every service instance lands in the subaccount where the cluster was created. The post shows how to point the SAP BTP Service Operator at a separate provider subaccount for each namespace, …

community.sap.com ↗picked up by SigiDEENPicked up · Cloud

SAP BTP ABAP Environment now runs on SAP’s own infrastructure, too

Since 19 September 2025, the ABAP environment of SAP BTP has also been running on SAP Cloud Infrastructure – SAP’s own kit rather than a hyperscaler’s. First region: Frankfurt with EU Access, and all the usual plans from standard down to free are on board.

community.sap.com ↗picked up by SigiDEEN

Picked up

community.sap.comSAP Cloud ALM: the ITSM Console shows every call to the ticketing systemcommunity.sap.comNeo ends in 2028: AI skills to help with the move to Cloud Foundrycommunity.sap.comOne Kyma cluster, several subaccounts: mapping namespaces cleanlycommunity.sap.comSAP BTP ABAP Environment now runs on SAP’s own infrastructure, too