Audit packages reverted from production

Summary: List all packages installed in production for a while and reverted afterwards.

About such packages:

• they have a status which is NOT baseline rippled (BAS) anymore, combined with a none-blank baseline ripple date (reflecting the date/time the package was in status BAS, i.e. when the package was operational in production environments). Typically such packages have a status of BAK or DEV (depending on additional package actions that may have been  performed after a backout was performed).
• The backout (BAK) date/time for each site indicates until when the package has been active in the selected site (i.e. the time between package status INS eand BAK).
• After the package was backed out, it may (optional!) have been reverted to DEV again at one or more sites (reflected by the revert date/time for each site).
• After each site performed a revert to DEV, the package will (automatically, without any human inervention) become in DEV status again, after which it is allowed/possible to perform any component updates again to such package, such as component updates, checkout other components, delete components from staging, etc. Optionally, the package status may then change again to FRZ, APR, DIS, INS and BAS) and this in a timespan of a few minutes or a few days / weeks / months.
• This may lead to situations where some (versions of) components have been in production 'for a while' (= time between BAS date and last revert to DEV date), but for which the exact version is no more contained in any CMN/ZMF staging library, baseline or production library.

IT auditors don't really like such scenario's ... which is why it might be a good idea to only perform a revert to DEV (which requires a special CMN/ZMF authorization ...) after somebody first reviewed the package content of all backed out packages waiting revert.