This documentation is available to agents as Markdown at https://docs.synthesized.io/tdk/latest/user_guide/070_integrations/sap.md. For the complete documentation index, see llms.txt.

SAP TDM

The Synthesized Platform creates test data for SAP S/4HANA and SAP ECC: it copies, subsets, time-slices, masks and generates SAP data while keeping the relationships between tables, so business processes still work in the test system. Your data stays inside your own environment.

The SAP data challenge

SAP landscapes are hard to copy safely:

  • Deeply connected data models, with hundreds of tables across functional areas.

  • Implicit relationships that the database doesn’t enforce, so a naive subset breaks.

  • Module boundaries that a usable subset must respect.

  • Sensitive business data across finance, HR and operations.

  • Years of transactional history, too large to copy in full.

What the platform does

  • Maps SAP relationships, including those that database constraints don’t define. See Relationship Mapping.

  • Scopes by functional area, separating master data (materials, vendors, customers) from transactional data (purchase orders, goods movements, invoices). See Modules and Data Scoping.

  • Filters by date: transactional data by posting date, master data by creation date. See Time Slicing.

  • Keeps referential integrity, pulling in the records that selected data depends on.

  • Masks sensitive fields while keeping the fields SAP processes depend on. See Data Protection.

Two ways to connect

Application layer (OData) Database layer (SAP HANA)

How it connects

Through Synthesized’s OData service on the SAP Gateway, installed with a small transport through your normal change process.

JDBC to SAP HANA 2.0 or later, under S/4HANA or ECC.

Access it needs

An SAP user authorized for the service and the tables in scope, over HTTPS. No database access.

A database user: read-only on the source schema and the metadata views, and write on a non-production target schema.

Choose it

By default, and always on RISE with SAP or wherever database access isn’t allowed. It’s SAP’s recommended integration route.

When you run SAP HANA yourself and your DBA approves a dedicated database user.

Setup

SAP Application Layer Integration

SAP HANA Connection

Both keep the data inside your environment. SAP data sources need a license key: in free mode, they’re blocked.

How it works

  1. Connect the source and target SAP systems as data sources.

  2. Choose functional areas: the parts of SAP you need data from.

  3. Choose the scope: master data only, transactional data, or a full copy.

  4. Filter by date range, if you want, to control the volume.

  5. Dependent data is included automatically, so related tables stay consistent.

  6. Choose a protection level, to mask sensitive fields while keeping business logic.

  7. Run the workflow, and check the output in the test system.

When transactional data is selected, the master data records it refers to are pulled in regardless of their creation date, so referential integrity holds across the SAP tables.

You can follow these steps in the SAP Workflow Wizard, or start from a blank SAP workflow and write the configuration yourself.

Choosing the right scope

Environment Recommended approach

Development

Master data only: fast, with a small footprint.

System testing

Transactional data with a recent time window.

UAT

Transactional data with a broader time window.

Performance testing

Transactional data with the full history, or a full copy.

Production clone

Full copy: all master and transactional data.

Before you start

  • Your Synthesized license key.

  • For OData: the Synthesized OData service installed and activated on the SAP Gateway, and an SAP service user for it.

  • For SAP HANA: network access to the database, and database users with the required grants.

  • A non-production target system or schema.

Pages in this section

Page What it covers

SAP Application Layer Integration, with SAP OData Connection

Connect at the application layer: when to use it, what you need, adding the data source, and troubleshooting.

SAP HANA Connection

Connect to SAP HANA over JDBC: URL, grants, TLS and troubleshooting.

SAP Modules

The tables and relationships in MM, FI, CO and HCM.

SAP Data Scoping

Master data only, transactional data, or a full copy.

SAP Time Slicing

Filtering by date, and how master data stays consistent.

SAP Relationship Mapping

Virtual foreign keys and table ordering.

SAP Data Protection

Which fields are kept, masked or noised.

SAP Process Table Reference

The tables behind 40 business processes, with ECC and S/4HANA names.