13: l_max hr_lookups.meaning%type;
14: l_min hr_lookups.meaning%type;
15: --
16: l_user_name ff_database_items.user_name%type;
17: l_tl_user_name ff_database_items_tl.translated_user_name%type;
18: --
19: cursor csr_tab(p_range_or_match in varchar2) is
20: select b.user_table_id,
21: b.user_table_name,
100: p_user_name in varchar2,
101: p_tl_user_name in varchar2)
102: is
103: l_user_entity_id number;
104: l_tl_user_name ff_database_items_tl.translated_user_name%type;
105: l_new_tl_user_name ff_database_items_tl.translated_user_name%type;
106: l_got_error boolean;
107: --
108: cursor csr is
101: p_tl_user_name in varchar2)
102: is
103: l_user_entity_id number;
104: l_tl_user_name ff_database_items_tl.translated_user_name%type;
105: l_new_tl_user_name ff_database_items_tl.translated_user_name%type;
106: l_got_error boolean;
107: --
108: cursor csr is
109: select u.user_entity_id
117: fetch csr into l_user_entity_id;
118: if csr%found then
119: select translated_user_name
120: into l_tl_user_name
121: from ff_database_items_tl
122: where user_name = p_user_name
123: and user_entity_id = l_user_entity_id
124: and language = 'JA';
125: --
223: end decode_glb;
224: --
225: begin
226: --
227: -- Note this only updates FF_DATABASE_ITEMS_TL with JA language.
228: -- It is not necessary to check whether the db charset is JA compliant,
229: -- because JA installation means that the DB is JA charset compliant.
230: --
231: if ja_installed and ff_dbi_utils_pkg.translations_supported('JP') then