STEP 1 — Analyzes Module Pool source code fetched by mcp-abap-adt. IMPORTANT: First use mcp-abap-adt GetProgram to get program source, then GetInclude for each include, then pass combined source here. Returns structured JSON: screens, PAI/PBO modules, tables, LLM business analysis, PAI-to-RAP mapping.

STEP 1b — MANDATORY before generate_rap_skeleton. Checks if SAP has released CDS views for the tables found in the Module Pool. Clean Core: always SELECT from released CDS instead of raw tables. Returns cds_source_mapping to pass into generate_rap_skeleton.

STEP 2 — Given the analysis JSON from step 1, generates the full RAP migration plan: CDS view, Behavior Definition, Behavior Implementation class, metadata extensions. Returns ABAP code as strings — does NOT write to SAP yet. Human must approve.

MANDATORY between every step — shows the human: WHAT WAS DONE, ANALYSIS SUMMARY, and NEXT PROPOSED ACTION. Human must type YES/MODIFY/ABORT to proceed. Always call this before write_abap_object or validate_and_activate.

STEP 3 — Writes a single ABAP object to SAP via ADT REST. CRITICAL: Always follow this exact order: 1st=CDS Root View (DDLS), 2nd=CDS Child Views (DDLS), 3rd=Behavior Definition (BDEF), 4th=Implementation Class (CLAS), 5th=Metadata Extension (DDLS). NEVER write BDEF before CDS views. NEVER write CLAS before BDEF. One object at a time only.

STEP 4 — Activates one or more ABAP objects via ADT REST. Runs syntax check first, returns errors for agent to fix before activation. Call human_checkpoint with results.

Creates a Workbench Transport Request in SAP. Do this before write_abap_object. Returns transport number.