EDI Perfect PO scenario

[Former Member]

My client wants to implementing a perfect PO system in which orders would only be released after the customer submitted pricing matches exactly what we have in our system for them. The intent behind this is to mitigate the increasing number of pricing-related deductions taken by customers. Historically, our approach has been to release the orders, even if there were pricing discrepancies, in order to get them processed as quickly as possible.. It was then understood that the pricing could be addressed after the fact (either by the customer taking a deduction or we issuing an invoice adjustment). We’d now like to get in front of the issue and resolve these price discrepancies before the orders are released from Customer Service. Please let me know if anyone has mapped this kind of process. This process is solely for EDI Orders.

Thanks,

NK

[Jelena]

I'm scratching my head on how did you get into such situation in the first place. Where are the customers getting their prices? Are you not providing them with the correct quotations or price lists? I can't just show up to a local supermarket and tell them what I'm going to pay. So I'm confused...

Also I believe it's a standard functionality for the prices to be determined using pricing conditions, as GL pointed out correctly. In the EDI scenarios, the customer desired price only comes in as an EDI condition (ED1, think), which is merely FYI.

There is a lot of information available online about the EDI processes, as well as several books. Kindly search first and then ask more specific questions.

[Lakshmipathi]

Ideally, before creating sale orders, the related master data should have been created which includes condition record for pricing. This being the case, whether it is an EDI orders or manually created orders, pricing discrepancy should not happen as I presume, no manual pricing is there in your pricing procedure. Still if you want to have some approval process, you need to explore Workflow functionality.