Customer expected price condition type EDI1

[KVKUMAR]

Hi All, I am working on the customer expected price condition type EDI1. I have created a sales order and it has normal price with PPR0 condition type. I have entered the customer expected price condition type EDI1 manually and entered some price less than the price of PPR0. system showed incomplete document due to price difference, when I save the sales order.  After this I went to Fiori app Manage Sales documents with Customer expected price and in the sales order I have clicked on Accept customer price button as shown in the below screen shot and observed that system is not replacing the actual price with expected customer price. am I missing some settings or is this standard behavior. Do we need to change the price manually.? Please guide.  

Thanks

Kumar

[MOHAMMED_BASER · Accepted solution]

Hi @KVKUMAR ,

That's correct, this is standard behavior. The condition type EDI1 (Customer Expected Price) is a statistical condition in SAP. It does not replace the actual pricing condition (like PPR0). The "Accept customer price" action in the Fiori app only acknowledges the discrepancy but does not overwrite the system-calculated price. If you want to use the customer’s expected price as the actual price, you must adjust the pricing manually or configure a custom routine to copy EDI1 into the main price condition.

The reason EDI1 behaves this way because, EDI1 is statistical: SAP defines EDI1 (expected gross price) and EDI2 (expected net price) as statistical conditions. They are used to capture what the customer sent in their EDI order, but they don’t determine the final billing price. The system compares EDI1 against your calculated price (e.g., PPR0). If there’s a difference, the document is flagged as incomplete so you can review it.

Fiori "Accept customer price": This button acknowledges the customer’s expected price in the workflow but does not automatically replace the system price. It’s designed to help avoid disputes, not to override pricing logic
You’re not missing a setting—EDI1 is not meant to overwrite actual pricing. If your business requires that behavior, you’ll need a custom enhancement or manual intervention. Would you like me to walk you through how to configure an alternative calculation routine so that EDI1 can replace PPR0 automatically, or would you prefer to explore tolerance-based acceptance where small differences are auto-approved? configure alternative calculation routine for EDI1, set tolerance checks for customer expected price