Siebel SQLs/Error Messages > LOV SQLs
These worked well in Siebel 7.7 , I cannot be sure if these are good for vanilla Siebel functionality or it was good only for the custom Siebel environment I worked in
--List of all Global LOVs select t3.name, t3.val, t1.name, t3.type, t3.sub_type, t3.desc_text, t3.lang_id, t2.name, t3.high, t3.low, t3.order_by, t3.active_flg, t3.multi_lingual_flg, t3.translate_flg, t3.rplctn_lvl_cd from siebel.s_lst_of_val t1, siebel.s_lang t2, siebel.s_lst_of_val t3 where t3.par_row_id = t1.row_id (+) and t3.lang_id = t2.lang_cd and (t3.active_flg = 'Y' and t3.multi_lingual_flg = 'N' and t1.name is null) order by t3.type, t3.order_by, t3.val;
--MultiOrg Lovs per region per organization
select t3.name, t3.val, t1.name, t3.type, t3.sub_type, t3.desc_text, t3.lang_id, t2.name, t3.high, t3.low, t3.order_by, t3.active_flg, t3.multi_lingual_flg, t3.translate_flg, t3.rplctn_lvl_cd, t4.name from siebel.s_lst_of_val t1, siebel.s_lang t2, siebel.s_lst_of_val t3, siebel.s_bu t4 where t3.par_row_id = t1.row_id (+) and t3.lang_id = t2.lang_cd (+) and t3.bu_id = t4.row_id and t3.active_flg = 'Y' order by t4.name, t3.type, t3.val;
|