> ## Documentation Index
> Fetch the complete documentation index at: https://help.owlery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reading Data from SAP S/4HANA

> How Owlery follows SAP sales, delivery, purchasing, and stock-transfer document flows.

Owlery follows relationships across SAP S/4HANA documents so operational shipments remain aligned with the underlying sales, delivery, and purchasing flow.

## Synchronized records

| SAP record                    | How Owlery uses it                                                             |
| ----------------------------- | ------------------------------------------------------------------------------ |
| Sales Order                   | Customer shipments grouped by production plant or sales-order item             |
| Outbound Delivery             | Shipped quantities, bill of lading, and pickup dates for linked sales orders   |
| Purchase Requisition          | Purchasing shipment for each requisition item with available sales assignments |
| Purchase Order                | Supplier shipment for each purchase-order item                                 |
| Stock Transfer Purchase Order | Internal transfer between supplying and receiving plants                       |

Depending on the document family, Owlery can map document and item identities, timestamps, statuses, materials, quantities, units, weights, prices, plants, partners, facilities, dates, references, item text, pricing conditions, and currency.

## Document relationships

Owlery preserves links between purchase requisitions and purchase orders in both directions. Account assignments can identify a related sales order and customer delivery address. This supports drop-ship and make-to-order flows without duplicating document relationships outside SAP.

For outbound delivery batch splits, Owlery can use child delivery lines when they represent the actual shipped quantities.

## Operational mapping

* Sales facilities come from production plants and ship-to partners.
* Purchasing facilities come from suppliers and linked customer addresses.
* Stock transfers use supplying and receiving plants.
* Requested, delivery, loading, and linked-sales dates are mapped when available.
* Material lines retain SAP item identities, quantities, prices, weights, volumes, and units.
* Bill of lading values remain tied to the relevant item or plant group.

## Synchronization and reliability

* **Incremental synchronization** uses SAP change timestamps and bounded lookbacks.
* **Requisition fallback** uses creation time when an item lacks a change timestamp.
* **Delivery re-enrichment** scans changed delivery items when SAP does not update the sales header.
* **Pagination** drains each enabled record family independently.
* **Chunked lookups** retrieve related sales orders within practical OData request sizes.
* **Relationship caching** avoids repeated partner and plant address calls.
* **Exact lookup** retrieves a specific document and optional item for reconciliation.