PDA

View Full Version : Copy Data Button / Building a Pricing Matrix


ABC123

newbee
12-17-2013, 05:35 PM
Hi,

I would like to create a button that copies default data from one table [Pricing Matrix] (stand alone) to a child table of Contractor Called Pricing [Contractor]->[Pricing]. In the [Pricing Matrix] there are {Item, Unit, Price, Branch, etc.} there are a total of 4 branches so in effect the same item could have 4 different prices. (Coping the data would allow us to enter a new contractor faster)

When in a Contractor that has a branch set to (FX) as an example I want to be able to push a button that will generate/copy all the default pricing for all items in that branch over to [Contractor]->[Pricing] then I want to be able to make final adjustments to the pricing from there.

I just can't figure out what to do to be able to copy that group of default prices over to that table so we don't have to physically go in and enter each item in individually. I have tried append but I just don't know the syntax to copy based off a filter. Or that may not be the best way.

Once the default pricing is copied in I then have fields you can put the desired price that exists locally in the [Pricing] table that will calculate based off the main [Pricing Matrix] I did that to try to make it easy to update pricing as needed.

Any suggestions would be appreciated maybe I need a different approach? The problem is every contractor has different pricing, pricing is all individually negotiated.

Anyone??? Thanks Ahead of time.

Ray in Capetown
12-18-2013, 01:33 PM
YOU want to create a stock table for each contractor? Each containing the items for one (of four) branches, filtered according to the branch code of the contractor?
Pretty basic. If that is in fact what you want.
My suggestion;-

Use a COPY operation to prepare one.
Then save the code that you can re-use from a button, supplying the contractor-name of the pricelist.

Are you familiar with any or all of that? See how far you get - then ask.

Ray in Capetown
12-18-2013, 01:43 PM
I wouldn't use such a design. End up with a separate table for every contractor.
I have had in use for more than a decade, a customer /product /price exception matrix table. a linear table indexed on Customer/product. Where the branch price for a customer (contractor) is acceptable your system uses that if there is no exception entry in the matrix table
You also need to consider the complexity of cost price adjustments,
my 2c worth.

newbee
12-18-2013, 03:25 PM
Thanks for the input. The fact that the price is different for each contractor is what is tough. basically you could think of it as stock pricing and each contractor has there won multiplier but that multiplier is different for each item. I am not as concerned with updates since I could write a script to take care of it but ideally I would like it to pull static info from one table in to the contractor then have an area were we can modify the price then they have the final cost to them. This way in the parent list I could just update something by .01 and it would flow through to the contractors but I just can not figure out the layout to make it simple enough....???