SAP reference for inventory positions¶
This reference translates the current public Community/Enterprise contracts.
The legacy planning-* codebase is not a mapping authority; confirm final
availability in the deployed edition and OpenAPI.
This page complements inventory positions. OpsFactor receives a dated snapshot; SAP current-balance tables and movement documents are not automatically equivalent to that snapshot.
Field mapping¶
| OpsFactor | Nearby SAP field | Common SAP tables | Note |
|---|---|---|---|
snapshotDate |
extraction cut-off date and time | defined by the extraction process | Do not replace it with execution time without a functional agreement |
materialId |
MATNR |
MARD, MCHB |
Material whose balance is reported |
locationId |
WERKS + LGORT |
MARD, MCHB |
Plant and storage location can form one OpsFactor location |
lotId |
CHARG |
MCHB |
Batch when traceability is required |
quantity |
balance in the selected category, such as unrestricted-use stock | MARD, MCHB |
Document included and excluded categories |
uomId |
base unit MEINS or a reconciled balance unit |
material master and balance source | Must be convertible to the planning unit |
| blocked quantity | corresponding blocked or quality categories | MARD, MCHB |
Do not add to available stock without an explicit rule |
If an OpsFactor location represents storage location 0001 in plant 1000,
use a stable code such as 1000-0001. The logical key of a snapshot without a
batch is snapshotDate + locationId + materialId; add lotId for batch-level
stock.
Correct date for Supply Planning¶
Extract inventory at the start of each bucket:
- monthly: first day of the month;
- weekly: Monday, the start of the ISO week;
- daily: start of the day.
For example, the May opening balance must have snapshotDate=2026-05-01. Do
not send the 2026-05-31 balance as if it were the start of May.
MARD and MCHB are common references for current balances. Reconstructing a
historical position may require material documents—such as MKPF/MSEG in ECC
or the MATDOC model in S/4HANA—and reconciliation of every movement through
the cut-off. Whenever possible, produce and retain the snapshot at the agreed
time instead of reconstructing it later.
Nearby SAP transactions¶
MMBE: stock overview across organizational levels;MB52: warehouse stock list;- inventory Fiori apps and CDS views may be the appropriate surface in SAP S/4HANA.
These screens support point-in-time reconciliation. The integrated file or API must still declare stock categories, cut-off time, unit, and grain.
Return to inventory positions, see Identifiers and periodicity, or the SAP index.