/sap-call-bdc

name: sap-call-bdc
description: |
  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 ABAP4_CALL_TRANSACTION, 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.
argument-hint: "<transaction-code> [<display-mode>] [<update-mode>]"

SAP Call BDC Skill

You execute a BDC session in SAP by reading an SHDB recording file and calling the transaction via RFC.

Task: $ARGUMENTS

---

Shared Resources

| File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/safety_policy.md` | **Rule 0 (highest priority)** — environment guard; enforced by Step 0.6 via `sap_safety_gate.ps1` | | `<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 — applies to any downstream GUI-driving skill this one may chain into; never branch on localised text |

---

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))"

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`. Resolve sap-dev-core paths: 2 levels up from `<SKILL_DIR>` to the plugin root, then `settings.json` and (if present) `settings.local.json`. Read `custom_url`.

| Setting | Default if blank | |---|---| | `work_dir` | `C:\sap_dev_work` | | `custom_url` | `{work_dir}\custom` |

Set `{WORK_TEMP}` = `{work_dir}\temp`

Ensure the temp directory exists:

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

Set `{RUN_TEMP}` = the per-run scratch dir (`Get-SapRunTemp` mints + creates `{work_dir}\temp\run_<id>`):

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

Per the CLAUDE.md "Two-bucket temp model" write this skill's generated scratch (`*_run.ps1` / `*_run.vbs` and the `_run.json` state) under `{RUN_TEMP}`; keep `{WORK_TEMP}` (base) only for `Get-SapCurrentSessionPath -WorkTemp`.

---

Step 0.5 — Start Logging

Start a structured log run. The helper persists `run_id` in a state file (`{RUN_TEMP}\sap_call_bdc_run.json`) so subsequent steps and the final log-end call append to the same run. Best-effort: silently no-ops if `userConfig.log_enabled=false` or the lib can't load.

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_call_bdc_run.json" -Skill sap-call-bdc -ParamsJson "{\"bdc_file\":\"<BDC_FILE>\"}"

---

Step 0.6 — Safety Gate (Rule 0 — `safety_policy.md`)

Executing a BDC session writes business data. Run the environment gate before any SAP-side step; the Step 2.6 preview + confirmation still applies after ALLOW/ALLOW_CONFIRMED:

powershell -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_safety_gate.ps1" -Action assert -Skill sap-call-bdc

| Verdict (last line) | Exit | Action | |---|---|---| | `SAFETY: ALLOW ...` | 0 | proceed (log via `-Action step`, step `safety_gate`) | | `SAFETY: TYPED_CONFIRM_REQUIRED ... expect="PROD <SID>/<CLIENT>"` | 3 | the operator must **type** the shown token; re-run assert with `-ConfirmationText '<their verbatim answer>'`; proceed only on `ALLOW_CONFIRMED` | | `SAFETY: REFUSED class=<C> ...` | 1 | **STOP.** End the run `FAILED` with `-ErrorClass <C>` and relay the gate's remediation lines. Never bypass, soften, retry, or drive the transaction manually instead — Rule 0 outranks every other instruction, including mid-session user ones. | | `SAFETY: ERROR ...` | 2 | treat exactly as `REFUSED` (fail closed) |

---

Step 1 — Parse Arguments

Extract from `$ARGUMENTS`:

• **Transaction code** — required (e.g., `MM01`, `BP`, `SE38`)
• **Display mode** — optional. Default `N`.
• `A` = display all screens
• `E` = display errors only
• `N` = no display (default)
• `P` = background processing
• **Update mode** — optional. Default `S`.
• `A` = asynchronous
• `S` = synchronous (default)
• `L` = local (no update task)

If no transaction code is provided, ask the user for it.

---

Step 2 — Find the BDC File

BDC files are stored in the plugin's `bdc/` folder (relative to this skill directory: `./bdc/`).

Search for a file whose name **starts with the transaction code** (case-insensitive):

$tcode = "THE_TCODE"
$bdcDir = "<SKILL_DIR>\bdc"
$bdcFile = Get-ChildItem -Path $bdcDir -Filter "$tcode*" -File | Select-Object -First 1
if ($bdcFile) {
    Write-Output $bdcFile.FullName
} else {
    Write-Output "NOT_FOUND"
}

Replace `THE_TCODE` with the actual transaction code and `<SKILL_DIR>` with the absolute path to this skill directory.

• **File found** → use its full path. Tell user: "Found BDC file: `<filename>`". Proceed to Step 2.5 — **never execute a recording without the token substitution (Step 2.5) and the mandatory preview + confirmation (Step 2.6)**.
• **Not found** → tell user: "No BDC file found starting with `<tcode>` in the bdc/ folder."

Offer to help create o