TDMS, but agentic, on-demand, and a fraction of the cost.
DataMaker uses the same SAP OData services TDMS does, but it's agent-driven, runs in seconds, and doesn't need a separate landscape to operate.
TDMS is heavy, slow, and built for a different era.
Batch only
Plan, schedule, run, wait. There's no 'give me 50 Business Partners now' workflow, and that's what testers actually need.
Its own landscape
TDMS needs an SAP system, BASIS attention, and licence renewals. You're paying to operate the tool that operates SAP.
Anchored to copy-and-mask
TDMS is built around copying production. DataMaker generates realistic data on demand, no production touch needed.
Same OData entry-points. A different operating model.
DataMaker plugs into the standard SAP OData services your BASIS team already exposes, and runs inside your own network.
V2 & V4, no Z-code
Auto-CSRF, $metadata discovery, $filter queries. DataMaker speaks SAP OData natively, no Z-customisations to maintain.
Prompt → records in seconds
Ask the agent for what you need; typed records land in your sandbox while the tester is still on the call.
No more spreadsheets
The agent reads your $metadata, builds the template, and POSTs back. No mapping spreadsheet, no consultant time.
No second landscape to operate
DataMaker is self-hosted in your data centre or private cloud. No SAP system dedicated to the tool, no BASIS overhead to keep it alive.
Connect, generate, POST, through the same OData TDMS uses.
DataMaker uses the standard SAP OData services your BASIS team already exposes. Auto-CSRF, real entity sets, real status codes, no new landscape.
- OData V2 & V4 (A2X)
- Auto-CSRF token handling
- Native entity discovery via $metadata
- No Z-customisations required
Move off TDMS. Keep the same entry-points.
Start with a pilot on a single SAP sandbox, then scale across the landscape.