eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PAY_IP_RULES dependencies on PAY_ACTION_INFORMATION

Line 32: l_data pay_action_information.action_information1%type;

28: PROCEDURE LOAD_XML (
29: P_XML varchar2
30: ) AS
31: l_proc_name varchar2(100);
32: l_data pay_action_information.action_information1%type;
33:
34: BEGIN
35: l_proc_name := g_proc_name || 'LOAD_XML';
36: hr_utility_trace ('Entering '||l_proc_name);

Line 53: l_data pay_action_information.action_information1%type;

49: P_NODE varchar2,
50: P_DATA varchar2
51: ) AS
52: l_proc_name varchar2(100);
53: l_data pay_action_information.action_information1%type;
54:
55: BEGIN
56: l_proc_name := g_proc_name || 'PREPARE_XML';
57: hr_utility_trace ('Entering '||l_proc_name);

Line 297: lv_gre_name pay_action_information.action_information1%type;

293:
294: ln_legal_employer_id number;
295: l_employer_xml char_tab;
296: ld_effective_date date;
297: lv_gre_name pay_action_information.action_information1%type;
298: lv_trans_gre_name pay_action_information.action_information1%type;
299: lv_paternal_last_name pay_action_information.action_information1%type;
300: lv_employee_name pay_action_information.action_information1%type;
301: lv_location_id pay_action_information.action_information1%type;

Line 298: lv_trans_gre_name pay_action_information.action_information1%type;

294: ln_legal_employer_id number;
295: l_employer_xml char_tab;
296: ld_effective_date date;
297: lv_gre_name pay_action_information.action_information1%type;
298: lv_trans_gre_name pay_action_information.action_information1%type;
299: lv_paternal_last_name pay_action_information.action_information1%type;
300: lv_employee_name pay_action_information.action_information1%type;
301: lv_location_id pay_action_information.action_information1%type;
302: l_proc_name varchar2(100);

Line 299: lv_paternal_last_name pay_action_information.action_information1%type;

295: l_employer_xml char_tab;
296: ld_effective_date date;
297: lv_gre_name pay_action_information.action_information1%type;
298: lv_trans_gre_name pay_action_information.action_information1%type;
299: lv_paternal_last_name pay_action_information.action_information1%type;
300: lv_employee_name pay_action_information.action_information1%type;
301: lv_location_id pay_action_information.action_information1%type;
302: l_proc_name varchar2(100);
303: lv_userdefined_proc_er varchar2(150);

Line 300: lv_employee_name pay_action_information.action_information1%type;

296: ld_effective_date date;
297: lv_gre_name pay_action_information.action_information1%type;
298: lv_trans_gre_name pay_action_information.action_information1%type;
299: lv_paternal_last_name pay_action_information.action_information1%type;
300: lv_employee_name pay_action_information.action_information1%type;
301: lv_location_id pay_action_information.action_information1%type;
302: l_proc_name varchar2(100);
303: lv_userdefined_proc_er varchar2(150);
304: lv_userdefined_proc_ee varchar2(150);

Line 301: lv_location_id pay_action_information.action_information1%type;

297: lv_gre_name pay_action_information.action_information1%type;
298: lv_trans_gre_name pay_action_information.action_information1%type;
299: lv_paternal_last_name pay_action_information.action_information1%type;
300: lv_employee_name pay_action_information.action_information1%type;
301: lv_location_id pay_action_information.action_information1%type;
302: l_proc_name varchar2(100);
303: lv_userdefined_proc_er varchar2(150);
304: lv_userdefined_proc_ee varchar2(150);
305: