Capture the price valiance of Sales order price and applicable sales prices

I’ve attached a sample version of our price discrepancy GI to illustrate the joins. I’ve been using variations of this GI for years for reports and business events. There are probably better ways to do this, but it’s worked for us and our pricing model. This does not cover break quantities and how you and your customers handle discounts can also add some complications.

The GI is essentially joining SOLine to ARSalesPrice multiple times - the goal is to provide the necessary data to build out the sales price priority system (Customer > Customer Price Class > Base). Once you have the individual prices, you can then compare what was provided on the PO against the “system” price and trigger notifications, order holds, and other fun business events.

We enter all customer orders at the customer’s PO price (typically from the SPS integration, some manual order entry). From there we have a chain of business events and automation schedules that use this logic to determine if there is a pricing issue. If there’s no issue, the order is released from hold. If a discrepancy is found, it updates an attribute on the order explaining why and will then send an email to customer service to let them know what the discrepancy is.