SAP reference for inventory policies¶

This page complements inventory policies. The structural difference is essential: OpsFactor keeps policies and details versioned and effective-dated. SAP commonly exposes active material/plant settings; that is not equivalent to a version history.

Nearby fields¶

OpsFactor	Nearby SAP field	Common source	Note
`materialId`, `locationId`	`MATNR`, `WERKS`	`MARC`	Material/plant configuration
`safetyStock`	`EISBE`	`MARC`	Static safety stock
reorder point	`MINBE`	`MARC`	Can support the rule but is not the same OpsFactor field
`maximumStock`	`MABST`	`MARC`	Maximum stock
minimum/fixed lot	`BSTMI`, `BSTFE`	`MARC`	Complements replenishment policy
MRP/lot-size type	`DISMM`, `DISLS`	`MARC`	Governs replenishment behavior
planned delivery time	`PLIFZ`	`MARC`	Related input, not the entire policy

Nearby SAP transactions or apps¶

MM02 and MM03 MRP views support maintenance and reconciliation. The Manage Product Master Data app is the corresponding reference in compatible S/4HANA scenarios. Time-dependent or dynamic methods may have additional configuration; confirm the release and method actually used.

How to create the OpsFactor version¶

An SAP extraction should materialize a policy, for example:

policyId = SAP-MRP-2026-05-01;
validFrom = 2026-05-01;
detail identified by policyId-materialId-locationId-validFrom, such as SAP-MRP-2026-05-01-MAT001-1000-2026-05-01.

policyId must represent the imported snapshot or functional version. A new SAP configuration must not silently overwrite the previous version. A native integration must define an idempotent rule: repeating the same snapshot updates that version; a new snapshot/effective date creates another version. If SAP does not provide history, OpsFactor will only have history from snapshots captured by the integration.

Do not set validFrom to the technical run date when the configuration has a different agreed functional date.

SAP reference¶

Safety Stock Methods

Return to inventory policies or the SAP index.