We have about 12000 ProductIDs in our database but only about 2000 unique ManufacturerPartNumbers. In other words many of our "Product" pages share the same ManufacturerPartNumber and therefore share the same price. In our case it would be much easier to manage the ExtendedPrice by ManufacturerPartNumber instead of VariantID.
I have an idea on how to make this work but am looking for some input before proceeding:
I have found the Scalar-Valued Function dbo.GetCustomerLevelPrice. We would start by modifying the ExtendedPrice table to include ManufacturerPartNumber. We would then replace the references in the Scalar-Valued Function from VariantID to ManufacturerPartNumber.
I understand this mod may affect our ability to manage the extended pricing from the admin site. Any other issues this may cause? Are there any other files or stored procedures that would need to be modified?