> ## 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.

# SAP S/4HANA Configuration Reference

> Document scope, order grouping, requisition origins, lookup, and write-back controls.

Owlery reviews your SAP document flow and recommends the grouping, filters, mappings, and optional write-back supported by your services.

| Area | Available controls |
| - | - |
| Sales grouping | Group by production plant or individual sales-order item |
| Requisition origin | Include all origins or selected SAP origin values |
| Record families | Enable or disable sales, purchase, and transfer synchronization |
| Purchase versus transfer | Treat purchase order type `UB` as a stock transfer |
| Full or incremental sync | Run a backfill or retrieve changed records |
| Exact lookup | Retrieve a sales, requisition, purchase, or transfer document and optional item |
| Quote write-back | Enable selected carrier, quote-number, and quote-amount actions |
| Write-back scope | Enable each outbound action independently |
| Freight allocation | Allocate one tender across orders and SAP items while preserving the exact total |
| Additional freight rules | Apply an approved separate freight-charge condition when required |

## Sales order grouping

| Grouping | Owlery identity | Best fit |
| - | - | - |
| Production plant | `{SalesOrder}-{Plant}` | Lines from one production plant move together |
| Sales-order item | `{SalesOrder}-{SalesOrderItem}` | Each line needs independent planning or tracking |

Plant grouping is the default. Owlery recommends the grouping that matches how your team tenders freight.

## Requisition origins

The origin filter can distinguish requisitions created by MRP, direct procurement, production, store orders, manual entry, planned-order conversion, sales documents, planning systems, projects, external requirements, or self-service procurement. Leave the filter empty to include every origin.

## Authentication details

Owlery needs the approved SAP API endpoint plus a dedicated username and password. Permissions depend on the selected inbound and outbound OData services.

Some deployments use custom services for purchase-order partners, texts, or pricing. Owlery confirms the exact service names, partner functions, text types, pricing conditions, and permissions during discovery.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.