SAP System Connections
Teamscale connects to an SAP NetWeaver® AS ABAP® system through an SAP ABAP System Connection. To add one, go to Admin > Settings > SAP > SAP ABAP System Connection and click Add. Every SAP system needs its own connection, identified by a unique connection ID — the three-letter SAP system ID is a good choice.
How to Set Up an SAP System Connection
For step-by-step instructions, see our how-to guide.
System and Logon Parameters
Which parameters are required depends on the connection type, that is, whether the connection is direct or uses logon balancing.
| Direct connection: Application server host | Mandatory parameter for direct connection: The full qualified host name of the SAP NetWeaver application server, e.g., saphost.me.com |
| Direct connection: Instance number | Mandatory parameter for direct connection: The instance number (formerly called system number) of the SAP NetWeaver application server, e.g., 00 |
| System ID | Mandatory parameter for logon balancing connection: 3-letter SAP system ID, e.g., NSP |
| Logon balancing connection: SAP message server | Mandatory parameter for logon balancing connection: Host name of SAP message server |
| Logon balancing connection: Group of SAP application servers | Mandatory parameter for logon balancing connection: Group of SAP NetWeaver application servers (e.g., public) |
| Logon balancing connection: SAP message server port | Optional parameter for logon balancing connection: Port of message server, typically 36xx where xx refers to the instance number |
| SAP Router string | Optional parameter for connection to systems behind an SAP Router: SAP router string contains the chain of SAP routers and their port numbers and has the form (\H\<host>[\S\<port>])+ |
| SAP client | Mandatory parameter: Defines the client used for logon (e. g. 001) |
| Logon user for password-based authentication | Mandatory parameter for password-based authentication: The SAP username which should be used by Teamscale |
| Logon password for password-based authentication | Mandatory parameter for password-based authentication: Password of the user |
Object Selection Parameters
These options control which code Teamscale retrieves, how often it is updated, and whether other result data such as test coverage is included.
| Include objects in default custom namespaces | Specifies if ABAP source code objects within the default custom namespaces Y... / Z... should be retrieved by Teamscale. |
| Further custom namespaces | Comma-separated list of further custom namespaces like /ABC/, /DEF/ for which ABAP code should be retrieved. |
| Polling schedule for changes | Defines in which interval continuous code changes are retrieved from the SAP system. |
| Polling schedule for full sync | Defines in which interval a full synchronization of the code base is performed. |
| Use background job for full sync | If enabled, full sync is scheduled in the background. |
| Include objects in ABAP Dictionary (DDIC) | In addition to ABAP source code, this will also retrieve DDIC objects (table definitions, data elements etc.) in the given namespace(s), e.g. for use in architecture analysis. |
| Include all objects with modifications | In addition to ABAP custom code, this will also retrieve modified ABAP standard objects. |
| Include programs generated from BW objects | On SAP BW systems, this will also retrieve ABAP programs generated from BW transformations, queries, and DTPs in the given namespace(s). This is used for test gap analysis. |
| Include package information for standard objects | During full sync, this will retrieve package information for all ABAP and DDIC objects on the system. This is useful for analyzing dependencies to SAP standard packages. |
| Include code coverage in full sync | This will retrieve procedure execution information recorded by SCOV on the system. If not enabled already, Teamscale will attempt to start SCOV automatically. |
| Include code coverage with change polling | This may result in very high disk space consumption and long processing time. Especially, this option should not be enabled in combination with very frequent incremental change polling, e.g. every 10 minutes. Further, it should not be enabled when immediate analysis results in SAP or Eclipse ADT are desired, e.g. when using Teamscale during transport release. |
| Clear table COVRES after coverage retrieval | If enabled, the table COVRES which holds coverage data will be cleared after retrieving the coverage data. |
Code Inspector Execution
These options control the execution of SAP Code Inspector during code retrieval. They require a Code Inspector variant to exist in the SAP system.
| Code Inspector: variant name | Name of an SAP Code Inspector variant which should be executed |
| Code Inspector: variant user | Specifies the SAP username of the variant owner (leave empty for public variants). |
| Code Inspector: include specification | Defines for which code objects Code Inspector should be executed. |
| Code Inspector: exclude specification | Defines exclusions of code objects for Code Inspector execution. |
The name of the executed Code Inspector variant must be specified in parameter Code Inspector: variant name. If this is not a public variant, but a user variant, the SAP username of the owner must be additionally specified in Code Inspector: variant user.
Check Descriptions
| Check descriptions: Retrieve via HTTP(S) | Turns the retrieval of ATC check descriptions on and off. Disable it if the SAP system does not expose an HTTP(S) endpoint, or if you do not want descriptions to be fetched from it. |
| Check descriptions: ICF base URL | The base URL of the HTTP(S) server (ICF) of the SAP system, for example https://my-sap-host:8443. Enter only the protocol, the host and optionally the port. Leave it empty to use the host of the RFC connection over HTTPS on port 443. |
Available from Teamscale 2026.5 and Teamscale Connector for SAP NetWeaver® AS ABAP v2606.
Secure Network Communications (SNC)
SNC encrypts the RFC communication between Teamscale and SAP NetWeaver. Both the SAP system and the Teamscale server have to be prepared before these options take effect.
| Use Secure Network Communications (SNC) | Tick to enable SNC |
| SNC name of the communication partner server | The SNC name of the SAP system, something like p:CN=SNC, O=ACompany, C=EN |
| Own SNC name of the caller | The client SNC name of Teamscale, something like p:CN=TEAMSCALE, O=ACompany, C=EN |
| Use SNC Single sign-on (SSO) | Enable logon by X.509 certificate instead of username/password |
| Path to X.509 certificate | Path to *.crt file holding the X.509 client certificate, only required if SSO mechanism is enabled |
Global Settings
These options apply to all SAP connections and are found under SAP > SAP ABAP System Connections - Global Settings.
| Schedule for requesting results of asynchronous ABAP exports | Scheduling interval of the polling job that retrieves the results of a background full sync. |
| Maximum wait time | How long scheduled jobs are polled from Teamscale if no results could be retrieved for a long time. |
| Path to the SAP Cryptographic Library | Directory containing the library files of the SAP Cryptographic Library, required for SNC. |
JVM Properties
A few aspects are configured on the Teamscale server rather than in the web interface.
com.teamscale.abap.archivingPeriodInDays | How long raw export files are retained, in days. Defaults to 365. |
com.teamscale.abap.snc.credentials-user | The operating system user running Teamscale, used for SNC credential management. Set automatically for Docker instances. |
com.teamscale.abap.snc.create-credentials-at-startup | Whether Teamscale auto-creates a cred_v2 file from all available SAP system PSEs at start-up. |
See Configuration on the Teamscale Server for how to set these.