🏛️ SAP ATC Integration Guide

Skylint is an ATC-native static analysis engine. This guide explains how Skylint integrates into SAP's modern quality assurance infrastructure, why it exclusively targets ABAP Test Cockpit (ATC) instead of the legacy Code Inspector (SCI), and how to set up Check Variants and CI/CD pipelines.

---

🚫 Why ATC and NOT Classic SCI (Code Inspector)?

A critical design choice of Skylint is its exclusive adherence to SAP's modern ATC framework (IF_CI_ATC_CHECK).

The Technical & Architectural Differences

Dimension	Legacy Code Inspector (SCI)	Modern ABAP Test Cockpit (ATC)	Skylint Architecture
Base Interface	cl_ci_check_root	if_ci_atc_check	Extends zcl_skylint_check_base & implements if_ci_atc_check
ABAP Cloud Support	❌ Forbidden / Not Released	✅ 100% Released (Contract C1)	Native ABAP Cloud (Language Version 5)
Tooling & IDE	SAP GUI (Tx SCI, SCII)	Eclipse ADT (ABAP Development Tools)	Native Eclipse ADT integration
QuickFix Automation	❌ Not supported	✅ Native QuickFix API (cl_ci_atc_quickfixes)	One-click fixes via Ctrl + 1
Compiler Symbols	Raw text tokens without semantics	Full symbol resolution (compiler_references)	Type-safe AST traversal
Remote Checkability	Complex RFC scripts	RFC & HTTPS Remote Source Providers	Built-in remote enablement (is_remote_enabled = abap_true)

IMPORTANT: No Transaction SCI Support

Skylint check classes do not inherit from cl_ci_check_root. As a result, they will not appear in transaction SCI.

Trying to run Skylint via legacy SCI is neither supported nor possible in ABAP Cloud. All configuration and execution must be performed via Eclipse ADT or the system transaction ATC.

---

🛠️ Configuring Skylint in Eclipse ADT

In modern ABAP systems (SAP BTP ABAP Environment, S/4HANA Cloud, and S/4HANA 2022+), ATC Check Variants are ABAP repository objects created and maintained directly in Eclipse ADT.

Step 1: Create an ATC Check Variant in ADT

1. Open Eclipse ADT connected to your development or central check system.
2. In the Project Explorer, right-click your package (e.g., ZSKYLINT_CONFIG) and select:
   New → Other ABAP Repository Object...
3. In the search filter, type ATC Check Variant (Object Type: CHKV) and click Next.
4. Enter the details:
   • Name: e.g., ZCLEAN_ABAP or ZSKYLINT_DEFAULT
   • Description: Skylint Clean ABAP Quality Rules
5. Click Finish and assign a transport request.

---

Step 2: Add Skylint Checks to the Variant

1. The ATC Check Variant Editor opens in Eclipse.
2. In the Checks tab, click Add Check....
3. In the dialog, search for check classes using the prefix:

   ZCL_SKYLINT_*

4. Select all desired Skylint rules (or select all rules for complete Clean ABAP coverage).
5. For each rule, you can customize:
   • Default Severity: Error, Warning, or Note.
   • Check-Specific Parameters: For rules with configurable thresholds (such as MAX_METHOD_LENGTH or MAX_NESTING_DEPTH), configure the numeric bounds directly in the attribute pane.
6. Save and activate (Ctrl + F3) the ATC Check Variant.

---

Step 3: Set Default System-Wide ATC Variant (Optional)

To enforce Skylint checks across your development team during transport release or central check runs:

1. In SAP GUI, execute transaction ATC.
2. Navigate to ATC Administration → Configuration.
3. Under System Check Configuration, set the Default Check Variant to your newly created variant (e.g., ZCLEAN_ABAP).
4. Enable Check on Transport Release if you wish to block transport requests with priority 1 (Error) findings.

---

🏃 Running Checks in Eclipse ADT

Developers can execute Skylint checks on individual objects, entire packages, or whole software components:

1. Running on Current Editor

• Press Ctrl + Shift + F2 while editing any ABAP class or program.
• Or right-click in the editor → Run As → ABAP Test Cockpit.

2. Running on Entire Packages / Software Components

• In Project Explorer, right-click the target package or project → Run As → ABAP Test Cockpit With....
• Select your custom variant (ZCLEAN_ABAP).
• The ATC Result View displays all findings, grouped by rule, priority, and object.

---

💡 Using Automated QuickFixes (Ctrl + 1)

Skylint provides automated one-click QuickFixes for dozens of rules (e.g. prefer-lines, no-call-method, prefer-is-not, prefer-string-template).

1. In the ABAP source code editor, navigate to any line decorated with an ATC warning marker.
2. Press Ctrl + 1 (Quick Assist).
3. The popup displays the available Skylint fix (e.g., "Replace DESCRIBE TABLE with lines()").
4. Press Enter to apply the transformation.
5. Save and re-run ATC to verify the resolution.

---

🌐 Central & Remote ATC Scenarios

In enterprise landscapes with multiple development systems, SAP recommends a Central ATC Check System architecture.

Because Skylint check base classes set remote_enablement = abap_true and use framework data providers:

• You only need to install Skylint once on your Central ATC Hub (e.g., an SAP S/4HANA foundation system or SAP BTP ABAP Environment system).
• The central system can check remote target systems (even systems where Skylint is not installed) over standard RFC or HTTPS ATC communication scenarios.
• Developers working in satellite development systems receive findings in their local Eclipse ADT seamlessly.

---

🤖 CI/CD Pipeline Automation

Skylint integrates smoothly into modern DevOps pipelines:

1. Project "Piper" (SAP BTP ABAP Environment Pipeline)

If your organization uses Project Piper for ABAP CI/CD:

stage('ATC Static Analysis') {
    steps {
        abapEnvironmentRunATCCheck(
            script: this,
            atcConfig: [
                atcCheckVariant: 'ZCLEAN_ABAP',
                maxSeverity: 'warning'
            ]
        )
    }
}

2. Git-Enabled CTS (gCTS) Pre-Commit Checks

When using gCTS in ABAP Cloud, you can configure an ATC quality gate in the repository settings to automatically run the Skylint variant before any commit or push is accepted.