Report on Service request SLA

Atchutaram
Tera Contributor

Hi Experts,

Good Day!

                        I have been trying to generate a report on Service Request SLA. where SLA's are attached to our RITM.

I am generating report on task_sla table but unable to get.

 

Can i generate a report on this SR's where i can see Request number and tasks number associated it?

 

Could you please assist me with this.

 

Best Regards,

Atchut ram

1 ACCEPTED SOLUTION

ronprice
Giga Guru

You can create a report that filters for a specific Item, and pulls in additional information from parent records (RITM and Request) by dot-walking.  In the screenshot below, the report is based on task_sla, and then the task [+] field was expanded to show all fields available from any kind of task record related to task_sla.  By doing this, you can access the Item field and the Request field from the RITM.  However, assuming that your SLAs are attached to the RITM and not the catalog tasks, you cannot also pull in the sc_task information.  If you need to do this, you will need to create a database view that ties together the Request, Requested Item, Task SLA, and Catalog Task tables.

ronprice_0-1681146607156.png

 

Please mark as correct/helpful if this answered your question.

View solution in original post

1 REPLY 1

ronprice
Giga Guru

You can create a report that filters for a specific Item, and pulls in additional information from parent records (RITM and Request) by dot-walking.  In the screenshot below, the report is based on task_sla, and then the task [+] field was expanded to show all fields available from any kind of task record related to task_sla.  By doing this, you can access the Item field and the Request field from the RITM.  However, assuming that your SLAs are attached to the RITM and not the catalog tasks, you cannot also pull in the sc_task information.  If you need to do this, you will need to create a database view that ties together the Request, Requested Item, Task SLA, and Catalog Task tables.

ronprice_0-1681146607156.png

 

Please mark as correct/helpful if this answered your question.