Whitepapers

This guide provides a complete step-by-step procedure to deploy virtual machine instances on Amazon Web Services (AWS EC2), Microsoft Azure (Azure VM), and Google Cloud Platform (GCP Compute Engine), followed by comprehensive post-deployment configuration. Each cloud section covers three deployment methods: GUI (Console), CLI, and Infrastructure-as-Code templates. The post-deployment activities section covers OS-level hardening, disk configuration, monitoring, backup, patching, and governance — applicable to all three clouds.

This guide provides the complete set of SAP transaction codes (T-codes) required by the BASIS team for day-to-day monitoring, performance analysis, and troubleshooting across five system components. Each table includes: the T-code, the monitoring category it belongs to, what it shows/does, and the most important use case or trigger for using it.

SAP BusinessObjects (BOBJ) BI Platform is SAP’s enterprise reporting and analytics suite, encompassing Crystal Reports, Web Intelligence (Webi), Analysis for Office, Dashboards (Xcelsius), and the BI Platform management layer (Central Management Server — CMS). Monitoring BOBJ in SAP Cloud ALM ensures continuous visibility into server health, report scheduling, user sessions, processing server availability, and connectivity to underlying databases and SAP ERP systems. This document provides the complete step-by-step procedure to integrate an on-premise SAP BOBJ BI Platform 4.3 system with SAP Cloud ALM, configure all relevant monitoring use cases, and set up proactive alerting. The integration combines SAP Cloud Connector for secure tunnel connectivity with SAP Host Agent for system-level metrics collection, and the BI Platform REST API for application-level monitoring data.

SAP Business Technology Platform (BTP) is SAP’s cloud platform that provides integration, extension, data management, and analytics services. The SAP Cloud Connector (SCC) is the secure tunnel that bridges on-premise systems (S/4HANA) with BTP cloud services without opening inbound firewall ports. This document covers three key integration scenarios: S/4HANA ↔ BTP Integration Suite (for iPaaS/API management), S/4HANA ↔ SAP Analytics Cloud (for live BI), and the underlying Cloud Connector and Destination configuration that enables both.

SAP BW/4HANA is the next-generation SAP data warehouse platform, optimized exclusively for SAP HANA. A Support Package Stack (SPS) update delivers cumulative corrections, performance improvements, new analytic features, and compatibility updates for connected components (SAP HANA, SAP Datasphere, SAP Analytics Cloud, BTP). The update is executed using the Software Update Manager (SUM) in Patch mode — identical in tool to an S/4HANA SPS update but with BW/4HANA-specific package components, pre-checks, and post-update validation requirements. BW/4HANA SPS updates are more impactful than a typical ABAP stack update because they affect not only the ABAP layer but also HANA-native data store objects (DSOs, Advanced DataStore Objects, CompositeProviders, HANA Calculation Views) and connected analytical front-ends (SAC, Analysis for Office, BOBJ). Careful pre-update and post-update validation is essential to maintain reporting continuity.

A BW/4HANA system copy creates an entirely new, independent BW/4HANA system from an existing source — complete with new infrastructure, fresh HANA and ABAP installation, and the source system’s data restored into the new target. Unlike a system refresh (which overwrites an existing target), a system copy provisions brand-new servers, assigns a new System ID (SID), and registers the new system independently in the SAP landscape. BW/4HANA system copies are more complex than S/4HANA copies because of the mandatory BW-specific post-copy activities: source system reconnection (RSA1), ODP delta queue management, BW object mass activation, repository consistency repair (RSRV), and process chain reconfiguration. These BW-specific steps are as important as the technical infrastructure steps — skipping or performing them incorrectly will leave the new BWT system unable to extract data or run reports.