product entity is used for all things the one deviation is supplier products. I say deviation because that is not the way Data model book does it. also ProductPrice.productPricePurposeId and ProductPriceChange.productPricePurposeId define what the price is used for, like purchase. you can find these out by useing webtools look at the entity then look at the relationship. you can click on view relationship then name in the related Entity column. so you will have to change the ProductPrice that are linked to the product in the order item.
========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> James McGill sent the following on 4/21/2010 4:21 PM: > On Wed, Apr 21, 2010 at 3:35 PM, BJ Freeman <[email protected]> wrote: > >> there is a eca for prices change that tracks those. >> see ProductPriceChange entity view it in the atrifact. >> > > That would be from a Product perspective, where we don't want to change the > price. > We only want to adjust the price for a given receipt, and only after the PO > is "COMPLETED" > but wouldn't ProductPriceChange affect catalogs and all other PO's? > > That's why I want to actually add Items to an existing PO, so that I have > traceability to the original order, > the original receipt, and the adjustments, separately. If I just change the > price on the product, or just change > the price on an OrderItem and InventoryItem, I've lost traceability, right? > > (Our problem is related to some very particular business logic that applies > to aircraft parts -- there > are a lot of things we do that won't fit other shops) >
