Difference Between Condition Types EK01 (Actual Cost) and EK02 (Calculated Cost)

In SAP pricing, EK01 and EK02 are critical condition types used in cost-based pricing within sales documents. These condition types help businesses determine the cost price of a material, ensuring accurate price calculations and profitability analysis.

Understanding the differences between EK01 (Actual Cost) and EK02 (Calculated Cost) is essential for configuring SAP pricing effectively.

What is EK01 (Actual Cost)?

EK01 represents the actual cost derived from unit costing and is directly applied in the price determination process.

Key Features of EK01:

  • Price Determination: The unit costing result is transferred as a real price condition in the first position of the conditions screen.
  • Final Price Impact: The actual cost calculated is included in the final price of the sales order.
  • Use Case: Typically used when the unit costing should directly influence the sales price calculation.

Example Scenario for EK01:

A company sells customized machinery, and each unit’s production cost varies. By using EK01, SAP ensures that the actual cost of production is factored into the final sales price.

What is EK02 (Calculated Cost)?

EK02 represents the statistical cost, meaning it is only used for reference and does not affect the final price.

Key Features of EK02:

  • No Impact on Price: The cost appears in the pricing screen for analysis but does not alter the final sales price.
  • Statistical Purpose: Used when a company wants to compare costs but not include them in the price calculation.
  • Use Case: Ideal for businesses that want to track cost calculations for reporting or profitability analysis without impacting customer pricing.

Example Scenario for EK02:

A manufacturing company wants to track material and labor costs without affecting the customer’s final price. EK02 provides visibility into the costs while keeping pricing strategies intact.

Key Differences Between EK01 and EK02

Condition Type Purpose Impact on Pricing Best Used For
EK01 Actual Cost Affects price determination When unit costing should determine the price
EK02 Statistical Cost Does not affect final price When cost is only for analysis and comparison

Troubleshooting: Excluding K007 Discount for Two Orders

If the K007 discount is still applied despite setting the exclusion indicator, consider these troubleshooting steps:

1. Change the Validity Period of K007

  • Navigate to VK12 (Change Condition Record).
  • Adjust the validity period so that K007 is not active during the period covering the two orders.

2. Check Pricing Procedure & Condition Exclusion Settings

  • In V/08 (Pricing Procedure), ensure that condition exclusion logic is configured correctly.
  • If a requirement is assigned in the pricing procedure for K007, it might be overriding the exclusion indicator.

3. Manual Exclusion in the Sales Order

  • If automatic exclusion fails, manually remove K007 in the pricing screen during sales order creation.

Conclusion

Understanding the difference between EK01 and EK02 is crucial for SAP users dealing with cost-based pricing. EK01 ensures that the actual cost influences the final price, while EK02 is used for analysis without affecting price determination.

By configuring pricing conditions correctly and troubleshooting discount exclusions, businesses can optimize their SAP pricing strategy for better profitability and cost control.

Related SD Queries:

Get help for your SAP SD problems
SAP SD Forums - Do you have a SAP SD Question?

SAP Sales and Distribution Books
SAP SD Books - Certification, Interview Questions and Configuration

SAP Sales and Distribution Tips
SAP SD Discussion Forum and Sales/Distribution Tips

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.