SD pricing mandatory condition
Mandatory pricing condition is missing
Sales order or billing document shows a pricing error because a condition type marked mandatory has no valid value.
Quick answer
- Most likely cause
- No valid condition record exists for the pricing date and access key.
- Check first
- Pricing analysis at item level.
- First resolution step
- Use pricing analysis to identify why every access failed.
Likely root causes
- No valid condition record exists for the pricing date and access key.
- Pricing procedure includes a mandatory condition that is not applicable to the current business data.
- Customer/material master data needed by the access sequence is incomplete.
What to inspect
- Pricing analysis at item level.
- Condition type marked mandatory in the pricing procedure.
- Condition records and validity dates for the selected access.
- Customer/material pricing master data.
Resolution path
- Use pricing analysis to identify why every access failed.
- Create/correct the required condition record or source master data through pricing governance.
- Change the pricing procedure only if the business design is wrong, not to bypass one document.
- Reprice and verify net value before saving/billing.
Share this diagnosis
Paste a credited summary into a ticket, chat or forum reply. Your pasted input is never included.
ERPClimb is an independent platform and is not affiliated with SAP SE.