DBA Data[Home] [Help]

APPS.HR_JP_STANDARD_PKG dependencies on HR_API

Line 348: if p_replacement_chr is null or p_replacement_chr <> hr_api.g_varchar2 then

344: l_new_str := substr(c_hankaku.voiced_kana, i * 2 - 1, 2);
345: l_str := replace(l_str, l_old_str, l_new_str);
346: end loop;
347: --
348: if p_replacement_chr is null or p_replacement_chr <> hr_api.g_varchar2 then
349: if not is_hankaku(l_str) then
350: --
351: -- In most cases, length(l_src) will be very small number,
352: -- which will not cause performance issue.

Line 397: return to_hankaku(p_chr, hr_api.g_varchar2);

393: function to_hankaku(
394: p_chr in varchar2) return varchar2
395: is
396: begin
397: return to_hankaku(p_chr, hr_api.g_varchar2);
398: end to_hankaku;
399: -- |---------------------------------------------------------------------------|
400: -- |------------------------------< to_zenkaku >-------------------------------|
401: -- |---------------------------------------------------------------------------|

Line 441: if p_replacement_chr is null or p_replacement_chr <> hr_api.g_varchar2 then

437: c_zenkaku.upper_kana ||
438: c_zenkaku.lower_kana ||
439: c_zenkaku.jp_symbol);
440: --
441: if p_replacement_chr is null or p_replacement_chr <> hr_api.g_varchar2 then
442: if not is_zenkaku(l_str) then
443: --
444: -- It is very rare case to get into this if statement,
445: -- so we can ignore the performance.

Line 481: return to_zenkaku(p_chr, hr_api.g_varchar2);

477: function to_zenkaku(
478: p_chr in varchar2) return varchar2
479: is
480: begin
481: return to_zenkaku(p_chr, hr_api.g_varchar2);
482: end to_zenkaku;
483: -- |---------------------------------------------------------------------------|
484: -- |------------------------------< upper_kana >-------------------------------|
485: -- |---------------------------------------------------------------------------|