Sc4sap:create Program

SC4SAP Create Program

Core ABAP program creation skill. Generates a Main Program wrapped with conditional Includes following the sc4sap template convention. Supports both OOP (two-class split: Data + Screen/ALV) and Procedural (PERFORM) paradigms. Full pipeline: SAP version preflight → Socratic interview → planner → writer spec → user confirm → executor/qa/reviewer.

Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention.

Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus 4.7|Sonnet 4.6|Haiku 4.5> per ../../common/model-routing-rule.md § Phase Banner Convention.

Four teamMode integration points — Type A: Phase 1A (post-interview cross-module consistency) + Phase 2 (planner conflict resolution) — see team-mode.md. Type B: Phase 4 Wave 2/3 (executor's novel code gets live consultant review) — see team-mode-b.md. Type D: Phase 1A↔1B bridge — user-chosen at Phase 1A close (legacy sequential 1B vs Type D team synthesis); analyst + architect + consultant parallel synthesis replaces sequential 1B when selected — see team-mode-d.md. Base protocol: ../../common/team-consultation-protocol.md.

Paths are relative to this skill's directory (sc4sap/skills/create-program/).

ECC DDIC fallback gate. When the planner's object list includes a new Table, Data Element, or Domain AND SAP_VERSION = ECC, Phase 4 (Executor) must not call CreateTable / CreateDataElement / CreateDomain. Instead, follow ../../common/ecc-ddic-fallback.md: generate a helper report in $TMP using the matching template under skills/create-object/ecc/, activate the helper, then emit the mandatory user message (SE38 run → uncheck dry-run → SE11 activate + assign transport). Do not treat the DDIC object as created until the user confirms activation. Remaining objects (classes, includes, screens, …) proceed on the normal flow; the plan should sequence the DDIC helpers first so the user can create them before code that depends on them is activated.

MUST run BEFORE the Socratic interview starts. The entire development approach (tables, BAPIs, CDS availability, ABAP syntax, RAP eligibility) depends on the SAP platform and release.

Steps:

1. Read .sc4sap/config.json for sapVersion, abapRelease, and activeModules
   • Also read .sc4sap/sap.env → SAP_ACTIVE_MODULES as fallback
   • Load common/active-modules.md and precompute the cross-module concern list for the program's primary module. Every downstream phase (planner, writer, executor) receives this list and must factor in integration fields (e.g., MM primary + PS active → add PS_POSID).
2. If missing or stale, ask the user to confirm:
   • ECC (ECC 6.0) — classical DDIC, LFA1/KNA1/BKPF/BSEG/MKPF/MSEG world, SAPGUI only
   • S/4HANA On-Premise — ACDOCA, MATDOC, Business Partner (BUT000), CDS/AMDP preferred, Fiori possible, ADT-first
   • S/4HANA Cloud (Public) — no classical Dynpro, no SE80 custom dev, only Developer Extensibility / Key User Extensibility (RAP managed, Custom Fields/Logic, Custom Business Objects)
   • S/4HANA Cloud (Private) — similar to On-Premise but with extensibility-first mindset
3. Confirm abapRelease (e.g. 750, 756, 758) — drives allowed syntax

Branching consequences:

• ECC: no RAP, no ACDOCA, no Business Partner; inline decl only if 740+; CDS/AMDP typically unavailable (<750)
• S/4HANA On-Prem: prefer CDS + AMDP, RAP where applicable, Business Partner APIs, ACDOCA for finance
• S/4HANA Cloud Public: REJECT classical Dynpro / custom screen + GUI Status requests. The standard Full-ALV path (CL_GUI_ALV_GRID + Docking Container) is not executable on Cloud Public — must redirect to RAP + Fiori Elements, if_oo_adt_classrun, or SALV-only output. Fail-fast with an explanation. Full prohibited-statement list and Cloud-native API replacements: see ../../common/cloud-abap-constraints.md.
• S/4HANA Cloud Private: classical Dynpro technically possible but discouraged; warn user and confirm intent before proceeding.

Outputs:

• .sc4sap/program/{PROG}/platform.md — resolved platform, release, and constraints
• Interview dimensions pre-filtered by platform (e.g., ALV-Full hidden on Cloud Public)

Full procedure (when-to-stock, three-option prompt, dispatch template, persistence paths, reuse-gating rules) lives in inventory-lookups.md. Read and follow literally. Output files consumed by planner / writer / executor:

• .sc4sap/program/{PROG}/cbo-context.md
• .sc4sap/program/{PROG}/customization-context.md

Full procedure — two-stage rule, lead agents, dimension lists, skip rules, gates, output files, and enforcement contracts — lives in interview-gating.md. Read that file and follow it literally before asking the first question.

One-line summary:

Phase 1A sap-{module}-consultant interviews business context (purpose / reason / company rules / reference assets / standard-SAP alternatives) → file module-interview.md, gate ≤ 5% → Phase 1B sap-analyst + sap-architect interview technical dimensions (purpose-type / paradigm / display / screen / data / package / test) → file interview.md, gate ≤ 5% → proceed to <Spec_Approval_Gate>. Phase 1B never starts before 1A closes; Phase 2 planner refuses to run if either file is missing.

Full procedure — required steps, enforcement contract, rationale, spec template, and the verbatim user-facing approval prompt — lives in spec-approval-gate.md. Read that file and follow it literally.

One-line summary (the full text lives in the companion file):

Invoke sap-writer → produce spec.md → display to user → wait for an explicit approval keyword (승인 / approve / ok / proceed / go ahead / confirmed). "yes" / "빨리" / "해봐" / silence are NOT approval — loop with revisions. Phase 4 Executor refuses to run if spec.md is missing, unapproved, or modified after approval.

• If .sc4sap/session-trust.log already has a line within the last 24h, skip silently.
• Exception: GetTableContents and GetSqlQuery are NEVER auto-approved — they require explicit per-call user consent. See ../trust-session/SKILL.md Layer 1.

trust-session is NOT re-invoked here — it already ran at the start of Phase 1A.

Full procedure — verbatim mode-prompt text, per-mode semantics, state.json schema (also drives C-2 resume support), and manual-mode phase-transition prompt — lives in execution-mode.md. Read that file and follow it literally before dispatching Phase 4.

Read that file before dispatching any agent. It is the authoritative source for:

• Phase 0 — SAP Version Preflight
• Phase 1A — Module Interview (sap-{module}-consultant, business context)
• Phase 1B — Program Interview (sap-analyst + sap-architect, technical dimensions)
• Phase 2 — Planning (sap-planner + consultants, CBO reuse gate, SPRO lookup)
• Phase 3 — Spec Writing (sap-writer)
• Phase 4 — Implementation (sap-executor)
• Phase 5 — QA (sap-qa-tester, OOP mode)
• Phase 6 — Review (sap-code-reviewer, mandatory, see phase6-review.md)
• Phase 7 — Debug escalation (sap-debugger)
• Phase 8 — Completion Report (gated on Phase 6 PASS)

Do not inline or paraphrase phase logic here — update agent-pipeline.md instead so the pipeline stays single-sourced.

Task: {{ARGUMENTS}}