SAP reference for prices¶
This page complements prices. SAP SD condition technique is the closest analogy, but its key depends on the configured procedure, condition table, and organizational dimensions.
| OpsFactor | Nearby SAP concept | Common sources | Note |
|---|---|---|---|
priceListId |
condition type + organization/channel/list + validity | condition tables A*, KONH, KONP |
Access and persistence differ between ECC and S/4HANA |
locationId |
plant, sales organization, customer, or ship-to | condition key | Define which dimension represents location |
materialId |
MATNR |
condition item/key | Valued material |
grossUnitPrice, netUnitPrice |
condition value and pricing unit | KBETR, KPEIN, KMEIN |
Define gross/net and currency |
| validity | DATAB, DATBI |
condition record | Convert to the OpsFactor effective interval |
Nearby SAP transactions or apps¶
VK11, VK12, and VK13 create, change, and display condition records. Fiori
pricing apps may replace them depending on the deployed release and scope.
ID and semantic difference¶
A reproducible example is PR00-BR10-10-MAT-001-20260101, adding every
dimension that actually forms the SAP key. Do not use only an internal
condition number if it is not stable across environments.
OpsFactor selects versioned lists by priority and validity. The integration must resolve which conditions represent gross and net prices and translate SAP conflicts/priorities; copying every condition without that rule does not reproduce the effective price.