Product and Version
|Release Date||January 2021|
|SAP Server Platforms Supported||SAP NetWeaver 7.0x, SAP NetWeaver 7.3x, SAP NetWeaver 7.40, SAP NetWeaver 7.50, SAP HANA SAP Application Suites, SAP ERP 6.0, SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0, SAP Industry Solutions based on SAP NetWeaver 7.0, SAP MDM 7.0, SAP HCM, SAP BW/BI 7.x, SAP EP 7.0|
|Operating Systems Supported||All supported by SAP|
|Databases Supported||All supported by SAP|
|Deployment Mechanisms||TMS, CTS+|
|Java Stack Deployment||All supported by CTS+ (CTS+ must be pre-configured)|
|Operating Systems Supported||Windows 8.0, 8.1, 10|
|Requirements||SAP GUI for Windows 7.10, 7.20, 7.30, 7.40, 7.50, 7.60|
|Citrix Versions supported||Some Basis Technologies customers choose to install the Windows client on a central Citrix server. Basis Technologies do not formally test against different Citrix releases but the Windows GUI is a standard Win32 application with networking capabilities through SAP’s RFC drivers, and should therefore run under Citrix’s default virtual environment without the need for unusual configuration.|
|Browsers Supported||All supported by SAP|
|SAP GUI for Windows||All supported by SAP|
|Certification Type||ABAP add-on for SAP NetWeaver|
|Certified Functions|| Integration with SAP Transport Management System
SAP Solution Manager Ready functionality
|Certification Document Number||12648 (SAP NW 7.50), 12658 (SAP S/4HANA)|
Additional Requirements & Information
|Central Domain Controller System|| Installed to the ABAP stack of the Solution Manager system must be a Unicode system running SAP NetWeaver 7.01 or above
Application data is stored on the domain controller system
|SAP systems to be managed||Requires the server software to be installed in each system|
|RFC Connections||Requires specific RFC destinations and users to allow connection to systems in the landscape|
|Server software object naming||All objects exist in the /BTI namespace so will not update or overwrite any existing SAP or customer objects|
|Additional Load|| Additional RFC users connected
Background jobs to perform automated scheduled imports
|Additional Database Space|| Minimal additional space per change / transport. Small product footprint; typical 65kb average per transport (excluding Attachments).
Attachments stored in compressed format in SAP cluster table.
|Industry limitations||None. Currently used by 200+ customers across more than 30 SAP verticals|
|User limits||None. Currently used by Customers with user communities ranging from 10 – 3000 AC users|
|Number of Paths (Routes)||Can manage 1 – 99 (max) Development tracks|
|Number of Transports||No limitations. We are aware of existing Customer managing 40K transports concurrently; they deploy 90K transports to Production annually.|
Thanks for your feedback.
Post your comment on this topic.