SAP SD Condition Record Load Worksheet
Pricing data usually reaches SAP from a spreadsheet. Use this worksheet to lay out condition records with the key fields in order, see the per-unit value, and export a clean sheet for your upload method.
| Condition type | Access (key combination) | Sales org | Dist. channel | Customer / price list | Material | Amount | Per | UoM | Value per 1 UoM | Valid from | Valid to | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
$125 | ||||||||||||
$8 | ||||||||||||
$119 | ||||||||||||
$45 | ||||||||||||
$12 |
Percentage discounts (such as K005 in percent) and values entered per 100 or per 1,000 units should be reviewed before load: the computed column divides the amount by the Per field and is meaningful for currency values only. Condition type codes are examples, check your pricing procedure.
Validate a price list against SAP before upload
Optional: ask Netray about a read-only comparison of your spreadsheet and live condition records.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per condition record. Choose the condition type and the access, enter the key values such as sales org, channel, customer and material, then the amount, the pricing unit (Per), the unit of measure and the validity dates. The Value per 1 UoM column checks your price scale. Export to Excel and map columns to your load tool, whether that is LSMW, the S/4HANA migration cockpit, or manual entry in VK11.
How condition records work
A condition record stores a value for a condition type under a key defined by an access sequence. For PR00 the access sequence normally looks for a customer-specific price first, then a price list, then a general material price. The Per and UoM fields define the pricing quantity, so 840 per 100 M is 8.40 per metre. Validity dates must not overlap for the same key unless you want SAP to delimit them.
- Most specific key is read first
- Per defines the pricing quantity
- Valid-to of 9999-12-31 means open ended
- Scales need separate scale lines in VK11
Checking the result
Sort by material and look for duplicate keys, empty validity dates and units that differ between records of the same material. If a customer price is higher than the list price, confirm that is intended. Currency, unit conversions and rounding in the pricing procedure can change the price shown on the order, so always test two or three records in VA01 with the pricing analysis.
Common mistakes
Common faults are loading records against the wrong sales org, mixing price per unit with price per 100, loading percentages into a value condition type, and ignoring that the condition type is not in the pricing procedure assigned to the customer. A record can be perfect and still never be found if the access sequence or procedure is missing the key field.
Frequently Asked Questions
Can I upload this directly to SAP?
The export is a clean Excel layout. You then map it to your upload method, such as the S/4HANA migration cockpit, LSMW or a recorded VK11 batch. The column names are intentionally generic so they can be mapped.
What does Per mean in a condition record?
Per is the quantity the amount applies to, together with the unit of measure. An amount of 840 per 100 M means 840 for every 100 metres. It is the pricing unit, not the order quantity.
Why is my price not found on the order?
Check the pricing procedure includes the condition type, the access sequence includes your key, the validity covers the pricing date, and the customer pricing procedure and document pricing procedure resolve to the procedure you expect.
What is PR00?
PR00 is the standard price condition type delivered with the SAP pricing procedure RVAA01. Many companies copy it or add their own Z condition types, so confirm the code in your own system.
If you load large price lists often, Netray can help build a validated, read-only comparison between your spreadsheet and the live condition tables before you upload.
Related Tools
SAP SD Rebate Agreement Request Form Template
A request form for creating a volume rebate agreement in SAP SD: who qualifies, what is measured, scale, accrual treatment and approval.
SAPSAP SD Customer Master Sales Area Load Worksheet
Collect sales area data per customer: sales org, channel, division, shipping, incoterms, payment terms and tax classification, then export to Excel.
SAPSAP SD Transaction Codes Reference
A searchable list of common SAP sales and distribution transaction codes, grouped by process area, for daily use and onboarding.
SAPSAP SD Rebate Accrual Calculator
Estimate how much rebate to accrue to date and for the full year with a retroactive threshold, then compare with what has already been settled.