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

SAP S/4HANA data mapping

Data mapping is where the business decisions of a SAP S/4HANA migration are made. A mapping that copies the legacy structure one to one usually carries the legacy problems into SAP S/4HANA. superglue's agent proposes field mappings and transformations, you decide the ambiguous cases, and the client signs transformed files before anything loads.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Proposes field mappings and value translations from the source structure to SAP S/4HANA.
  • Lists the ambiguous cases and the records that cannot map, with counts.
  • Builds a client questionnaire for questions only the client can answer.
  • Produces transformed files for review.

What you decide and approve

  • The business meaning of ambiguous fields and codes.
  • What happens to records that cannot map.
  • When the mapping is ready for the client's signature.

What the client gets

  • A mapping report to sign.
  • Transformed files to review before the load.

Key SAP S/4HANA mapping decisions

  1. 01

    Map customers and vendors to Business Partner roles

    Each legacy customer and vendor needs a Business Partner grouping and roles such as FLCU01 for customer and FLVN01 for vendor. A party that is both becomes one Business Partner with both roles.

  2. 02

    Agree the value mappings with process owners

    The Migration Cockpit asks for target values for keys such as payment terms, units, tax codes and plants. Get each mapping signed and reuse it in every mock load.

  3. 03

    Map cost elements to G/L accounts

    S/4HANA has no separate cost element master. Primary cost elements become G/L accounts of type primary costs or revenue, and secondary cost elements become G/L accounts of type secondary costs.

  4. 04

    Move legacy segments into Universal Journal fields

    Oracle and Dynamics AX hold reporting values in account segments and financial dimensions. Map them to profit centers, cost centers, segments and functional areas on each ACDOCA line.

Frequently asked questions

What are the key SAP S/4HANA mapping decisions?

Map customers and vendors to Business Partner roles; Agree the value mappings with process owners; Map cost elements to G/L accounts; Move legacy segments into Universal Journal fields. The agent proposes an answer from the source data, and you confirm or change it.

Can the client review the mapping before anything loads?

Yes. The agent produces transformed files and a mapping report. The client signs the mapping, and the load uses exactly the signed mapping.

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.