Hi, Nilesh.
It's not an issue
In my scenario there's no any "preset" DSO. Create an ADSO and change settings in it (switch template, change field properties etc) in order to only map graphical settings to xml attributes (this is exactly what I've done in previous post). It will be just an investigation of corresponding xml. You can do it for one ADSO, after it you'll know what xml you should generate, because you will understand how settings will be presented in xml. Then create your DSO "structure" (as an xls table like <dsoname, fieldname, fieldtype, iskey, isinfoobject> or some modeling tools like PowerDesigner, ERWin etc) and generate xml from this structure.
Hope I was clear.
Regards,
Andrey.