You can create a Database View to include both normal catalog variables and MVRS variables for RITM records, but it requires joining multiple tables since the data is stored differently.

1. Tables to include

For normal variables:

• sc_req_item
• sc_item_option_mtom
• sc_item_option
• item_option_new

For MVRS variables:

• sc_req_item
• sc_multi_row_question_answer
• item_option_new

2. Join conditions

Normal variables:

sc_req_item.sys_id = sc_item_option_mtom.request_item
sc_item_option_mtom.sc_item_option = sc_item_option.sys_id
sc_item_option.item_option_new = item_option_new.sys_id

MVRS variables:

sc_req_item.sys_id = sc_multi_row_question_answer.parent_id
sc_multi_row_question_answer.question = item_option_new.sys_id

3. Fields to select

For normal variables:

• sc_req_item.number
• item_option_new.name
• sc_item_option.value

For MVRS:

• sc_multi_row_question_answer.row_index
• item_option_new.name
• sc_multi_row_question_answer.value

4. Important points

• MVRS data is stored as multiple rows, so one RITM will produce multiple records
• Database Views do not support aggregation or pivoting
• You may see duplicate RITM numbers due to multiple rows

5. Recommended approach

If you need cleaner reporting:

• Create separate views for normal variables and MVRS, or
• Use scripts/reports to flatten MVRS data after retrieval