SAP S/4HANA· Discovery
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 2 of 11 · Pre-implementation · Updated October 26, 2026

SAP S/4HANA discovery and requirements

Discovery workshops decide what the client needs from SAP S/4HANA. The answers end up spread across call notes, emails, chat threads and the sales team's memory, and some get lost between pre-sales and delivery. superglue's agent reads all of them and keeps one list of requirements, with the source and the decision behind each item.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Reads workshop transcripts from your notetaker, and the email, Slack or Teams threads and documents of the project.
  • Writes the requirements per business process, with the source and the person who stated each one.
  • Lists open questions and conflicting statements for the next workshop.
  • Keeps a decision log that design, testing and your colleagues reuse.

What you decide and approve

  • Which requirements are in scope.
  • The priority of each requirement.
  • When the requirements go to the client for sign-off.

What the client gets

  • A requirements document per business process.
  • A decision log with the source of each decision.

What to get out of SAP S/4HANA discovery workshops

  1. 01

    Run fit-to-standard workshops

    Show each SAP Best Practices process in a starter or sandbox system, and record each gap against its scope item. Users react to the real process and ask for fewer changes.

  2. 02

    Record who needs each scope item

    Every scope item adds configuration, master data and test scripts. Record the business owner and the reason for each one in scope.

  3. 03

    Get usage data for custom code

    ECC systems carry years of Z programs, reports and user exits. Use the usage statistics of the system to find which ones still run before anyone asks to rebuild them.

  4. 04

    List every IDoc, RFC and file interface

    ECC landscapes often run EDI through IDocs and side systems through RFC calls. Each interface needs a target on S/4HANA APIs or SAP Integration Suite.

Frequently asked questions

What should come out of SAP S/4HANA discovery workshops?

Run fit-to-standard workshops; Record who needs each scope item; Get usage data for custom code; List every IDoc, RFC and file interface. The agent keeps the requirements and the decisions in the project, so design and testing reuse them.

Which meeting tools can the agent read?

Circleback, Granola, Fireflies, Fathom, Fellow, Read AI and Otter, plus email, Slack, Teams and shared drives. The agent only reads them.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into SAP S/4HANA?

Common sources are SAP ECC, Oracle E-Business Suite, Microsoft Dynamics AX, JD Edwards and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live SAP S/4HANA project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.