sap-se19listed

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 (SXS_ATTR / SXC_*) and New BAdIs (Enhancement Framework / BADI_IMPL). Auto-detects the BAdI type via RFC (SXS_ATTR-EXIT_NAME for Classic, BADI_IMPL-BADI_NAME for New); asks the user when a migrated BAdI is genuinely ambiguous (e.g. MB_MIGO_BADI, ME_PROCESS_PO_CUST). 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.
sapdev-ai/sap-dev · ★ 7 · AI & Automation · score 75

Install: claude install-skill sapdev-ai/sap-dev

# SAP SE19 BAdI Implementation Lifecycle Skill You drive transaction **SE19 (BAdI Builder)** to manage the full lifecycle of a BAdI **implementation** — Create / Update / Display / Delete / Activate / Deactivate — for both **Classic** and **New** (Enhancement Framework) BAdIs. Two facts decide everything: 1. **Operation** — `create` takes a BAdI **definition / enhancement-spot** name; every other operation takes a BAdI **implementation** name. 2. **BAdI type** — Classic vs New, decided automatically by an RFC classifier (`references/sap_se19_classify.ps1`). If a name is genuinely ambiguous (a *migrated* BAdI that lives in both worlds), you ASK the user. 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 (no unsolicited deploy; no raw SQL writes on SAP tables) | | `<SAP_DEV_CORE_SHARED_DIR>/rules/tr_resolution.md` | TR resolution — this skill delegates to `/sap-transport-request`; never prompt for a TR directly | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI scripting must identify by component ID + DDIC field; status via `MessageType`; VKey not menu-text; no branching on `.Text`/titles | | `<SAP_DEV_CORE_SHARED_DIR>/rules/abap_code_quality_rules.md` | Applies to any implement