This is a weird discussion. Here's the result of my guesswork.
QlikView is a capable ETL tool that easily reads data in various formats and databases. Some manual work is still necessary however when attempting to read novels, tax forms, license plates and source code. Your example contains only four groups of setting so I took the time to manually convert them into something QlikView can understand. See attachments.
If in reality there are many more groups in the ruby source, you may consider writing a tool in a general purpose scripting language (like perl) to process groups of values into comma-separated lines.
Note that the ruby code is a little bit inconsistent. The last value is stored in a variable alternately called r_name or retailer_name.
Thanks for help and Its a typo mistake,retailer_name is correct.
i don't have idea how ruby file is converted to csv or excel.
its a regular update we need from ruby file.
Well, the attachment is only an example of what to feed into QlikView.
If you need updates on a regular basis, that means that someone or something is updating the ruby code on a regular basis as well. These updates can be done anywhere (csv, ruby program, database table) as long as you don't have to do them twice and in different places. As far as I can see with limited information, you have two options to handle this quickly:
But keep in mind that the QlikView script engine is no parser construction toolkit.