2022: Week 30 C&BSCo Actual Sales Values

 Created by: Carl Allchin

Welcome to the final week of beginners' month in July. 

Chin & Beard Suds Co (C&BSCo) have been recording the percentage contribution of the top 3 sales people in each of their stores. They want to know how much value this actually equates to. This week's challenge will let you experience one final technique we haven't used this month yet, Unions. 

Here's more support with Unions if you are new to them:

Input

There are four files you will need to input this week. 

There are two inputs for Sales Data in each of our Regions (East and West). They are the same structure of data fields:

The third file is a Store ID lookup table:

The fourth file is same as the original input for Week 27:

Requirements

  • Input the 'Top 3 Sales People per Store' for both regions: East & West
  • Combine these files
    • Bonus challenge for experienced Preppers - take the Region Name from the File Name. For newer Preppers, use the Region name field from the Week 27 Input later in the challenge
  • Input the 'Store Lookup' file to provide the name of the Stores instead of the ID number
  • Remove any duplicate fields you have in the data set so far
  • Input the Week 27 Input file
  • Use Week 27 Input file to create Sales Values for each Store
  • Combine this data with the rest of the prepared data
  • Use the data set you have created to determine the actual sales value (rather than percentage) for each sales person
    • Multiply the Sales Person percentage contribution against their Store's total sales for the year
  • Output the data (removing any remaining duplicated fields)

Output

One file:

6 data fields:
  • Sales per Person
  • Store Name
  • Region
  • Sales Person
  • Percent of Store Sales
  • Sales Value
18 rows (19 rows incl. headers)

Note: Tableau Prep is very detailed with it's decimal places, if you use a different tool, slightly different rounding is fine

You can download the full output here. 

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @Datajedininja, @JennyMartinDS14 & @TomProwse1

You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help! 

Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more