Table structure for a more efficient dashboard

[Cyrilbrd]

This is a question about table structure:
What would be the most efficient way to organise data in order to extract sales versus target for multiple shop belonging to various companies.

How would you organise your tables with the following existing restrictions:
1-Your sales data would come from a live source with details such as and not limited to:
Sales number, Name of Shop, Name of company, Date of transaction, amount, designation of item sold ect.
2-You would as well have a master list that would give you for each company, each location the sales target per month per year.

How would you organise these two (or more if you include date table or other) tables, what relationship would you create to be able to extract sales versus target for any company and having this dynamically evolve with the current date.

What would be the better (organised) way to have these as related tables.

Again I am not imposing an existing dataset, on the contrary I am asking you what would be the best method to follow in terms of data, table structure, relationship and measure to extract the required KPI.

[Cyrilbrd]

@VijayP thank you for your reply but I would tend to disagree. Yes variations may exists but in a nutshell and regardless of your geography, sales versus target remains a simple KPI.
Although keeping data in a single table could be done backend at the server level, I am sure that other users might use different sources.
I appreciate your feedback.

[VijayP]

@Cyrilbrd 

You must normalise the Data and keep in single table ( if in case of multiple tables - using combine option)

Rest depends upon your business problem statement. There is no speicifc yard stick applicable for all reports