When it comes to processing inbound EDI sales orders in SAP (typically via ORDERS05 IDocs), pricing is one of the key failure points.

If the price sent by the customer doesn’t match what SAP calculates internally—or if essential pricing data is missing altogether—the result can be incomplete orders or incorrect pricing commitments to your customer. This disrupts automation, triggers manual intervention, and delays fulfillment—ultimately impacting customer satisfaction.

Let’s break down what needs to happen for a smooth ordering process.

Customer-Sent Pricing: EDI1 and EDI2 Conditions

SAP provides two statistical condition types to capture the customer’s expected price during IDoc processing:

• EDI1 – Expected gross price
• EDI2 – Expected net price

These conditions don’t determine the final price in SAP but serve as reference points for validation.

How They Are Used

• If the EDI1/EDI2 values differ from the price SAP calculates using condition records, the order may trigger incompletion logs. The acceptable difference is configurable—you can require an exact match or allow a tolerance based on a dollar value or percentage.
• If the pricing segment is missing entirely, the order might fail outright, depending on your incompletion procedure.

Best Practice

Map the price sent by the customer to EDI1 and/or EDI2 by populating E1EDP05-KRATE with KSCHL = EDI1 or EDI2.

Don’t force it as the system price. This approach keeps your SAP pricing logic intact while allowing SAP to validate expectations and raise warnings if needed.

Additional Pricing Considerations

When bringing in product pricing, you must also account for additional charges or discounts such as taxes, freight, off-invoice discounts, bulk discounts, and more. These typically arrive on the EDI order with a specific qualifier or code and need to be mapped to pricing conditions in SAP.

The EDI team should work closely with the business to understand and map these codes for proper pricing determination in SAP.

Key Factors That Drive Price Determination

• Sold-to / Ship-to customer
• Material number
• Pricing date
• Customer-specific agreements and price lists

If a condition record isn’t found for the combination of customer, material, and date, a manual order (VA01) may show as incomplete—while an IDoc order may fail to post entirely, with errors like: Pricing error: Mandatory condition PR00 missing.

Getting this right doesn’t just avoid errors—it builds trust with your customers by delivering accurate, timely order confirmations that match their expectations.