To generate any report you can just use SQL queries on the schedulix repository database.
Use the SCI_... views which decode values and transform unix timestamps into data types.
Most of the colum names are self explaining if you have a look at the API syntax.
Foreign keys have the format <abrivation>_id for example esd_id -> id of exit_state_definition.
Version objects have two views names SCI_C_... SCI_V_...
SCI_C_... views contain the current definition, SCI_V... views contain all versions with addition attributes VALID_FROM and VALID_TO
So SCI_SUBMITTED_ENTITY contains all instances for submitted batches and jobs.
To correctly join SCI_SUBMITTED_ENTITY with versioned objects like exit state definition you have to use an additional condtion utilising the SE_VERSION_ID.
Example:
Generate a report of all master submitted entities with their name, start_timr, end_time and their exit state you can use the following query:
sme.start_ts,
sme.finsh_ts,
from SCI_SUBMITTED_ENTITY sme,
SCI_V_SCHEDULING_ENTITY se,
SCI_V_EXIT_STATE_DEFINITION esd
and sme.se_version >= se.valid_from
and sme.se_version < se.valid_to
and sme.se_version >= esd.valid_from
and sme.se_version < esd.valid_to;
When issuing the query from sdmsh (user logged in must be member of group admin) you can issue the query as:
sme.start_ts,
sme.finsh_ts,
from SCI_SUBMITTED_ENTITY sme,
SCI_V_SCHEDULING_ENTITY se,
SCI_V_EXIT_STATE_DEFINITION esd
and sme.se_version >= se.valid_from
and sme.se_version < se.valid_to
and sme.se_version >= esd.valid_from
and sme.se_version < esd.valid_to
with se_id folder;
the with se_id folder will convert the se_id into the full path_name of the scheduling entity;