RITM report with all variables and approval details in single report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 05:57 AM
Hi All,
We have a requirement to pull a report of all RITM's and its associated variables and approval details in one single report. Is that possible, if yes from which table we need to run that report.
Any guidance on this matter is much appreciated.
regards,
Raghesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 07:10 AM
@Raghesh All variable details you can get from sc_req_item table using variable field but approval is stored in diffrent table so you will have to create a view to join all data together.
But all variables and approval with rest to a RITM i don't think there is any table OOB.
Hope this will help you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2023 04:38 AM
Thank you for your inputs.
Is there any article or can you share the steps for defining a DB view with RITM and Approval table.
I am not familiar with DB views configuration.
regards,
Raghesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2023 04:59 AM - edited 04-07-2023 05:01 AM
@Raghesh ,
Create a database view like mentioned below:
where clause:
approval.sysapproval = ritm.sys_id |
And then create a report by choosing the database view as mentioned below:
You will get the fields from both the tables.
If my answer solved your issue, please mark my answer as ✅Correct & 👍Helpful based on the Impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2023 05:42 AM
Thank you for the screen shots.
I have followed same steps however not getting the "Variables" option to select the variables of the RITM into the report.
On left hand side it is not visible.
What could be the reason.
regards,
Raghesh