SAP
change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.Grade C · dataset: API (the vendor’s response payloads) · type sap
What it is
An SAP system read over OData. In the test estate it is S/4 logistics: outbound delivery headers and items, plus one DELVRY07 IDoc. The connector reference is Enterprise SaaS and ERP.
Grade
C. Model only. There is no freely available local edition of the platform.
See the grade table for all 32 types.
Settings and credentials
From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.
| Names | |
|---|---|
| Type | sap |
| Settings | system_id, client, username, host, system_number |
| Credentials | password |
The test connection
Quillmere S/4 logistics
| Setting | Test value |
|---|---|
system_id | QFL |
client | 100 |
username | FACE_RFC |
host | https://sap.quillmere.invalid |
system_number | 00 |
Credentials: password. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.
Write host with its https:// scheme. FACE refuses a bare host name, because it would dial it unencrypted, and it refuses http://.
Stand up the test system
The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.
- Download
sap.zipand unzip it. It holds OData v2 responses forA_OutbDeliveryHeaderandA_OutbDeliveryItem, one DELVRY07 IDoc, andexpected.json. - Open the payloads next to
expected.json, or add the connection with the settings above, pointed at an SAP system you already have.
What FACE finds
Against a real system, FACE reads the OData $metadata (CSDL). The dataset is OData v2 responses from API_OUTBOUND_DELIVERY_SRV, plus one DELVRY07 IDoc file.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryHeader | odata_entity_set | shipments | DeliveryDocument | 24 | 8 |
API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryItem | odata_entity_set | shipments | DeliveryDocument, DeliveryDocumentItem | 47 | 6 |
DELVRY07 | idoc | shipments | E1EDL20.VBELN | 47 | 5 |
Declared foreign keys:
API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryItem(DeliveryDocument) referencesAPI_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryHeader(DeliveryDocument)
expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.
How it joins the Quillmere universe
This source carries 5 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.
| Universe entity | Fields here | Also in |
|---|---|---|
| customer | A_OutbDeliveryHeader.ShipToParty | files, hubspot, kafka, oms, postgres, redshift, salesforce, snowflake |
| order | A_OutbDeliveryItem.ReferenceSDDocument, DELVRY07.E1EDL24.VGBEL | document, files, hubspot, kafka, oms, postgres, snowflake |
| sap_delivery | A_OutbDeliveryHeader.DeliveryDocument, A_OutbDeliveryItem.DeliveryDocument, DELVRY07.E1EDL20.VBELN | only here |
| shipment | A_OutbDeliveryHeader.DeliveryDocumentBySupplier, DELVRY07.E1EDL20.BOLNR | bigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, servicenow, sharepoint, tms, whs, yms |
| sku | A_OutbDeliveryItem.Material, DELVRY07.E1EDL24.MATNR | ims, inventory, logisticsapi, oms, postgres, snowflake |
It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.
See all connectors at once for the walkthrough across every source.
Download
sap.zip: 4 files,expected.jsonincluded.
This is one of 25 zips: the 7 streaming types ship as replay recordings instead.
What is in the zip
sap/A_OutbDeliveryHeader.jsonsap/A_OutbDeliveryItem.jsonsap/idoc_DELVRY07_DESADV.xmlsap/expected.json
The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.