When an order item is created for a Purchase Order, its' description
is set to "${supplierProductId} - ${supplierProductName}". When talking to external systems and when creating custom PDFs, I need to access these values separately. Right now I use two order item attributes (supplierProductId and supplierProductName), but I am trying to reduce the number of our customizations. Would there be any objections to creating a new field "supplierProductId" on the OrderItem entity and using that when creating POs, leaving the order item description as the supplier's product name? smime.p7s (5K) Download Attachment |
Data model book Vol I page 126 calls out an PO Item and a Salesorder 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 <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Joe Eckard sent the following on 4/13/2010 12:14 PM: > When an order item is created for a Purchase Order, its' description is > set to "${supplierProductId} - ${supplierProductName}". > > When talking to external systems and when creating custom PDFs, I need > to access these values separately. Right now I use two order item > attributes (supplierProductId and supplierProductName), but I am trying > to reduce the number of our customizations. > > Would there be any objections to creating a new field > "supplierProductId" on the OrderItem entity and using that when creating > POs, leaving the order item description as the supplier's product name? |
In reply to this post by Joe Eckard
also
Data model book Vol I Page 107 calls out sales order line item and purchase order line item as reveferencing the Product. you will note on page 82 that the supplierProduct does not cover a product but additional information related to the supplier. However ofbiz has information in the supplierproduct that is from the product entity. so now we run into the problem so the question is do we get the datamodel correct or do we kluge ========================= 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 <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> BJ Freeman sent the following on 4/13/2010 1:01 PM: > Data model book Vol I page 126 calls out an PO Item and a Salesorder 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 > <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> > > > Joe Eckard sent the following on 4/13/2010 12:14 PM: >> When an order item is created for a Purchase Order, its' description is >> set to "${supplierProductId} - ${supplierProductName}". >> >> When talking to external systems and when creating custom PDFs, I need >> to access these values separately. Right now I use two order item >> attributes (supplierProductId and supplierProductName), but I am trying >> to reduce the number of our customizations. >> >> Would there be any objections to creating a new field >> "supplierProductId" on the OrderItem entity and using that when creating >> POs, leaving the order item description as the supplier's product name? > > > |
Free forum by Nabble | Edit this page |