SAP S/4HANA· Configuration
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 5 of 11 · Implementation · Updated October 26, 2026

SAP S/4HANA configuration

Configuration builds the signed design in SAP S/4HANA: features, setup records, numbering, roles and workflows. Done by hand, it is hours of screens that are hard to review and hard to repeat in production. superglue's agent applies the setup through the SAP S/4HANA API, in the sandbox first, and records each change it makes.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Turns the signed design into a configuration plan for your review.
  • Applies the setup through the API in the sandbox.
  • Records each change, so the configuration can be reviewed and repeated.
  • Repeats the tested configuration in production.

What you decide and approve

  • The setup values that only the client can decide.
  • Every write. Each one pauses for your approval.
  • When the sandbox configuration moves to production.

What the client gets

  • A configured sandbox and production account.
  • A configuration workbook that lists every setting.

What to get right in SAP S/4HANA configuration

  1. 01

    Change configuration only in DEV

    Every customizing change starts in DEV and moves to QAS and PRD by transport. A direct change in QAS or PRD breaks the landscape and the audit trail.

  2. 02

    Follow the Central Business Configuration sequence

    Public Edition is configured through CBC and the configuration apps of the system. The scope, the organizational structure and the core finance settings come first and are hard to change once deployed.

  3. 03

    Set number ranges for migrated data

    Decide internal or external number ranges per Business Partner grouping, material type and document type. Legacy numbers survive only where the number range allows external numbers.

  4. 04

    Build business roles from SAP templates

    Copy the SAP business role templates and restrict them by company code, plant and sales organization. Check segregation of duties before the roles move to QAS.

Frequently asked questions

What should you get right when configuring SAP S/4HANA?

Change configuration only in DEV; Follow the Central Business Configuration sequence; Set number ranges for migrated data; Build business roles from SAP templates. The agent applies the setup in the sandbox first.

Does superglue change SAP S/4HANA without approval?

No. The agent shows each change before it writes and waits for your approval. Production repeats the configuration you tested in the sandbox.

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.