SAP BTP
Connecting SAP systems on the Business Technology Platform is currently in trials at Nova: the SCIM-based route through SAP Cloud Identity Services is the documented path today, while direct RFC connectivity via WebSocket RFC is in the testing stage.
What Nova does with SAP BTP
- Provisions user accounts to BTP-hosted SAP environments through the SCIM 2.0 path: creating accounts, disabling them, and maintaining group assignments
- Direct BAPI calls into ABAP environments on BTP via WebSocket RFC: currently in trials, over an encrypted WebSocket connection straight to the SAP system
- Prerequisites: WebSocket RFC requires S/4HANA 1909 or later and activation by your SAP Basis team (ICM HTTPS port, certificates, UCON allowlisting)
- Why not classic RFC: the BTP connectivity proxy does not admit classic RFC connections from third-party software; we have verified and documented this
- Beta at Nova means we build the integration together with you in a project and clarify up front which operations work today and which do not yet
Technical integration
Two technical paths: SCIM 2.0 against SAP Cloud Identity Services (basic or bearer authentication) as the documented route today; in addition, WebSocket RFC through a Java sidecar with a TLS connection straight to the ABAP system, currently in trials.
In the identity lifecycle
Joiner/mover/leaver, request workflows, and recertification run for BTP targets on the same platform logic as for every other system; during the beta stage we clarify with you up front which operations your BTP landscape supports today.
Related integrations
All product names, logos and brands mentioned are property of their respective owners. They are referenced solely to describe compatibility and do not imply any partnership or endorsement.