Answer
Yes — build the Quick Report as a SQL query joining History_Log to History_Log_Attribute (aggregating each log entry's individual field changes into one combined description per change record using LISTAGG, formatted as 'Column: From {old} to {new}'), filtered by the specific Module, LU_Name, and Table_Name you're interested in, plus a date range on History_Log's own timestamp. Since History_Log's own Keys column stores the record's key values as a single delimited string rather than separate columns, use REGEXP_SUBSTR to pull out the specific key components you need (for example, extracting a Supplier ID or Company value out of that combined Keys string) so you can join back to the relevant master data (like Supplier_Info) for a readable name rather than just a raw ID. This general pattern — History_Log plus History_Log_Attribute joined with LISTAGG, and REGEXP_SUBSTR to parse the Keys column — works for building a history-log Quick Report against any LU's logged changes, not just one specific one, once you adjust the Module/LU_Name/Table_Name filters and the specific key positions you extract.