SAP OData
Discover services, inspect entities and deliver reviewed SAP test data.
Add the SAP business-system connection in Connections using the gateway origin and supported authentication supplied by your SAP administrator. Keep sandbox and production origins clearly distinguished.
Discover before generating
- Test access and list the integration's available services.
- Select the service and inspect its OData metadata.
- Review the entity's keys, required properties, navigation relationships and field constraints.
- Create or select the saved endpoint and template for that entity.
- Generate a small sample and validate it before a write.
The agent can use the SAP tool surface for metadata, filtered reads and endpoint delivery. Use the announced schema for exact tool arguments. DataMaker's schema graph supports discovery; it does not replace business validation performed by SAP.
Write and verify
The SAP export tool accepts one record object per call. Do not pass an array to export_to_sap_endpoint or assume it automatically splits a batch. Use an appropriate reviewed workflow for larger loads.
SAP writes may require a CSRF token and matching session cookies. Use the supported connector authentication flow rather than a token copied from an unrelated session. If SAP rejects a property or business rule, inspect the response and fix the data; refreshing authentication will not fix a validation error.
Check the created entity and record its returned key before treating a write as complete. For parent-child payloads, verify the nesting and foreign-key relationships on a small sample.
Source data and networking
Filtered reads can return real business data. Apply a reviewed masking policy before using sensitive values outside their approved context. The execution host must reach the gateway and trust its certificate chain.
See SAP regression workflow and Authentication troubleshooting.