Skip to content

SAP

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: 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
Typesap
Settingssystem_id, client, username, host, system_number
Credentialspassword

The test connection

Quillmere S/4 logistics

SettingTest value
system_idQFL
client100
usernameFACE_RFC
hosthttps://sap.quillmere.invalid
system_number00

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.

  1. Download sap.zip and unzip it. It holds OData v2 responses for A_OutbDeliveryHeader and A_OutbDeliveryItem, one DELVRY07 IDoc, and expected.json.
  2. 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.

DatasetKindDomainPrimary keyRowsFields
API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryHeaderodata_entity_setshipmentsDeliveryDocument248
API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryItemodata_entity_setshipmentsDeliveryDocument, DeliveryDocumentItem476
DELVRY07idocshipmentsE1EDL20.VBELN475

Declared foreign keys:

  • API_OUTBOUND_DELIVERY_SRV.A_OutbDeliveryItem (DeliveryDocument) references API_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 entityFields hereAlso in
customerA_OutbDeliveryHeader.ShipToPartyfiles, hubspot, kafka, oms, postgres, redshift, salesforce, snowflake
orderA_OutbDeliveryItem.ReferenceSDDocument, DELVRY07.E1EDL24.VGBELdocument, files, hubspot, kafka, oms, postgres, snowflake
sap_deliveryA_OutbDeliveryHeader.DeliveryDocument, A_OutbDeliveryItem.DeliveryDocument, DELVRY07.E1EDL20.VBELNonly here
shipmentA_OutbDeliveryHeader.DeliveryDocumentBySupplier, DELVRY07.E1EDL20.BOLNRbigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, servicenow, sharepoint, tms, whs, yms
skuA_OutbDeliveryItem.Material, DELVRY07.E1EDL24.MATNRims, 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.json included.

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • sap/A_OutbDeliveryHeader.json
  • sap/A_OutbDeliveryItem.json
  • sap/idoc_DELVRY07_DESADV.xml
  • sap/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.