Sc4sap:package To Process

SC4SAP Package → End-to-End Business Process

Reads ONE CBO package via MCP, classifies its programs/FMs into business document flows (PR → PO → GR → IR, SO → DN → Billing, etc.), and renders a Markdown narrative for functional consultants. Unlike analyze-cbo-obj (static inventory of reusable elements) or program-to-spec (single-object spec), this skill produces a process-level story spanning multiple programs with Mermaid diagrams + per-step tables.

Step X/7 · <label>   [██████░░░░░░░░░░░░░░]  29%

• Bar width = 20 chars, filled = █, empty = ░
• Percentage = floor(step_id × 100 / 7) at entry (Step 0 = 0%, Done = 100%)
• Authoritative mapping table: workflow.md § Progress Reporting

The bar is the only progress feedback for the user during long Steps 4–6 (multi-minute analyst dispatches), so it MUST be printed before each Step starts.

Invoke /sc4sap:trust-session with parent_skill=sc4sap:package-to-process to pre-grant MCP tool + file-op permissions (eliminates per-tool prompts during package walk + where-used graph + analyst/writer dispatches).

• If .sc4sap/session-trust.log already has a line within the last 24h, skip silently.
• Otherwise run it and surface the one-line confirmation.

Full spec: see ../trust-session/SKILL.md.

• Main orchestrator (Sonnet 4.6) — Steps 0, 1, 2 (gate), 3, 7: trust-session, intake, inventory gate, entry-point detection, validation/handoff. Sonnet provides enough headroom for the intake state machine and entry-point matching across PROG × TCode.
• sap-stocker (Sonnet 4.6, conditional) — Step 2 dispatch only when .sc4sap/cbo/<MODULE>/<PACKAGE>/inventory.json is missing. Runs the full Investigation_Protocol per ../../agents/sap-stocker.md.
• sap-analyst (Opus 4.7, frontmatter) — Step 4 (auto process grouping w/ rationale) + Step 5 (per-process narrative + 1-hop boundary + sequenceDiagram). Opus is required: novel cross-program reasoning + business-flow inference, not template-fill.
• sap-writer (Sonnet 4.6 via model: "sonnet" override) — Step 6 render. Master Markdown is L3-grade depth (TOC + multiple Mermaid blocks + per-process tables + cross-module gap section); Haiku is insufficient.
• Module consultant (optional, conditional) — if Step 5 narrative discovers a strong cross-module integration (e.g., MM ↔ FI through BAPI_ACC_DOC_POST), the analyst MAY annotate via sap-{module}-consultant (Opus 4.7) for the boundary section only. NOT a default dispatch — costs additional context only when warranted.

SAP MCP permission prompts are auto-approved by the sc4sap permission-approver PreToolUse hook.

.sc4sap/processes/<MODULE>/<PACKAGE>/process-<YYYYMMDD>-<lang>.md and/or .html (the process document has no Excel form — an Excel-only selection keeps its .md) .sc4sap/processes/<MODULE>/<PACKAGE>/bpml-<YYYYMMDD>-<lang>.xlsx / .md / .html (one per selected format)

HTML = the matching .md converted by scripts/spec/md-to-html.mjs (images inlined; Mermaid via CDN when opened online).

• <MODULE> = uppercase module key (SD, MM, FI, CO, PP, PM, QM, WM, TM, TR, HCM, BW, PS, Ariba)
• <PACKAGE> = uppercase package name
• <YYYYMMDD> = generation date
• <lang> = ISO 639-1 selected at Step 1 (ko / en / ja / other)
• Existing file at the same path → overwrite WITH a one-line > Regenerated from <old-date> note at the top (md, carried into html; xlsx overwrites silently).

Do not skip the companion-file reads — the step order, grouping dictionary, output skeleton, and dispatch prompts all live there.

Task: {{ARGUMENTS}}