ATC Central Check System
The concept name is not defined in the provided sources, so a precise definition cannot be grounded solely in the supplied snippets. Based on the available sources, ABAP Test Cockpit (ATC) is a code analysis tool that developers use to check ABAP custom code for quality, correctness, and migration readiness in both on-premise and SAP BTP ABAP environments. It supports a remote ATC setup using a central check system, where an on-premise system is configured as the checked system and delegates analysis to a central system. Developers can also manage findings through the Approve ATC Exemptions app, which allows authorized users to review and approve exemption requests for ATC check results.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept SAP Destination Service Configuration The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover related topics such as [inbound communication via principal propagation](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud), OAuth 2.0 SAML Bearer Assertion Grant, client certificate authentication, and [routing via destination](https://help.sap.com/docs/btp/sap-business-technology-platform/97d7a02cd6fd4f579fd96f41ee0d0c1d?locale=en-US&state=PRODUCTION&version=Cloud) in the ABAP environment on SAP BTP, but without a defined concept name, no accurate definition can be produced from these snippets alone.
- Concept ABAP Test Cockpit (ATC) The **ABAP Test Cockpit (ATC)** is a quality assurance framework in the SAP BTP ABAP environment that developers use to run automated checks on ABAP code to ensure its quality and correctness. It supports [custom code analysis](https://help.sap.com/docs/btp/sap-business-technology-platform/2fc0fea9aaff42728f8ccbcbe955f2a8?locale=en-US&state=PRODUCTION&version=Cloud) by performing remote checks against checked systems integrated into the landscape. Developers can [run ATC check runs](https://help.sap.com/docs/btp/sap-business-technology-platform/d8cec788fc104ff9ad9c3757b4dd13d4?locale=en-US&state=PRODUCTION&version=Cloud) and then read the results to identify and resolve issues in their ABAP codebase.
- Concept On-Premise Connectivity on SAP BTP **On-Premise Connectivity** on SAP Business Technology Platform refers to the capability that allows cloud applications to communicate securely with systems running in an on-premise landscape. Developers use it by [creating HTTP and RFC destinations](https://help.sap.com/docs/btp/sap-business-technology-platform/9b6510edf4d844a28f022b3db41f3202?locale=en-US&state=PRODUCTION&version=Cloud) to enable communication between SAP BTP and on-premise systems. Tools such as the Cloud Connector can be used to bridge on-premise databases or services — for example, connecting an SAP HANA on-premise system to SAP HANA Cloud — and trust configurations can be established between on-premise systems like SAP S/4HANA and SAP BTP to support secure integration scenarios.
- Concept SAP BTP ABAP Environment (Steampunk) The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as the [XCO Library](https://help.sap.com/docs/btp/sap-business-technology-platform/c154dffe892b4d9ea4566722f0bcd5f1?locale=en-US&state=PRODUCTION&version=Cloud), ATC configurations, abapGit, and the Cloud Connector — no grounded definition can be written for an "undefined" concept. Please provide a valid SAP developer concept name so an accurate, source-grounded definition can be produced.
- Concept SAP Cloud Connector Setup and Configuration The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as [Communication Systems](https://help.sap.com/docs/btp/sap-business-technology-platform/e695a4a640a9455f9a3e18675d7084d0?locale=en-US&state=PRODUCTION&version=Cloud), communication arrangements, and integration reference architectures — there is insufficient grounding to produce an accurate definition. Please provide a valid SAP developer concept name and relevant source snippets to generate a definition.
- Concept Communication Arrangement for Cloud Connector A **Communication Arrangement** is a configuration object in the ABAP environment of SAP Business Technology Platform that defines how an external system connects to and communicates with your system. Developers use it to set up integration scenarios by specifying a [communication scenario, system, and user](https://help.sap.com/docs/btp/sap-business-technology-platform/04488354490349f989871c5d555a2926?locale=en-US&state=PRODUCTION&version=Cloud), enabling both inbound and outbound connections. The [communication management apps](https://help.sap.com/docs/btp/sap-business-technology-platform/2e84a10c430645a88bdbfaaa23ac9ff7?locale=en-US&state=PRODUCTION&version=Cloud) allow developers to integrate their system with other systems, such as SAP Analytics Cloud, SAP Datasphere, or on-premise systems via Cloud Connector, as well as services like outbound email via SMTP.
- Concept Cloud Connector RFC Connection The concept name was not provided (marked as "undefined"), and the supplied source snippets do not contain enough shared, clearly scoped content to define a single coherent SAP developer concept. The sources cover a range of loosely related topics — Remote ATC, Communication Arrangements, and RFC connectivity — without a unifying concept name or description to anchor a definition. A valid concept name is required to produce an accurate, grounded definition.
- Concept RFC Connection from SAP BTP ABAP Environment to On-Premise System The concept name was not provided, so a precise definition cannot be generated. Please supply the concept name (for example, "RFC," "Custom Entity," or "SAP BTP ABAP Environment") so that a grounded, accurate definition can be written from the available sources.
- Concept Communication Arrangement in SAP BTP ABAP Environment The concept name is not defined in the provided sources, and the available source snippets do not contain sufficient shared context to identify and describe a single, specific SAP developer concept. A meaningful, source-grounded definition cannot be produced.
- Concept Communication Arrangement Management The provided sources do not contain enough grounded information to write a reliable 2–4 sentence definition for an **undefined** concept. Please supply a valid concept name and relevant source snippets so an accurate, source-grounded definition can be produced.
- Concept Cloud Connector for On-Premise System Integration The concept referenced here is **undefined** — no concept name or sufficient source content was provided to produce a grounded definition. Please supply a valid concept name and supporting source snippets so that an accurate, source-grounded definition can be written.