SAP reference for locations¶
This page complements locations under the current Community/Enterprise contracts. SAP has no single object equivalent to an OpsFactor location.
Nearby objects¶
| OpsFactor type | Nearby SAP object/field | Common tables | Transactions or apps |
|---|---|---|---|
| internal production location | plant WERKS |
T001W |
OX10 / plant configuration |
| storage location | WERKS + LGORT |
T001L |
OX09 / storage-location configuration |
| customer or external destination | Business Partner / customer | BUT000, KNA1 |
BP |
| supplier or external origin | Business Partner / vendor | BUT000, LFA1 |
BP |
Geography, coordinates, Planning Book availability, default unit, and reference location have no universal match. Integrate them from organizational fields, partner addresses, or explicitly documented transformation rules.
What to put in id¶
If each plant is a location, WERKS=1000 can become 1000. If the grain
includes storage location, concatenate WERKS-LGORT, for example 1000-0001.
For partners, use a collision-safe namespace: CUSTOMER-0000123456 or
VENDOR-0000098765.
Do not mix plant and storage-location grains under the same ID. Define in advance which organizational level represents inventory, demand, production, and transportation.
Important difference¶
An OpsFactor location combines planning semantics. An SAP plant, storage
location, or Business Partner is only a candidate source; the integration must
classify locationType and keep references consistent across every dataset.