Early accessSome features may be unavailable
Integration · SAP

S/4HANA-ready reference data, by construction.

27 SAP tables with foreign-key integrity across the P2P cycle. HANA and classic dialects. Separate master data and transactional for clean GL-to-subledger reconciliation testing.

Why SAP reference data

End-to-end provenance, not hand-faked CSVs.

SAP consulting shops, audit firms, and ERP migration teams have spent years faking BKPF/BSEG/ACDOCA test data by hand or shelling out for obfuscated client extracts. VynFi generates the whole graph from a single declarative config — with foreign keys that actually line up.

8 transactional + master tables

BKPF, BSEG, ACDOCA for the ledger. LFA1/LFB1 (vendors), KNA1/KNB1 (customers), MARA/MARD (materials), CSKS (cost centers), CEPC (profit centers).

27 total columns per table

Dual dialect

HANA: semicolon delimiters, comma decimals, ISO dates, UTF-8 BOM — direct IMPORT FROM CSV FILE target. Classic: comma delimiters, period decimals, YYYYMMDD — legacy ECC.

HANA default · classic available

FK integrity by default

Every PO has a matching GR; every GR has a matching invoice; every invoice has a matching JE. The three-way match closes 100% or the job fails validation.

Three-way match 100%

Configurable client + ledger

Assign your own SAP client code (default 200), ledger (default 0L), source-system tag (default DATASYNTH). Fits your naming convention, not ours.

Client · ledger · source_system

Master vs transactional split

Generate master data independently to validate migration scripts, or together for end-to-end reconciliation tests. Toggle each of the 8 tables on or off.

Per-table selection

Realistic cost-center allocation

CSKS hierarchy + CEPC profit-center rollup mirror realistic enterprise structures. Combine with manufacturing cost-flow for WIP → FG → COGS attribution.

Paper §5 · Knowledge graph
Configuration

One YAML block. Two dialects.

Specimen · generation config
output:
  format: sap
  sap:
    dialect: hana              # or classic
    client: "200"
    ledger: "0L"
    source_system: DATASYNTH
    tables: [bkpf, bseg, acdoca, lfa1, kna1, mara, csks, cepc]

Files land at sap_export/{bkpf,bseg,acdoca,lfa1,kna1,mara,csks,cepc}.csv inside the job archive. Access them via GET /v1/jobs/{id}/download/sap_export/bkpf.csv for single files, or GET /v1/jobs/{id}/download for the whole archive. No new endpoints, no zip shenanigans.

Begin

Generate your first SAP reference.

SAP export is available on Scale and Enterprise. 1.25× credit multiplier applies on jobs using the format.