AI Agent Workflow Collection

Manages SAP Business Partners via the BP transaction using SAP GUI Scripting. Creates new partners (Organization type) or updates existing ones. Existence check, partner creation with role/grouping selection, and partner update with field values from a definition file. Prerequisites: Active SAP GUI session (use /sap-login first).

Executes BDC (Batch Data Communication) sessions in SAP via RFC. Reads SHDB recording files from the bdc/ folder, connects via SAP NCo 3.1, calls ABAP4CALLTRANSACTION, and outputs full BDCMSGCOLL messages to a result file. Connection parameters resolved from the AI session's pinned profile in connections.json (saved via /sap-login). Prerequisites: SAP profile saved via /sap-login (RFC password required). SAP NCo 3.1 (32-bit, .NET 4.0) in GAC.

Changes the package (TADIR-DEVCLASS) assignment of an SAP repository object via the "Object Directory Entry" dialog (Goto > Object Directory Entry). Routes by object type to SE38 / SE37 / SE24 / SE11 / SE91 / CMOD (the last for enhancement projects — used by /sap-cmod). Handles three flows automatically based on current vs new package locality: (a) $TMP → transportable (Z/Y): resolves a modifiable TR via /sap-transport-request, then enters the new package + TR. (b) transportable A → transportable B: pre-checks E071/E070 to ensure the object is NOT linked to a modifiable TR (would block the move). (c) transportable → $TMP: confirms the move and presses "Local object". Verifies via TADIR re-query. Prerequisites: Active SAP GUI session (use /sap-login first).

Conservative cleanup of the artefacts /sap-dev-init created. Walks reverse dependency order — wrapper FM, then DDIC structure + table type, then utility program, then function group, then package — and deletes only what the operator confirms. Skips any artefact whose dependents were extended by the operator (e.g. function group that contains user-added FMs, package that contains user-added Z tables) unless --force is set. By default the transport request is left untouched (other work may live in it). Settings.json keys are preserved unless --settings is passed, so a follow-up /sap-dev-init re-creates the same names. The canonical "blow away and rebuild" sequence is: /sap-dev-clean ; /sap-dev-init. Pass --reset for a full, truly-clean reset: it implies --force + --settings, additionally clears the dev-default settings keys and deletes the dev transport request (delegating to /sap-se01) so nothing is left behind for the next /sap-dev-init to choke on. Prerequisites: Active SAP GUI session (use /sap-login first); SAP NCo 3.1 (32-bit, .NET 4.0) in GAC. Clean delegates to GUI-driven delete skills like /sap-se37, /sap-se11, /sap-se38, /sap-function-group, /sap-se21.

Initializes the SAP development environment after plugin installation. Ensures a transport request, package, and function group exist in SAP, then deploys the ZCMRUPDATEADDONTABLE utility program. Mode-aware: respects sapdevmode (GUI / RFC / BDC) and selects the preferred skill variant for each step, falling back to the next mode in the chain when no implementation exists for the preferred mode. Prerequisites: Active SAP GUI session (use /sap-login first). SAP NCo 3.1 (32-bit, .NET 4.0) in GAC for RFC sub-steps.

Transfers files between the local PC and the SAP application server, and lists app-server directories. Four modes: upload (CG3Z, PC -> app server), download (CG3Y, app server -> PC), list and exists (headless RFC via EPS2GETDIRECTORYLISTING - no AL11 scraping). Text (ASC) or binary (BIN) transfer, explicit --overwrite flag, popup-guarded (overwrite Query, cannot-open-file Information popup), locale-independent (all outcomes read via control IDs + MessageType, verified for JA logons). Wires the SAP GUI Security precheck/sidecar around the local-file IO. Closes the file-interface test loop: upload test input -> /sap-run-report -> list -> download output -> diff against the spec's expected output (golden rows / Mapping (File Out)). No transport request involved - this skill touches no repository object. Typical asks: "upload to the SAP server", "download /tmp/x from S4D", "list /usr/sap/trans", "does /tmp/out.txt exist on the app server". Prerequisites: active SAP GUI session (use /sap-login first) for upload/download; SAP NCo 3.1 (32-bit) in GAC for list/exists.

Full lifecycle for SAP function groups: check existence, create, re-activate, query PROGDIR state, and delete. Mode-aware — picks the RFC fast-path (RSFUNCTIONPOOLINSERT, RFCREADTABLE on TLIBG / TFDIR / TADIR / PROGDIR) when possible, falls through to GUI scripting (SE37 menus + SE38 delete) when no RFC equivalent exists. Honours userConfig.sapdevmode (GUI / RFC); the default chain for each operation is documented in the SKILL.md mode dispatch table. Replaces the now-removed sap-se37-fugr skill — call this skill for every function-group lifecycle step. Deletion is irreversible: the skill MUST confirm with the user before delegating to /sap-se38. Prerequisites: SAP NCo 3.1 (32-bit, .NET 4.0) in GAC for RFC paths; active SAP GUI session (use /sap-login first) for GUI paths.

Generates ABAP Unit tests for an EXISTING object (global class / function module / report) and closes the loop on a live system: pre-check the generated test, deploy, activate, run with coverage, read failures, fix, repeat until green (bounded). Reads the active source, builds a call/data map, and runs a SEAM ANALYSIS that classifies every DB read and external call into a doubling strategy (OSQL test double for SELECTs, ABAP test double for injected dependencies, or flags untestable-without-refactor), then emits a test class honest about what it could and could not cover. Pairs with /sap-run-abap-unit (which runs the tests). Deploy is GUI (/sap-se24 --test-source CCAU for a class, /sap-se38 for a report test) and gated — asks before writing anything (Rule 2). Prerequisites: pinned /sap-login connection; active GUI session for class download + deploy + run; SAP NCo 3.1 for RFC source read.

Author a new transaction-specific SAP skill from multiple natural-language scenarios. Runs /sap-gui-probe for each scenario, then merges the resulting probe folders into one coherent skill folder: SKILL.md with mode dispatch, one references/sap .vbs per probe, parameter tokens derived by cross-probe diff (values that vary across probes become %%TOKEN%%; values that stay constant bake in), popup-branch guards at every step where any probe observed a wnd[1] popup. Output is a ready-to-test draft. Prerequisites: active SAP GUI session (use /sap-login first).

Enumerates a SAP system's integration surface over pure read-only RFC and correlates it into a named interface register — the "list of all interfaces" every upgrade, S/4 migration, or system takeover needs and no SAP system has. scan reads six confirmable sources (RFC destinations RFCDES, IDoc/ALE partner profiles EDP13/EDP21/EDIFCT/TBD05, Z/Y RFC-enabled FMs via TFDIR, OData services via the Gateway hub catalog, ABAP proxies SPROXHDR, and interface-relevant batch jobs TBTCO/TBTCP) into per-source TSVs, then Claude clusters them into interfaceregister.tsv with a hard CONFIRMED-vs-INFERRED rule and a mandatory Gaps section. doc reverse-engineers one interface into a spec (IDoc segment tree via IDOCTYPEREADCOMPLETE, RFC-FM signature via RPYFUNCTIONMODULEREAD). Read-only — no writes, no GUI, no Z-object dependency. Release divergence (S/4-only OData hub, proxy framework) is handled by runtime existence probes, never a silently thinner register. Prerequisites: SAP profile via /sap-login (RFC); SAP NCo 3.1 (32-bit) in GAC.

Executes ABAP Unit tests on a deployed object (program or global class) via SAP GUI Scripting and reports per-method pass / fail with a verdict gate. Opens the object in SE38 / SE24, triggers the ABAP Unit run (via the SE38/SE24 menu), and parses the result display. Closes the generate -> deploy -> activate -> TEST loop for /sap-gen-abap output (Z TEST) and works standalone on any brownfield object. GUI backend, verified on S/4HANA 1909. Results-only by default; with --with-coverage it ALSO measures code coverage (Unit Tests With Coverage), running the suite twice (counts + coverage) since the coverage display has no status-bar summary. The RFC backend (ZAUNITRUN, Phase 2) does both in one headless call. Result/coverage component IDs are release-specific; if the skill emits NEEDSRECORDING, record them once with /sap-gui-record (see "Result parsing" below). Prerequisites: Active SAP GUI session (use /sap-login first); developer authorization to run ABAP Unit (SDEVELOP on the object).

Full lifecycle for SAP BAdI implementations via SE19 (BAdI Builder) using SAP GUI Scripting: Create, Update, Display, Delete, Activate, and Deactivate — for BOTH Classic BAdIs (SXSATTR / SXC) and New BAdIs (Enhancement Framework / BADIIMPL). Auto-detects the BAdI type via RFC (SXSATTR-EXITNAME for Classic, BADIIMPL-BADINAME for New); asks the user when a migrated BAdI is genuinely ambiguous (e.g. MBMIGOBADI, MEPROCESSPOCUST). For Create the user supplies a BAdI DEFINITION / enhancement-spot name; for all other operations the user supplies a BAdI IMPLEMENTATION name. Implementing-class work (method source, class create/activate) is delegated to /sap-se24; package reassignment is delegated to /sap-change-package. NEVER deletes a BAdI definition or any implementation it did not create. Prerequisites: Active SAP GUI session (use /sap-login first). SAP NCo 3.1 (32-bit) for the RFC type-detection step.

Deploys ABAP class source code to a SAP system via SE24 using SAP GUI Scripting. Creates new classes or updates existing ones. Existence check (SE24 Display), source upload via source-code-based view, save, and activation. Source is the complete class definition and implementation (CLASS ... DEFINITION through CLASS ... IMPLEMENTATION ... ENDCLASS). Also supports check-and-fix mode: when no source file is provided and the task is "fix Class" or "check and fix Class", opens the class in SE24, runs a syntax check (Ctrl+F2), downloads the source, fixes all errors, re-uploads, and activates the class (Ctrl+F3). Also supports change-properties mode: when the user asks to change a class's Description, Program Status, or Category, opens the class in SE24 CHANGE mode, opens the Properties dialog (Goto > Properties), toggles the dialog to change, updates the supplied fields, Continues, then Saves and Activates so the change persists. If the class opens in the form-based Class Builder it normalises the view to source-based for the edit and restores the prior setting afterward. Handles the conditional original- language popup and the post-save/activate Workbench-request popup per /sap-transport-request. Also supports delete mode: when the user asks to delete a class or interface (e.g. "delete class ", "drop class ", "remove interface "), navigates to SE24, fills the class-name field, presses Shift+F2 (sendVKey 14) from the initial screen, confirms via btnSPOP-OPTION1 (Yes), handles dependent-object and post-delete TR popups, and verifies removal via Display. Deletion is irreversible — the skill asks for explicit confirmation before running the VBS. Prerequisites: Active SAP GUI session (use /sap-login first).

Deploys ABAP function module source code to a SAP system via SE37 using SAP GUI Scripting. Creates new function modules or updates existing ones. Existence check (SE37 Display), source upload to the Source code tab, save, and activation. Source is the full function include (FUNCTION . through ENDFUNCTION.). Also supports check-and-fix mode: when no source file is provided and the task is "fix FM" or "check and fix FM", opens the FM in SE37, runs a syntax check (Ctrl+F2), downloads the source, fixes all errors, re-uploads, and activates the FM. Also supports change-attributes mode: when the user asks to change a function module's Short Text or Processing Type (Regular / Remote-Enabled / Update Module + update kind), opens SE37 in change mode, selects the Attributes tab, updates the supplied fields and saves. Handles the conditional original-language popup and the post-save Workbench-request popup per /sap-transport-request. Also supports reassign-function-group mode: when the user asks to move a function module to a different function group (e.g. "reassign FM to function group "), opens SE37, presses Reassign (toolbar btn[31]), fills the new function group, handles the post-reassign TR popup, then re-activates the FM (reassign leaves it inactive). Also supports delete mode: when the user asks to delete an FM (e.g. "delete ", "remove FM "), opens SE37, presses Delete (Shift+F2 / tbar[1]/btn[14]), confirms via btnSPOP-OPTION1 (Yes), handles the post-delete TR popup if the FM was transportable, and verifies removal via Display. Deletion is irreversible — the skill asks for explicit confirmation before running the VBS. Prerequisites: Active SAP GUI session (use /sap-login first).

Maintains screens (dynpros) in a SAP system via SE51 using SAP GUI Scripting. Two modes: (a) FLOW LOGIC — create new screens or update an existing screen's flow logic (PROCESS BEFORE OUTPUT / PROCESS AFTER INPUT). Existence check (SE51 Display), flow logic paste via Windows clipboard, save, activate. (b) LAYOUT / ADD ELEMENT — add layout elements (static Text labels, Input/Output fields, checkboxes, pushbuttons, radio buttons) to an existing screen via the ALPHANUMERIC Screen Painter (Edit > Create Element). This is the only scriptable placement path: the graphical drag-and-drop Layout Editor is a non-scriptable ActiveX control the recorder cannot capture, and the element-list grid is read-only for placement. Requires the per-user "Graphical Layout Editor" setting OFF. Prerequisites: Active SAP GUI session (use /sap-login first).