2023: Week 35 - HR Month - Transfers

 Challenge by: Kelly Gilbert

Validated by: Charalambos Pavlou

Occasionally, employees may want to transfer from one distribution center to another (for example, if the employee wants to move to a different city). The company doesn’t have a consistent policy or process for that. The HR manager has asked us to figure out how often it happens, so the HR team knows if they should prioritize working on that policy.

Our HR recording system has a few issues, so we’ll need to make some assumptions for this analysis.

Input

The DC/month assignments from Week 33 (ee_monthly_v4.csv)

Requirements

  • Input the data
  • Flag when transfers occurred:
    • A transfer occurs when the employee’s dc_nbr changes from month to month, and the difference in months is <= 2.
      • Our HR system doesn’t differentiate between an employee transferring from one DC to another vs. the employee quitting and then being rehired at another DC later, so we are going to make the assumption that if the gap is no more than two months, it was a transfer
      • For example, if an employee worked at DC #1 in May, did not work in June, then worked at DC2 #2 in July, that would count as a transfer
      • Make sure to flag the transfer in the month that the employee left the old DC (NOT the month the employee started working at the new DC)
  • For each DC, calculate:
    • The count of unique employee_ids present for all history. Name this ee_count
    • The total number of transfers. Name this xfer_count
    • The percentage of employees who transferred. Name this xfer_pct and format with two decimal places (e.g. 33.35% = 35.35)
    • The average tenure (in months) for employees that transferred. Name this avg_tenure_months and format with two decimal places
  • Include a total row, with the totals across all DCs
  • Output the data

Output


  • 6 fields
    • dc_nbr
    • ee_count
    • xfer_count
    • xfer_pct
    • avg_tenure_months
  • 7 rows (8 including headers)
After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @kelly_gilbert, @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