A superdat can be used to update many things, not just a dat or engine. To build your report, you need to know what exactly is being updated. If you are using a standard superdat that updates the dat and engine, then your report needs to be built on the dat/engine versions. To show the progress of such an update, I would do a report on managed systems, with a boolean pie chart where the "compliant" criteria would be the dat and engine version in the superdat. Any system that did not have the correct versions would be Non-compliant. As your update progresses, the compliant slice of the pie should grow while the other slice shrinks.
Hope that helps...
Could you clarify if you are looking for Extra.DAT saturation or SDAT saturation? An SDAT is just a combination of the DAT file and the latest engine which you can create individual reports for. If you are looking to create an ExtraDAT saturation report, the Extra DAT version is an available column under VirusScan Enterprise Properties during custom query creation.
No need to build two separate reports for engine and dat versions... you can do a single report to show systems that meet both criteria with a boolean pie chart.