Integrations · SaaS applications · Coming next
SAP applications: coming next connector
SAP S/4HANA connector over OData V2 and V4 APIs: entity sets, keys and referential constraints discovered from each service's $metadata, and counted, key-ordered reads.
Coming next SaaS applications
Active implementation; not yet available for production use.
Not available yet. Active implementation; not yet available for production use. The console does not offer it, and asking an agent for a connector it does not ship fails with the error code CONNECTOR_NOT_AVAILABLE; the product never fakes a connection.
What you can do today
Export SAP data to CSV or Parquet with your existing tooling inside your network and read it with the Local files or object-store connectors (SAP HANA databases have their own connector).
Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.
Known limitations
- Exercised only against a local mock of SAP Gateway OData V2/V4 services; not yet run against a real SAP system.
- Read-only access is attested by the operator; only the services' metadata is verified.
- Only single-property referential constraints between configured entity sets become relationships; binary, stream, geo and complex properties are not read.
Capability matrix
SAP applications does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.
| Capability | Design intent |
|---|---|
| Discovery | Planned |
| Classification | Planned |
| Profiling | Not planned yet |
| Masking | Planned |
| Deterministic masking | Planned |
| Entity-aware subsetting | Not planned yet |
| Relationship preservation | Planned |
| Synthetic workflows | Not planned yet |
| Certification | Planned |
| Provisioning | Not planned yet |
| CI/CD | Not planned yet |
| Evidence generation | Planned |
How the connector is designed to prove read-only access
Attested: SAP exposes no machine-readable view of a communication user's authorizations, so the operator attests that the communication arrangement grants read access only; without it the source is refused. The services' metadata is verified: a service that declares create, update or delete, or a side-effecting operation, is refused unless the operator also attests that the arrangement restricts it to reads.
A communication user (basic) or OAuth 2.0 client credentials of a communication system, as secret references. A page that holds fewer records than the service counts (records hidden by authorizations) fails instead of returning a partial read. Records are processed inside your environment and never sent to DataNivra Cloud.
Planned authentication: communication user, basic (secret reference); OAuth 2.0 client credentials (secret reference); access token (secret reference).
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Request this connector
We prioritise connectors by demand, engineering effort and strategic fit. Telling us that SAP applications matters to you is counted; it does not commit a delivery date.
Need something specific from the SAP applications connector? Request a feature (please describe it without real data).
All integrations · SaaS application test data management · Guides · Start free