Pie charts are casting judgement on my DB structure...

I've got a table in my database that stores employee payroll information by month. The table has an employee column, month column, and one column for each type of time that we track (standard time, vacation time, sick time, overtime, etc.).

When I pulled this data into Yellowfin I started building a report that would allow me to aggregate our time measures across employees, months, or both. When I went to generate a pie chart to show the proportion of the different kinds of time, I learned that the Yellowfin pie charts only accept one metric/dimension for "size" and one metric for "color". In other words, to get this pie chart to work I would have to restructure my database table to have four columns: employee, month, time type (standard, overtime, sick, etc.), and a time amount field. Then I could choose time type as my color metric and time amount as my size.

Alternatively I suppose I could switch my view to freehand SQL and do this massaging there, but all the Yellowfin material I've read has advised against freehand SQL since that diminishes Yellowfin optimizations...

Any advice?