This content has been marked as final. Show 4 replies
The audit trail normally would work for price changes too (after all they are stored in a table). But you would have a problem if the user changes the default price BEFORE saving.1 person found this helpful
In your case, it might be simpler to write a report that shows all newly created lines with a price different than the list price.
Nirabh,1 person found this helpful
Did you say you update the List Price itself in the Order Lines? In my opinion you should never update List Price. Set the profile OM: Discounting Privilege to 'Unlimited' to allow update of Selling Price, but switch off 'OM: List Price Override Privilege' for the responsibilities so that List Price field is not Editable. So that List Price always reflect the price with which Order Line was created (From the price List). Now create a custom report wherever Unit Selling Price does not match Unit List Price.
If you really want to go a little further then create a modifier with Application method 'New Price' that should kick in everytime the Unit Selling Price is updated. Let me know if that helped.
Edited by: Dipanjan Maitra on May 25, 2012 2:25 PM
I am opting for the change in selling price keeping the list price intact. Modifier option doesn't seem to be feasible as they don't have fixed way of arriving new price so we need to opt for manual modifiers. Generally, they have aroud 30 + lines on SO, they will have to manually apply price adjustments on all lines. The direct updating of Selling price seems to be a viable option, I feel.
Anyway, thanks a lot.
With Best Regards,