원클릭으로 Manus에서 모든 스킬 실행

sap-atc

스타6

포크1

업데이트2026년 7월 24일 12:35

Runs the SAP ABAP Test Cockpit (ATC) end-to-end as a quality gate: builds an SCI Object Set scoped to the target object(s), creates an ATC Run Series bound to that set, polls the ATC Run Monitor until the run completes, then reads the Priority 1 / Priority 2 / Priority 3 finding counts from the Manage Results screen and (best-effort) downloads the result text file. Applies the customer brief's MAX_PRIORITY threshold to decide pass / fail. Replaces the legacy SCI-results-tree implementation that lacked a Priority column. Per-stage VBS references are recorded against the S/4HANA 1909 ATC layout — re-record on first failure with /sap-gui-probe --record if your release uses different tree node IDs / grid column IDs. Prerequisites: Active SAP GUI session (use /sap-login first).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

sapdev-ai

sapdev-ai/sap-dev

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

SAP ATC Quality Gate Skill

You drive the proper SAP ATC pipeline — Object Set → Run Series → Run Monitor → Manage Results — and apply a priority-based gate. The four stages each have their own VBS reference; SKILL.md orchestrates them with a polling loop in the middle.

Task: $ARGUMENTS

Stage map

Stage 1: SCI       /nSCI       create / refresh Object Set "<SET>"
   |
   v
Stage 2: ATC       /nATC       tree node 12 → CREATE_SERIE bound to <SET>
   |                            → EXECUTE_SERIE → run is async
   v
Stage 3: ATC       /nATC       tree node 13 → poll Run Monitor for <RUN>
   |                            until STATE=COMPLETED (or FAILED)
   v
Stage 4: ATC       /nATC       tree node 14 → Manage Results: read
                                P1/P2/P3 counts; best-effort download
                                to <OUTPUT_PATH>
   |
   v
Gate logic in SKILL.md compares the counts to MAX_PRIORITY.
   |
   v
Stage 4b: ATC      /nATC       (optional) tree node 14 → drill into the
                                run-series row → export per-finding ALV
                                as TSV. Auto-triggered when gate FAILS;
                                always triggered by --drill. Outputs
                                <OUTPUT_PATH>.findings.tsv with one row
                                per finding: PRIO | CHECK_ID | CHECK_TITLE
                                | OBJ_NAME | OBJ_TYPE | MSG_TEXT | LINE.
   |
   v
Final PASS / FAIL emitted with the findings.tsv path when available.

Shared Resources

File	Stage	Purpose
`<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md`	—	Mandatory operating rules
`<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md`	—	GUI-scripting language independence — identify by component ID + DDIC field name, status-bar checks via `MessageType` codes (S/W/E/I/A), VKey instead of menu-text, no branching on `.Text`/`.Tooltip`/window titles
`<SAP_DEV_CORE_SHARED_DIR>/rules/sap_gui_security_handling.md`	4 / 4b	SAP GUI Security dialog handling — the Stage-4 result download and Stage-4b findings-TSV export are SAP-GUI-side file IO, so they can raise the modal "SAP GUI Security" dialog (which suspends the Scripting API and hangs cscript). Pre-check + OS-level watcher wrap both downloads.
`<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_gui_security_precheck.ps1`	4 / 4b	Read-only allow-list pre-check (`saprules.xml`) — `ALLOWED` (exit 0) / `NOT_COVERED` (exit 1).
`<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_gui_security_sidecar.ps1`	4 / 4b	OS-level (Win32) watcher that auto-dismisses the SAP GUI Security dialog (ticks Remember + clicks Allow). Launched as a background process before each download.
`<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_object_resolver.ps1`	2b	Pre-flight existence check of the target (CLI mode, 32-bit PowerShell; emits `STATUS: RESOLVED\|NOT_FOUND\|AMBIGUOUS\|UNKNOWN_TYPE\|RFC_ERROR`). `NOT_FOUND` aborts the skill with `ATC_EMPTY_SCOPE` before any scope is built.
`<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_artifact_lib.ps1`	6d	`New-SapScopeKey` / `Register-SapArtifact` — register the result TXT + findings TSV so `/sap-evidence-pack` collects them under the object's scope (Kind `atc_findings`). Best-effort; never changes the gate verdict.
`<SKILL_DIR>/references/sap_sci_create_object_set.vbs`	1	Define the scope — programs / classes / FMs / interfaces / FUGRs
`<SKILL_DIR>/references/sap_atc_create_run_series.vbs`	2	Schedule + trigger the ATC run
`<SKILL_DIR>/references/sap_atc_check_run_status.vbs`	3	Read run state from the Monitor (read-only; safe to call in a poll loop)
`<SKILL_DIR>/references/sap_atc_get_results.vbs`	4	Pull P1/P2/P3 counts + try to save the result TXT (outer grid only — summary level)
`<SKILL_DIR>/references/sap_atc_drill_findings.vbs`	4b	(Optional) Drill into the run-series row → export per-finding ALV as TSV. Run when gate FAILS or `--drill` is passed.
`<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_error_hints.ps1`	6c	frequently_errors recorder. `-Action record -Source ATC -FindingsFile <...>.findings.tsv` captures FM/METHOD-attributable findings to the team store as CANDIDATEs. Best-effort; never changes the gate verdict.

Step 0 — Resolve Work Directory

Resolve work_dir via the env-aware helper — do NOT take work_dir from a direct settings.json read (that ignores the SAPDEV_AI_WORK_DIR env var and userconfig.json). Use the WORK_DIR= value printed by:

powershell -NoProfile -ExecutionPolicy Bypass -Command ". '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_settings_lib.ps1'; . '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'; Write-Output ('WORK_DIR=' + (Get-SapWorkDir)); Write-Output ('RUN_TEMP=' + (Get-SapRunTemp))"

The settings note below still applies to the OTHER keys.

Settings reads/writes follow shared/rules/settings_lookup.md — merge per-key on the .value field (env var → settings.local.json → userconfig.json → settings.json); non-per-connection writes go to userconfig.json. {WORK_TEMP} = work_dir\temp.

cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}"

Set {RUN_TEMP} = the RUN_TEMP= value printed above — a fresh per-run scratch directory {work_dir}\temp\run_<id>, already created by Get-SapRunTemp. Resolve it once here and reuse the same value for the rest of this invocation; it isolates this run's generated wrappers / state / scratch files so concurrent runs (parallel sub-agents, multi-connection deploys) never collide. {WORK_TEMP} stays the base temp dir and is used ONLY for Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}' (the session-attach plumbing derives {work_dir}\runtime from its parent, so it must see the base path, not the run dir). Everything the skill writes itself goes under {RUN_TEMP}.

Step 0.5 — Start Logging

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_atc_run.json" -Skill sap-atc -ParamsJson "{\"object_type\":\"<TYPE>\",\"object_name\":\"<NAME>\"}"

Step 0a — Read MAX_PRIORITY from the Customer Brief

If the customer brief defines MAX_PRIORITY (typically 2 = block on critical + high), use it as the default gate threshold. Allow override via --max-priority=<n> on the skill argument list. Range: 1-4 (1=critical / 2=high / 3=medium / 4=low; lower = worse, fail-on-or-below).

If neither brief nor argument supplies a value, default to 2.

Step 1 — Parse Arguments

Arg	Required	Default	Notes
`OBJECT_TYPE`	yes*	—	One of `PROGRAM` / `CLASS` / `INTERFACE` / `FUGR` / `DDIC` / `TYPEGROUP` / `WDYN`. SCI groups Class and Interface under one category, so both map to `XSO_CLAS` + `SO_CLAS-LOW`. `FM` is intentionally rejected — SCI Object Sets have no per-function-module category; pass `FUGR <function-group-name>` instead to scope at FG level. *Not required when `--object-list` is supplied.
`OBJECT_NAME`	yes*	—	UPPERCASE repository name. *Not required when `--object-list` is supplied.
`--object-list=<file>`	no	—	Batch mode (A5). Path to a file of `<OBJECT_TYPE> <OBJECT_NAME>` lines (whitespace/tab separated; blank + `#`-comment lines ignored). ALL objects go into one SCI Object Set → one ATC run → one result set, keyed per object by the Stage-4b drill's `OBJ_NAME` column. Mutually exclusive with the positional `OBJECT_TYPE`/`OBJECT_NAME`. Objects are grouped by SCI category, so a list may mix PROGRAM/CLASS/FUGR/DDIC/… freely. Cuts a 1000-object estate's analyze phase from one-run-per-object to one-run-per-batch — see `/sap-cc-analyze --batch-size`. When set, `--drill` is implied (per-object attribution needs the drill TSV) and the empty-scope gate is applied per resolved object (Step 2b).
`--variant=<NAME>`	no	(empty = system default)	Global ATC check variant to run, e.g. `S4HANA_READINESS` for an S/4HANA-conversion readiness check. When omitted, the run series leaves the check-variant field untouched and ATC runs the system's configured default variant (the prior behaviour). Passing a named variant is mandatory for migration readiness — see `/sap-cc-analyze`, which calls this skill with `--variant=S4HANA_READINESS`. The named variant must EXIST and be GLOBAL on the connected system (readiness needs the Simplification Database loaded). Accepts `--check-variant=<NAME>` as an alias.
`--object-provider=<ID>`	no	(empty = LOCAL)	Central / remote ATC. Binds the run series to a registered remote object provider (`DATA_SOURCE_ID`) so a central hub analyzes a remote satellite's code. Requires the hub to be configured (tx ATC → Manage System Groupings + an SM59 RFC destination to the satellite, hub check content ≥ the satellite's target release). When omitted, the run is LOCAL. When supplied but the provider field isn't on the config screen, Stage 2 fails loud (never silently runs local-as-remote). The provider field id is UNVERIFIED — no configured hub was available to record against; see "Central / remote ATC" below.
`--max-priority=<n>`	no	`2` (or brief)	Gate threshold — fail if any priority ≤ this value has count > 0.
`--object-set=<NAME>`	no	auto	Reuse a named SCI Object Set. If omitted, generate `ZGATE_<8-char-hash-of-objname>` so re-runs on the same target reuse the same set.
`--run-series=<NAME>`	no	auto	Run Series name. If omitted, generate `RUN_<YYYYMMDD>_<HHMMSS>` to avoid collisions.
`--poll-interval=<sec>`	no	`15`	Stage 3 polling cadence.
`--max-wait=<sec>`	no	`600` (10 min)	Stage 3 timeout.
`--save-to=<PATH>`	no	`{RUN_TEMP}\ATC_<series>.txt`	Local path for the downloaded result TXT.
`--drill`	no	(off by default; auto when gate FAILS)	Force Stage 4b — drill into the run-series row and export per-finding ALV as TSV to `<save-to>.findings.tsv`. Use to see WHICH findings exist even when the gate passes (e.g. inspecting P3 informational findings).
`--no-drill`	no	(off)	Disable Stage 4b even when the gate FAILS. Useful for CI runs where the operator only needs PASS/FAIL counts and will drill manually if needed.

Naming generation (when not supplied):

Object set: ZGATE_ + first 8 hex chars of an MD5 of <OBJECT_TYPE>:<OBJECT_NAME> (single mode), or of the newline-joined, upper-cased, sorted <TYPE> <NAME> lines of the --object-list file (batch mode — stable for the same batch content regardless of line order). Stable across runs of the same target/batch. Max length budget: SCI accepts up to 30 chars on SCI_DYNP-OBJS; we use 14. Callers that manage their own set lifecycle (e.g. /sap-cc-analyze --batch-size names each batch ZCC_<campaign>_B<nnn>) pass --object-set=<NAME> explicitly.
Run series: R_ + Get-Date -Format "yyMMdd_HHmmss" → R_260509_195347 (16 chars). The ATC popup field ctxtSATC_CI_S_CFG_SERIE_UI_02-NAME has MaxLength = 16 on S/4HANA 1909 — verified live; the older RUN_<YYYYMMDD>_<HHMMSS> form (19 chars) fails with "method got an invalid argument". The shorter form is unique to the second across 100 years.

Step 2 — Ensure SAP GUI Session

Run /sap-login first if no session is active.

Step 2b — Pre-flight: Resolve the Target Object (empty-scope guard)

A typo'd / nonexistent OBJECT_NAME produces an EMPTY object set — the ATC run then COMPLETES with P1=P2=P3=0 and would false-PASS the gate. Resolve the target via the shared object resolver BEFORE building any scope. CLI mode, 32-bit PowerShell (SAP NCo is 32-bit); creds fall back to the pinned connection profile, so -Token alone works on a logged-in session:

C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_object_resolver.ps1" -Token "<KIND> <OBJECT_NAME>"

<KIND> mapping from OBJECT_TYPE: PROGRAM→PROGRAM, CLASS→CLASS, INTERFACE→INTERFACE, FUGR→FUGR, TYPEGROUP→TYPEGROUP. For DDIC / WDYN the resolver has no kind mapping — skip this pre-flight with a WARN: existence unverified (no resolver mapping for <TYPE>) and rely on the Stage-4 empty-scope gate (Step 6) instead.

Read the STATUS: line of the output:

STATUS: RESOLVED → proceed to Stage 1. Remember this for the Stage-4 gate.
STATUS: NOT_FOUND → ABORT the skill — do not create the object set or the run series. Report ERROR: ATC_EMPTY_SCOPE - <TYPE> <NAME> does not exist on the connected system; an ATC run on a nonexistent object completes with 0/0/0 findings and would false-PASS the gate. Log-end with -Status FAILED -ExitCode 1 -ErrorClass ATC_EMPTY_SCOPE.
STATUS: RFC_ERROR (or the resolver cannot run at all — no NCo, RFC-off host) → emit WARN: object existence UNVERIFIED (resolver: <status>) and continue; the Stage-4 gate then must NOT accept a 0/0/0 result as PASS without the manual checked-object count (Step 6).
STATUS: AMBIGUOUS / UNKNOWN_TYPE → surface the resolver output and ask the operator before proceeding.

Batch mode (--object-list). Resolve EACH line's object the same way (-Token "<KIND> <NAME>"). Drop any NOT_FOUND object from the list with a WARN: dropped <TYPE> <NAME> (NOT_FOUND) and rewrite the object-list file to the surviving objects before Stage 1 (an empty object silently sinks the whole batch's counts). If every object resolves NOT_FOUND, ABORT with ERROR: ATC_EMPTY_SCOPE. If the resolver cannot run (RFC_ERROR/no NCo), emit WARN: batch existence UNVERIFIED and proceed with the full list (the Stage-4 plan-error + object-count checks remain the backstop). Remember the surviving count for the Stage-4 gate.

Step 3 — Stage 1: Create Object Set (SCI)

Fill sap_sci_create_object_set.vbs and run it. Tokens: %%OBJECT_SET_NAME%%, %%OBJECT_TYPE%%, %%OBJECT_NAME%%, %%OBJECT_LIST_FILE%%, %%SESSION_LOCK_VBS%%.

Single vs batch mode. The VBS decides by whether %%OBJECT_LIST_FILE%% is non-empty: single-object mode fills %%OBJECT_TYPE%%/%%OBJECT_NAME%% straight into the category's LOW field (the verified pre-A5 path, byte-identical); batch mode reads the list file, groups objects by SCI category, and drives the select-options Multiple Selection dialog per category (row-by-row fill, scrolling the tblSAPLALDBSINGLE table past its 8-row window, Copy=F8). In batch mode leave %%OBJECT_TYPE%%/%%OBJECT_NAME%% empty and substitute %%OBJECT_LIST_FILE%% with the (post-Step-2b) list path; in single mode leave %%OBJECT_LIST_FILE%% empty.

# IMPORTANT: read with explicit UTF-8 and write with UTF-16 LE (BOM).
# The VBS templates contain Japanese/Chinese tooltip stems for
# locale-independent state decoding (see sap_atc_check_run_status.vbs).
# `Get-Content -Raw` reads via the Windows ANSI codepage and silently
# mangles those high-byte characters into garbage that VBScript then
# refuses to compile ("unterminated string literal"). Likewise
# `Set-Content -Encoding Unicode` was observed to double-encode in
# some PowerShell versions. Use System.IO.File directly.
$skillDir = '<SKILL_DIR>'
$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$content  = [System.IO.File]::ReadAllText("$skillDir\references\sap_sci_create_object_set.vbs", [System.Text.Encoding]::UTF8)
$content  = $content.Replace('%%OBJECT_SET_NAME%%','THE_OBJECT_SET')
$content  = $content.Replace('%%OBJECT_TYPE%%',    'THE_OBJECT_TYPE')     # empty in batch mode
$content  = $content.Replace('%%OBJECT_NAME%%',    'THE_OBJECT_NAME')     # empty in batch mode
# Batch mode (A5): absolute path to the <TYPE> <NAME> object-list file, else empty.
$content  = $content.Replace('%%OBJECT_LIST_FILE%%','THE_OBJECT_LIST_FILE')
$content  = $content.Replace('%%SESSION_LOCK_VBS%%',"$shared\scripts\sap_session_lock.vbs")
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content  = $content.Replace('%%SESSION_PATH%%',   $sessionPath)
$content  = $content.Replace('%%ATTACH_LIB_VBS%%', "$shared\scripts\sap_attach_lib.vbs")
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_atc_stage1_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))

Stages 2-4 use the same I/O pattern. Always [System.IO.File]::ReadAllText(..., UTF8) + [System.IO.File]::WriteAllText(..., UnicodeEncoding). Never Get-Content -Raw + Set-Content -Encoding Unicode for these files — any localized string in the template will be silently corrupted. Explicit generator blocks for each stage are spelled out below (Steps 4, 5, 6) so each stage is self-contained.

Run via 32-bit cscript (bare cscript resolves to the 64-bit host, which cannot bind the SAP GUI Scripting COM objects):

C:/Windows/SysWOW64/cscript.exe //NoLogo {RUN_TEMP}\sap_atc_stage1_run.vbs

Expected last line: SUCCESS: Object set <NAME> created/updated with <TYPE> <NAME>.

If it fails with "Object set already exists" or similar, that's fine for our reuse model — proceed to Stage 2 with the same name. If it fails with a missing-field-id error, the SCI screen layout shifted; re-record via /sap-gui-probe --record.

Step 4 — Stage 2: Create + Execute Run Series (ATC)

Fill sap_atc_create_run_series.vbs. Tokens: %%RUN_SERIES_NAME%%, %%OBJECT_SET_NAME%%, %%CHECK_VARIANT%%, %%OBJECT_PROVIDER%%, %%SESSION_LOCK_VBS%%.

Substitute %%CHECK_VARIANT%% with the parsed --variant= value, or the empty string when no variant was supplied (the empty value is what tells the VBS to leave the check-variant field untouched and run the system default — the prior behaviour). When a variant IS requested but the VBS cannot locate the check-variant input field on the connected release, Stage 2 fails loud (ERROR: --variant=… requested but the run-series check-variant input field could not be located) rather than silently running the default variant — a silent fallback would misreport non-readiness findings as readiness. If you hit that error, re-record the ATC run-series config screen via /sap-gui-probe (or /sap-gui-probe --record) and add the real field id to the chkvCands list in sap_atc_create_run_series.vbs.

$skillDir = '<SKILL_DIR>'
$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$content  = [System.IO.File]::ReadAllText("$skillDir\references\sap_atc_create_run_series.vbs", [System.Text.Encoding]::UTF8)
$content  = $content.Replace('%%RUN_SERIES_NAME%%', 'THE_RUN_SERIES')
$content  = $content.Replace('%%OBJECT_SET_NAME%%', 'THE_OBJECT_SET')
# Empty string = run the system default variant (prior behaviour).
$content  = $content.Replace('%%CHECK_VARIANT%%',   'THE_CHECK_VARIANT')
# Empty string = LOCAL analysis; a value = remote object provider (central ATC).
$content  = $content.Replace('%%OBJECT_PROVIDER%%', 'THE_OBJECT_PROVIDER')
$content  = $content.Replace('%%SESSION_LOCK_VBS%%', "$shared\scripts\sap_session_lock.vbs")
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content  = $content.Replace('%%SESSION_PATH%%',   $sessionPath)
$content  = $content.Replace('%%ATTACH_LIB_VBS%%', "$shared\scripts\sap_attach_lib.vbs")
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_atc_stage2_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))

Run via 32-bit cscript:

C:/Windows/SysWOW64/cscript.exe //NoLogo {RUN_TEMP}\sap_atc_stage2_run.vbs

Expected lines: VARIANT: <S4HANA_READINESS | SYSTEM_DEFAULT> (which variant the run will use) PROVIDER: <provider-id | LOCAL> (LOCAL = this system's own code; an id = central/remote) SUCCESS: Run series <NAME> scheduled (object set <SET>, variant <ID>, provider <P>).

If Stage 2 instead ends with ERROR: RUN_SERIES_NOT_FOUND ... (exit 1), the freshly-saved series could not be matched on the node-12 grid and nothing was executed (the old last-row fallback that could fire someone else's series is removed). Re-record the grid per the error text; do not retry blindly.

Confirm the VARIANT: line reports the variant you intended — if you passed --variant=S4HANA_READINESS but it reads SYSTEM_DEFAULT, the token was not substituted (treat as a bug, not a clean run).

Local-object runs (no object provider). When the target is a LOCAL / $TMP object (or any run with no remote object provider), Save raises an informational confirmation popup — the SAPLSPO1 "Save inconsistent data / local objects will be checked" modal. Stage 2 detects it by its DDIC control id (wnd[1]/usr/btnBUTTON_1 — the Yes button; locale-independent, never by title; btnSPOP-BUTTON_1 is tried as a release-variance fallback) and confirms-and-continues (presses Yes) so EXECUTE_SERIE still fires. This is the normal path for a local Z-program ATC run; it is not an error. A different unhandled post-Save modal (one with no such Yes control — e.g. a Local-only SCI Object Set that can't bind to a Run Series) still aborts loud. (Field fix, S/4HANA 1909, 2026-06-26 — the popup previously aborted every local-object run before EXECUTE_SERIE. Control id btnBUTTON_1 verified live by dumping the dialog's control tree.)

After this point the ATC run is async — SAP queues the work and executes it in the background. Stage 3 polls.

Step 5 — Stage 3: Poll Run Status

Generate the Stage 3 VBS once (it's reused inside the poll loop):

$skillDir = '<SKILL_DIR>'
$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$content  = [System.IO.File]::ReadAllText("$skillDir\references\sap_atc_check_run_status.vbs", [System.Text.Encoding]::UTF8)
$content  = $content.Replace('%%RUN_SERIES_NAME%%', 'THE_RUN_SERIES')
$content  = $content.Replace('%%SESSION_LOCK_VBS%%', "$shared\scripts\sap_session_lock.vbs")
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content  = $content.Replace('%%SESSION_PATH%%',   $sessionPath)
$content  = $content.Replace('%%ATTACH_LIB_VBS%%', "$shared\scripts\sap_attach_lib.vbs")
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_atc_stage3_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))

Then loop:

Run {RUN_TEMP}\sap_atc_stage3_run.vbs via 32-bit cscript (C:/Windows/SysWOW64/cscript.exe //NoLogo — never bare cscript, which resolves to the 64-bit host and cannot bind the SAP GUI COM objects).
Parse the last line:
- STATE=COMPLETED → break, proceed to Stage 4.
- STATE=RUNNING → wait --poll-interval seconds, retry.
- STATE=FAILED → abort with ERROR: ATC run <NAME> failed.
- STATE=NOT_FOUND → wait one cycle (the Monitor may not have picked up the freshly-scheduled run yet), then retry; if still NOT_FOUND after 3 cycles, abort.
- STATE=UNKNOWN:<raw> → log and retry once; if it persists, fall back to "treat as RUNNING" until --max-wait elapses.

Hard cap at --max-wait seconds (default 600). On timeout, ABORT with ERROR: ATC_POLL_TIMEOUT - ATC run <NAME> did not complete within <N>s and log-end -Status FAILED -ExitCode 1 -ErrorClass ATC_POLL_TIMEOUT. Never fall through to Stage 4 — reading Manage Results for an unfinished run yields bogus 0/0/0 counts.

Implementation hint for the orchestrator (PowerShell):

$pollInterval = 15
$maxWait      = 600
$elapsed      = 0
$notFound     = 0
while ($true) {
  $out = & 'C:/Windows/SysWOW64/cscript.exe' //NoLogo '{RUN_TEMP}\sap_atc_stage3_run.vbs'
  # $out is an ARRAY of lines; -match against an array never fills $Matches.
  # Regex each single line and keep the last STATE= hit.
  $state = ''
  foreach ($line in @($out)) {
    if ($line -match '^STATE=(.+)$') { $state = $Matches[1].Trim() }
  }
  if ($state -eq 'COMPLETED') { break }
  if ($state -eq 'FAILED')    { throw 'ERROR: ATC run failed (STATE=FAILED)' }
  if ($state -eq 'NOT_FOUND') {
    $notFound++
    if ($notFound -ge 3) { throw "ERROR: run series not visible in the Run Monitor after $notFound polls" }
  } else { $notFound = 0 }
  if ($elapsed -ge $maxWait) {
    throw "ERROR: ATC_POLL_TIMEOUT - not COMPLETED after ${maxWait}s (last STATE=$state); do NOT proceed to Stage 4"
  }
  Start-Sleep -Seconds $pollInterval
  $elapsed += $pollInterval
}
Write-Output "STATE=COMPLETED after ${elapsed}s"

The throws abort the block with a non-zero exit — treat any of them as a hard stop for the whole skill (log-end ATC_POLL_TIMEOUT on the timeout path, ATC_RUN_SCHEDULE_FAILED when the run never appeared); Stage 4 runs ONLY after the STATE=COMPLETED line.

Don't echo the polling output to chat each iteration — that's noisy. Suppress and only show on state-change or timeout.

Step 6 — Stage 4: Read Results + Apply Gate

Fill sap_atc_get_results.vbs. Tokens: %%RUN_SERIES_NAME%%, %%OUTPUT_PATH%%, %%SESSION_LOCK_VBS%%.

$skillDir = '<SKILL_DIR>'
$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$content  = [System.IO.File]::ReadAllText("$skillDir\references\sap_atc_get_results.vbs", [System.Text.Encoding]::UTF8)
$content  = $content.Replace('%%RUN_SERIES_NAME%%', 'THE_RUN_SERIES')
$content  = $content.Replace('%%OUTPUT_PATH%%',    'THE_OUTPUT_PATH')
$content  = $content.Replace('%%SESSION_LOCK_VBS%%', "$shared\scripts\sap_session_lock.vbs")
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content  = $content.Replace('%%SESSION_PATH%%',   $sessionPath)
$content  = $content.Replace('%%ATTACH_LIB_VBS%%', "$shared\scripts\sap_attach_lib.vbs")
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_atc_stage4_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))

Run the Stage-4 VBS with the SAP GUI Security guard. The result-file download is SAP-GUI-side file IO, so it can raise the modal SAP GUI Security dialog — which suspends the Scripting API and hangs cscript. Per shared/rules/sap_gui_security_handling.md, pre-check the allow-list and run the OS-level watcher around the download (the watcher ticks Remember + clicks Allow). The Manage-Results dynpro (SATC_CI_RESULT_ADMIN_UI) is stable, so one Remember rule covers future runs. Run as one PowerShell block (substitute THE_OUTPUT_PATH with the same --save-to path the generator wrote into the VBS):

$shared = '<SAP_DEV_CORE_SHARED_DIR>\scripts'
$out    = 'THE_OUTPUT_PATH'   # the path SAP GUI will write the result TXT into
# 1. Pre-check the allow-list (read-only; informational + lets us skip the watcher).
& "$shared\sap_gui_security_precheck.ps1" -Path $out -Access w | Out-Host
$allowed = ($LASTEXITCODE -eq 0)
# 2. If NOT already allow-listed, launch the OS-level watcher BEFORE the (blocking)
#    download. It finds the #32770 dialog, ticks Remember + clicks Allow, and
#    persists a rule so subsequent runs pre-check ALLOWED.
$watcher = $null
if (-not $allowed) {
    $watcher = Start-Process powershell -PassThru -WindowStyle Hidden -ArgumentList @(
        '-NoProfile','-ExecutionPolicy','Bypass','-File',"$shared\sap_gui_security_sidecar.ps1",'-TimeoutSeconds','40')
    Start-Sleep -Milliseconds 800
}
# 3. Run the results read + download (32-bit cscript). If the dialog appears it
#    blocks here until the watcher dismisses it; then the download completes.
& 'C:/Windows/SysWOW64/cscript.exe' //NoLogo '{RUN_TEMP}\sap_atc_stage4_run.vbs'
# 4. Reap the watcher.
if ($watcher) { $watcher | Wait-Process -Timeout 45 -ErrorAction SilentlyContinue }

Parse the output for these lines:

PRIORITY_COUNTS: P1=<n> P2=<n> P3=<n>
COUNT_PLNERR=<n|NA>                ← planning-error count from the result row (NA = column unreadable)
FILE: <path> (<size> bytes)        ← only on successful auto-download
SAVE_HINT: <diagnostic>            ← only when auto-download skipped
SUCCESS: Read result for run series <NAME>.

Parse failure is a FAIL, not 0/0/0. When the Priority columns cannot be read, the VBS exits 1 with ERROR: ATC_RESULT_PARSE_FAILED - priority columns not found (release/locale layout drift; re-record per SKILL.md). Report the gate as FAIL and log-end -ErrorClass ATC_RESULT_PARSE_FAILED — never treat unparsed counts as 0/0/0.

Fail-loud pre-checks (apply BEFORE the priority table):

COUNT_PLNERR > 0 → FAIL with ERROR: ATC_PLAN_ERRORS - <n> object(s) could not be planned/checked; the finding counts are not trustworthy (log-end -ErrorClass ATC_PLAN_ERRORS). Never PASS, regardless of P1/P2/P3.
P1=0 P2=0 P3=0 is only a PASS when the run demonstrably checked >= 1 object. Evidence, in order of preference:
- Step 2b resolved the target (STATUS: RESOLVED) and COUNT_PLNERR=0 → accept the 0/0/0 as a genuinely clean PASS.
- otherwise (COUNT_PLNERR=NA, or Step 2b was skipped/UNVERIFIED — DDIC/ WDYN target, RFC-off host) → read the checked-object count manually: open ATC > Manage Results, drill into the series row; the result display header lists the objects checked. Only a count >= 1 makes the 0/0/0 a PASS. 0 findings with 0 objects checked → FAIL with ERROR: ATC_EMPTY_SCOPE (log-end -ErrorClass ATC_EMPTY_SCOPE).

Gate logic:

MAX_PRIORITY	Pass condition
`1`	`P1 == 0` (any critical finding fails)
`2` (default)	`P1 == 0 AND P2 == 0`
`3`	`P1 == 0 AND P2 == 0 AND P3 == 0`
`4`	report findings but never fail (informational)

Emit a final verdict line in your reply:

GATE_VERDICT: PASS  P1=0 P2=0 P3=18 (threshold=2 → P3 doesn't block)
GATE_VERDICT: FAIL  P1=3 P2=2 P3=14 (threshold=2 → P1+P2 sum 5 blocks)

Step 6b — Stage 4b: Drill Into Per-Finding Detail (conditional)

The aggregated P1/P2/P3 counts from Stage 4 tell the operator THAT the gate failed but not WHY. The findings ALV (check ID, source line, message text — one row per finding) lives one screen deeper, behind a doubleClick on the run-series row. Stage 4b drills there and exports the grid as TSV.

Trigger conditions (run Stage 4b when ANY is true):

--drill was passed on the command line.
Gate verdict is FAIL AND --no-drill was NOT passed.

Otherwise skip Stage 4b.

6b.1 — Fill and run sap_atc_drill_findings.vbs

Compute output path:

DRILL_PATH = <save-to>.findings.tsv
            (i.e. same dir + filename as --save-to but with .findings.tsv suffix)

Token-replace and run the same way as Stage 4 (UTF-8 read + UTF-16 LE write):

$skillDir = '<SKILL_DIR>'
$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$content  = [System.IO.File]::ReadAllText("$skillDir\references\sap_atc_drill_findings.vbs", [System.Text.Encoding]::UTF8)
$content  = $content.Replace('%%RUN_SERIES_NAME%%', 'THE_RUN_SERIES')
$content  = $content.Replace('%%OUTPUT_PATH%%',    'THE_DRILL_PATH')
$content  = $content.Replace('%%SESSION_LOCK_VBS%%',"$shared\scripts\sap_session_lock.vbs")
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content  = $content.Replace('%%SESSION_PATH%%',   $sessionPath)
$content  = $content.Replace('%%ATTACH_LIB_VBS%%', "$shared\scripts\sap_attach_lib.vbs")
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_atc_stage4b_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))

Run with the SAP GUI Security guard — the findings-TSV export is SAP-GUI-side file IO, same modal risk as Stage 4:

$shared = '<SAP_DEV_CORE_SHARED_DIR>\scripts'
$out    = 'THE_DRILL_PATH'   # the findings TSV SAP GUI will write
& "$shared\sap_gui_security_precheck.ps1" -Path $out -Access w | Out-Host
$allowed = ($LASTEXITCODE -eq 0)
$watcher = $null
if (-not $allowed) {
    $watcher = Start-Process powershell -PassThru -WindowStyle Hidden -ArgumentList @(
        '-NoProfile','-ExecutionPolicy','Bypass','-File',"$shared\sap_gui_security_sidecar.ps1",'-TimeoutSeconds','40')
    Start-Sleep -Milliseconds 800
}
& 'C:/Windows/SysWOW64/cscript.exe' //NoLogo '{RUN_TEMP}\sap_atc_stage4b_run.vbs'
if ($watcher) { $watcher | Wait-Process -Timeout 45 -ErrorAction SilentlyContinue }

Expected output lines:

INFO: Outer row <N> for series <NAME> — drilling in.
INFO: Findings grid located at <path>
FINDING_COUNT: <n>
FILE: <DRILL_PATH> (<size> bytes)
SUCCESS: Drilled findings for run series <NAME>.

6b.2 — Interpret + report

The findings TSV has the header row (matches colHeaders in sap_atc_drill_findings.vbs; LINE is blank on S/4HANA 1909 — the outer findings grid has no line-number column there):

PRIO	CHECK_ID	CHECK_TITLE	OBJ_NAME	OBJ_TYPE	MSG_TEXT	LINE

When the gate FAILED, parse this TSV and surface the offending findings (PRIO <= MAX_PRIORITY) in the final reply — one bullet per row with file:line and message text. Don't dump the whole TSV inline if it's long; quote the top 5 by priority and point the operator at the TSV path for the rest.

When the gate PASSED but --drill forced Stage 4b, mention the file path so the operator can review informational findings if interested.

6b.3 — Failure handling

If Stage 4b errors out (e.g. drill couldn't locate the findings grid because the screen 201 layout shifted on a newer SAP_BASIS release):

Do NOT fail the overall skill — the gate verdict from Stage 4 already determined PASS/FAIL.
Emit a warning line: WARN: Stage 4b drill failed — operator must inspect findings manually via /nATC > Manage Results > <series>.
Suggest re-recording via /sap-gui-probe --record against the result-display screen, then updating the findingPaths fallback list in sap_atc_drill_findings.vbs.

6c — Record FM/METHOD findings to frequently_errors (best-effort)

When Stage 4b produced a <save-to>.findings.tsv, feed it to the team frequently_errors store. The recorder keeps only findings it can attribute to a specific FM or class METHOD (by matching a known object token in the finding's MSG_TEXT / CHECK_TITLE / CHECK_ID, or — when the deployed source path is supplied and the finding carries a LINE — the enclosing call). Program-level findings with no FM/method are skipped (they are not what this store is for). Attributed findings upsert as CANDIDATE rows under {custom_url}\frequently_errors\<OBJECT>.tsv (TEAM-SHARED, not a MEMORY file) with SEVERITY=ATC_P<n> and ERROR_CLASS=ATC_<CHECK_ID>.

Best-effort — never changes the gate verdict. Skip when frequently_errors_enabled / frequently_errors_autorecord is false, or when Stage 4b did not run.

powershell -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_error_hints.ps1" -Action record -Source ATC -CustomUrl "{custom_url}" -FindingsFile "<save-to>.findings.tsv" -SourceFile "<DEPLOYED_ABAP_PATH-if-known>" -Program "<OBJECT_NAME>"

-SourceFile is optional but improves attribution when the source the run checked is on disk (e.g. straight after /sap-gen-abap + deploy). Report STATUS: RECORDED added=<n> updated=<n> skipped=<n> as an INFO note.

Step 6d — Register Artifacts for `/sap-evidence-pack` (best-effort)

Register the ATC outputs into the artifact index so /sap-evidence-pack collects them by scope / ticket / date without scraping the filesystem — otherwise the audit pack permanently reports atc_findings as missing evidence. Register the result TXT (Stage 4 --save-to) and, when Stage 4b ran, the findings TSV (<save-to>.findings.tsv), both under Kind atc_findings (the name /sap-evidence-pack expects — see its -Expected list). Best-effort: wrap in try/catch and NEVER change the gate verdict if registration fails (mirrors /sap-review-abap Step 6).

Run as one PowerShell block (pure file I/O — no SAP/RFC). Substitute {TADIR_OBJ} = the TADIR object code for OBJECT_TYPE (PROGRAM→PROG, CLASS→CLAS, INTERFACE→INTF, FUGR→FUGR, TYPEGROUP→TYPE, DDIC/WDYN→`` empty), {OBJECT_NAME}, the gate {VERDICT} (PASS/FAIL from the GATE_VERDICT: line), the {RESULT_TXT} (Stage-4 --save-to) path, the {FINDINGS_TSV} path (or empty when Stage 4b did not run), and {TICKET} (empty unless the operator supplied one):

$shared = '<SAP_DEV_CORE_SHARED_DIR>\scripts'
try {
  . "$shared\sap_artifact_lib.ps1"
  $obj   = [pscustomobject]@{ pgmid = 'R3TR'; object = '{TADIR_OBJ}'; obj_name = '{OBJECT_NAME}' }
  # Scope key (falls back to a plain slug if the object code is empty, e.g. DDIC).
  $scope = if ('{TADIR_OBJ}') { New-SapScopeKey -Resolved $obj } else { "OBJ_{OBJECT_NAME}" }
  $verdict = if ('{VERDICT}' -eq 'PASS') { 'GO' } elseif ('{VERDICT}' -eq 'FAIL') { 'NO_GO' } else { '' }
  if (Test-Path -LiteralPath '{RESULT_TXT}') {
    Register-SapArtifact -Skill 'sap-atc' -ScopeKey $scope -Kind 'atc_findings' -Format 'txt' `
        -Path '{RESULT_TXT}' -Object $obj -Verdict $verdict -Ticket '{TICKET}' | Out-Null
  }
  if ('{FINDINGS_TSV}' -and (Test-Path -LiteralPath '{FINDINGS_TSV}')) {
    Register-SapArtifact -Skill 'sap-atc' -ScopeKey $scope -Kind 'atc_findings' -Format 'tsv' `
        -Path '{FINDINGS_TSV}' -Object $obj -Verdict $verdict -Ticket '{TICKET}' | Out-Null
  }
  Write-Output "ARTIFACTS: registered scope=$scope"
} catch { Write-Output "WARN: artifact registration skipped ($($_.Exception.Message))" }

Step 7 — Report

For the operator's final reply, summarise:

Object set used (auto-generated or supplied)
Run series name
Total wall time (from Stage 2 schedule to Stage 4 read)

Priority counts table:

Priority 1 (critical) :  3
Priority 2 (high)     :  2
Priority 3 (medium)   : 14

Gate verdict (PASS / FAIL) and which counts contributed to the FAIL
Local result-file path if the auto-download succeeded; otherwise the SAVE_HINT message and the manual-download instructions
Per-finding TSV path (<save-to>.findings.tsv) when Stage 4b ran, with a 1-line preview: Findings: N (top: P<n> <check> @<obj>:<line>)
For FAILED gates, list the offending findings (PRIO <= MAX_PRIORITY) inline — quote the top 5 by priority, point at the TSV for the rest

If the operator wants the full finding list, point them at the saved TXT, the findings TSV (when Stage 4b ran), or the still-open ATC > Manage Results > screen.

Step 8 — Clean Up

cmd /c del {RUN_TEMP}\sap_atc_stage1_run.vbs & del {RUN_TEMP}\sap_atc_stage2_run.vbs & del {RUN_TEMP}\sap_atc_stage3_run.vbs & del {RUN_TEMP}\sap_atc_stage4_run.vbs & del {RUN_TEMP}\sap_atc_stage4b_run.vbs

Keep the downloaded result TXT (--save-to) and, when Stage 4b ran, the findings TSV (<save-to>.findings.tsv) — both are operator artefacts.

Final — Log End

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action end -StateFile "{RUN_TEMP}\sap_atc_run.json" -Status SUCCESS -ExitCode 0 -MetricsJson '{"gate":"ATC","verdict":"PASS","p1":0,"p2":0,"p3":0}'

For gate FAIL, set -Status FAILED -ExitCode 1 -ErrorClass ATC_GATE_FAIL and put the P1/P2/P3 counts in -ErrorMsg.

Build-KPI enrichment (best-effort). Include -MetricsJson on BOTH the PASS and FAIL end paths, populated from the GATE_VERDICT: line: verdict is PASS or FAIL (the gate verdict, independent of the run -Status), and p1/p2/p3 are the priority counts. The offline aggregator (shared/rules/build_metrics.md) reads it for the atc_first_pass_pct KPI. Best-effort: if you cannot read the counts, omit -MetricsJson — the run still logs and the KPI degrades to n/a, never a wrong value.

For other failure modes:

-ErrorClass ATC_EMPTY_SCOPE (Step 2b pre-flight NOT_FOUND, or a 0/0/0 result with 0 objects checked)
-ErrorClass ATC_OBJ_SET_FAILED (Stage 1 broke)
-ErrorClass ATC_RUN_SCHEDULE_FAILED (Stage 2 broke, incl. RUN_SERIES_NOT_FOUND)
-ErrorClass ATC_POLL_TIMEOUT (Stage 3 ran out of wait time — the Step-5 loop aborts; Stage 4 never runs)
-ErrorClass ATC_RESULT_PARSE_FAILED (Stage 4 couldn't read the Priority counts — the VBS exits 1; never reported as 0/0/0)
-ErrorClass ATC_PLAN_ERRORS (COUNT_PLNERR > 0 — finding counts untrustworthy)

Component IDs (verified S/4HANA 1909, recorded reference)

ATC tree nodes (left pane of /nATC):

Node ID	Function
`12`	Schedule / Manage Run Series (Stage 2 entry)
`13`	Run Monitor (Stage 3 entry)
`14`	Manage Results (Stage 4 entry)

The string format " 12" (10 leading spaces + node ID) is how SAP GUI scripting addresses ATC tree nodes. Different ATC roles / versions may renumber these — re-record if Stage 2/3/4 fails to navigate.

Run Monitor grid (Stage 3, tree node 13) — column IDs verified live on S/4HANA 1909:

Column ID	What it shows
`APP_CONFIG_NAME`	Run Series name (the value Stage 2 supplied)
`STATE_ICON`	Icon-encoded state, e.g. `@DF\QState: Finished@`
`TITLE`, `RESTARTS`, `DURATION`, `STARTED_ON_DATE`, `STARTED_ON_TIME`, `VALID_TO_DATE`, `STARTED_BY`, `COUNT_PLNERR`	Other monitor columns

Manage Results grid (Stage 4, tree node 14) — column IDs verified live:

Column ID	What it shows
`RUN_SERIES_NAME`	Run Series name
`COUNT_PRIO1` / `COUNT_PRIO2` / `COUNT_PRIO3`	Finding counts per priority bucket
`COUNT_PLNERR`	Planning errors
`IS_ACTIVE`, `IS_CENTRAL_RUN`, `IS_IN_BASELINE`, `TITLE`, `SCHEDULED_BY`, `SCHEDULED_ON_DATE`, `SCHEDULED_SYS`, `VALID_TO_DATE`, `DATA_SOURCE_ID`, `ANNOTATION`	Other admin columns

The Stage 3 / Stage 4 VBS files put these IDs first in their column- candidate lists, with older release names (RUN_SERIES_NAME, PRIO_<n>, STATUS_ICON, etc.) as portability fallbacks.

Run-series config screen (Stage 2, SAPLSATC_CI_CFG_SERIE_DIALOG screen 3000) — the check-variant field id is VERIFIED live on S/4HANA 1909 (2026-06-03 probe). It sits directly under wnd[0]/usr next to the TITLE field, NOT inside the object-selection tabstrip. sap_atc_create_run_series.vbs tries the verified id first, then a candidate list (chkvCands) for other releases, and aborts loud if none match when --variant= is supplied:

Field id	Status
`wnd[0]/usr/ctxtSATC_CI_S_CFG_SERIE_UI_01-CHECK_VARIANT`	Verified, S/4HANA 1909 — `GuiCTextField`, `changeable=True`. Set via `.Text`.
`wnd[0]/usr/cmbSATC_CI_S_CFG_SERIE_UI_01-CHECK_VARIANT`	Fallback if a release renders it as a dropdown (set via `.key`)
`wnd[0]/usr/ctxtG_DYNP_3000-CHECK_VARIANT` / `…-CI_CHK_VARIANT` / `…-CHKV` / `…-VARIANT`	Cross-release structure-name fallbacks
`wnd[0]/usr/ctxtP3B_CHKV`, `…3010/ctxtG_DYNP_3000-CHECK_VARIANT`	Last-resort fallbacks

The Stage-2 run-series management grid (node 12, program SAPLSATC_CI_CFG_SERIES_CATALOG) exposes its name column as NAME (title "Series Name") — VERIFIED live on S/4HANA 1909 (2026-06-26 S4D, dumped via ColumnOrder at ATC node 12; columns are NAME, TITLE, CHECK_VARIANT, CREATED_BY, CREATED_ON, CHANGED_BY, CHANGED_ON, UPDATE_ITEM_STATE, OVERRIDE_BASELINE_EFFECT). There is no APP_CONFIG_NAME on this grid — that id belongs to the Stage-3 Run Monitor grid (node 13). The row-matching candidate list in sap_atc_create_run_series.vbs now lists NAME first, so the correct column is matched without relying on the invalid candidates raising an error first (on the tested kernel an unknown column id raises -2147024809, but that behaviour is not guaranteed across releases/locales — a build that returns "" instead would never trip the fallthrough). Live repro confirmed the match lands on the right row via column NAME (e.g. row 80). The last-row fallback itself is removed (2026-07-02): when no candidate column matches, Stage 2 aborts with ERROR: RUN_SERIES_NOT_FOUND (exit 1) without executing anything.

On a different release: if Stage 2 errors with "check-variant input field could not be located", record the config screen via /sap-gui-probe or /sap-gui-probe --record, read the real field id, and prepend it to chkvCands. Then update this table.

Recording references

Each stage's VBS header names its source recording (captured with SAP GUI's Script Recording and Playback against S/4HANA 1909):

Stage VBS	Source recording
`sap_sci_create_object_set.vbs`	`Record_SCI_CreateObjectSet_01.vbs`
`sap_atc_create_run_series.vbs`	`Record_ATC_CreateRunSeries_01.vbs`
`sap_atc_check_run_status.vbs`	`Record_ATC_CheckRunStatus_01.vbs`
`sap_atc_get_results.vbs`	`Record_ATC_CheckResult_01.vbs`

When something breaks on a different SAP release, re-record on the target system and patch the affected VBS.

Composition with `/sap-sp02`

The Stage 4 download is best-effort — if the ATC Manage Results detail screen doesn't expose a Save list to local file shortcut on your release, Stage 4 emits SAVE_HINT: and leaves the screen open. The operator can then run /sap-sp02 against any spool produced via *List

Print > Print* (the same idiom as /sap-where-used-list --to-spool) to capture a TXT copy.

Central / remote ATC (`--object-provider`)

Large conversions run readiness ATC from a central check system (a hub on NW 7.52+/S4 that carries the S/4 simplification content) against the custom code on remote satellites (e.g. the ECC source), instead of running ATC on each system. Two ways to do that with this skill:

Logged-into-the-hub (no --object-provider) — the simplest, fully supported path: point your session at the hub (e.g. /sap-login --switch <check_system>), make sure the code under test is present there, and run /sap-atc --variant=S4HANA_READINESS locally on the hub. This is the migration chain's default (see /sap-cc-analyze).
True remote object provider (--object-provider=<ID>) — the hub analyzes a satellite's code in place over RFC. The run series binds to a registered object provider (DATA_SOURCE_ID / SCA_DS_OBJECT_PROVIDER_ID).

Prerequisites for option 2 (all on the hub):

An SM59 RFC destination to each satellite.
A registered object provider / system grouping (tx ATC → Manage System Groupings; stored in SATC_AC_OSY_ATTR). /sap-atc does not create these.
Version direction: the hub's check content must be ≥ the satellite's target release. You check OLD systems FROM a NEW hub — never the reverse.
The Simplification Database / readiness content loaded on the hub (same as for --variant=S4HANA_READINESS).

Status — UNVERIFIED (single-system limitation). The remote object-provider field only appears on the run-series config screen once providers are registered; no configured hub was available, so the field id in provCands (sap_atc_create_run_series.vbs) is a conjecture. The fail-loud guard is verified live (S/4HANA 1909): with --object-provider set on a non-hub, Stage 2 aborts with "no remote object-provider field found" before any Save — it never silently runs a LOCAL analysis under a remote request. On a real hub, if Stage 2 fails-loud, record the config screen via /sap-gui-probe and prepend the true field id to provCands, then update the table below.

Provider field candidate (UNVERIFIED)	Notes
`wnd[0]/usr/ctxtG_DYNP_3000-DATA_SOURCE_ID` / `cmb…`	Most likely (the run stamps `DATA_SOURCE_ID`; input or dropdown)
`…-OBJECT_PROVIDER`, `ctxtSATC_CI_S_CFG_SERIE_UI_01-DATA_SOURCE_ID`	Alternatives

Limitations

One-time recording per release. ATC tree node IDs and result- grid column IDs were captured on S/4HANA 1909. On other releases, re-record via /sap-gui-probe --record and patch the four VBS files.
OBJECT_TYPE coverage (verified live, S/4HANA 1909):
- PROGRAM → XSO_REPO + SO_REPO-LOW ✓
- CLASS / INTERFACE → XSO_CLAS + SO_CLAS-LOW ✓ (SCI groups them as one category)
- FUGR → XSO_FUGR + SO_FUGR-LOW ✓
- DDIC → XSO_DDIC + SO_DDIC-LOW (untested but field ID dumped)
- TYPEGROUP → XSO_DDTY + SO_DDTY-LOW (untested)
- WDYN → XSO_WDYN + ctxtSO_WDYN-LOW (untested; uses ctxt instead of txt)
- FM is intentionally rejected — there is no per-FM category in SCI Object Sets. The Stage 1 VBS produces a clear redirect message pointing at FUGR <function-group-name> instead.
Stage 4 download is best-effort. The recording stops before the download step; the VBS attempts Ctrl+Shift+F9 followed by a format-radio + DY_PATH/DY_FILENAME dialog (the SP02 idiom). If the Manage Results detail screen on your release uses a different save path, the VBS emits SAVE_HINT: and leaves the screen open for manual export.
No baseline / exemption flow. ATC has rich baseline-comparison and exemption-management features; v1 of this skill ignores them and reads raw P1/P2/P3 counts. Future expansion: a --baseline=<NAME> flag that compares against a saved baseline rather than absolute zero.

Migration note (for operators of the previous skill)

The previous sap-atc shipped a single sap_atc_run.vbs that drove SCI's results-tree screen (Error / Warnings / Information columns, no Priority). That implementation is retired — the four-stage flow above captures findings via ATC's native Priority columns and supports async runs, Object Set reuse, and downloadable result files.

Operator-visible API changes:

The first positional argument is still <OBJECT_TYPE> <OBJECT_NAME>.
The old positional [CHECK_VARIANT] argument is replaced by the named flag --variant=<NAME> (alias --check-variant=). When omitted, the run series leaves the check-variant field untouched and ATC runs the system's configured default variant (plus the default behaviour flags GENERATED_CODE-ANALYZE, QUICKFIXES-GENERATE_QUICKFIXES) — same as before. When supplied (e.g. --variant=S4HANA_READINESS), Stage 2 sets that variant on the run-series config, and fails loud rather than silently falling back to the default if it cannot locate the field on the connected release (see Step 4).
MAX_PRIORITY is still honoured but now applies to ATC's actual priority columns instead of a heuristic mapping.

name	sap-atc
description	Runs the SAP ABAP Test Cockpit (ATC) end-to-end as a quality gate: builds an SCI Object Set scoped to the target object(s), creates an ATC Run Series bound to that set, polls the ATC Run Monitor until the run completes, then reads the Priority 1 / Priority 2 / Priority 3 finding counts from the Manage Results screen and (best-effort) downloads the result text file. Applies the customer brief's MAX_PRIORITY threshold to decide pass / fail. Replaces the legacy SCI-results-tree implementation that lacked a Priority column. Per-stage VBS references are recorded against the S/4HANA 1909 ATC layout — re-record on first failure with /sap-gui-probe --record if your release uses different tree node IDs / grid column IDs. Prerequisites: Active SAP GUI session (use /sap-login first).
argument-hint	<OBJECT_TYPE> <OBJECT_NAME> \| --object-list=<file> [--variant=<NAME>] [--object-provider=<ID>] [--max-priority=<n>] [--object-set=<NAME>] [--run-series=<NAME>] [--poll-interval=<sec>] [--max-wait=<sec>] [--save-to=<PATH>] [--drill] [--no-drill]

sap-atc

이 저장소의 다른 Skills

SAP ATC Quality Gate Skill

Stage map

Shared Resources

Step 0 — Resolve Work Directory

Step 0.5 — Start Logging

Step 0a — Read MAX_PRIORITY from the Customer Brief

Step 1 — Parse Arguments

Step 2 — Ensure SAP GUI Session

Step 2b — Pre-flight: Resolve the Target Object (empty-scope guard)

Step 3 — Stage 1: Create Object Set (SCI)

Step 4 — Stage 2: Create + Execute Run Series (ATC)

Step 5 — Stage 3: Poll Run Status

Step 6 — Stage 4: Read Results + Apply Gate

Step 6b — Stage 4b: Drill Into Per-Finding Detail (conditional)

6b.1 — Fill and run sap_atc_drill_findings.vbs

6b.2 — Interpret + report

6b.3 — Failure handling

6c — Record FM/METHOD findings to frequently_errors (best-effort)

Step 6d — Register Artifacts for /sap-evidence-pack (best-effort)

Step 7 — Report

Step 8 — Clean Up

Final — Log End

Component IDs (verified S/4HANA 1909, recorded reference)

Recording references

Composition with /sap-sp02

Central / remote ATC (--object-provider)

Limitations

Migration note (for operators of the previous skill)

SAP ATC Quality Gate Skill

Stage map

Shared Resources

Step 0 — Resolve Work Directory

Step 0.5 — Start Logging

Step 0a — Read MAX_PRIORITY from the Customer Brief

Step 1 — Parse Arguments

Step 2 — Ensure SAP GUI Session

Step 2b — Pre-flight: Resolve the Target Object (empty-scope guard)

Step 3 — Stage 1: Create Object Set (SCI)

Step 4 — Stage 2: Create + Execute Run Series (ATC)

Step 5 — Stage 3: Poll Run Status

Step 6 — Stage 4: Read Results + Apply Gate

Step 6b — Stage 4b: Drill Into Per-Finding Detail (conditional)

6b.1 — Fill and run sap_atc_drill_findings.vbs

6b.2 — Interpret + report

6b.3 — Failure handling

6c — Record FM/METHOD findings to frequently_errors (best-effort)

Step 6d — Register Artifacts for /sap-evidence-pack (best-effort)

Step 7 — Report

Step 8 — Clean Up

Final — Log End

Component IDs (verified S/4HANA 1909, recorded reference)

Recording references

Composition with /sap-sp02

Central / remote ATC (--object-provider)

Limitations

Migration note (for operators of the previous skill)

이 저장소의 다른 Skills

Step 6d — Register Artifacts for `/sap-evidence-pack` (best-effort)

Composition with `/sap-sp02`

Central / remote ATC (`--object-provider`)

Step 6d — Register Artifacts for `/sap-evidence-pack` (best-effort)

Composition with `/sap-sp02`

Central / remote ATC (`--object-provider`)