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_JP_ENTRIES_PKG dependencies on PAY_ELEMENT_ENTRIES_F

Line 42: g_old_rec pay_element_entries_f%ROWTYPE; -- Global record definition

38: -- Current Element Entry Row Hander "pay_ele_shd" does not comply with API
39: -- strategy. "pay_ele_shd" is like API, but not API. So this package
40: -- used in PAYJPTAX form implement part of real API to use DTCSAPI library.
41: --
42: g_old_rec pay_element_entries_f%ROWTYPE; -- Global record definition
43: g_package varchar2(33) := ' pay_jp_entries_pkg.'; -- Global package name
44: --
45: -- ----------------------------------------------------------------------------
46: -- |------------------------< element_name >----------------------------------|

Line 707: l_entry_type pay_element_entries_f.entry_type%TYPE;

703: Is
704: --
705: l_proc varchar2(72) := g_package||'find_dt_upd_modes';
706: --
707: l_entry_type pay_element_entries_f.entry_type%TYPE;
708: l_processing_type pay_element_types_f.processing_type%TYPE;
709: --
710: Cursor C_Sel1 Is
711: select pee.entry_type,

Line 715: pay_element_entries_f pee

711: select pee.entry_type,
712: pet.processing_type
713: from pay_element_types_f pet,
714: pay_element_links_f pel,
715: pay_element_entries_f pee
716: where pee.element_entry_id = p_base_key_value
717: and p_effective_date
718: between pee.effective_start_date and pee.effective_end_date
719: and pel.element_link_id = pee.element_link_id

Line 752: p_base_table_name => 'pay_element_entries_f',

748: -- Call the corresponding datetrack api
749: --
750: dt_api.find_dt_upd_modes
751: (p_effective_date => p_effective_date,
752: p_base_table_name => 'pay_element_entries_f',
753: p_base_key_column => 'element_entry_id',
754: p_base_key_value => p_base_key_value,
755: p_correction => p_correction,
756: p_update => p_update,

Line 784: l_entry_type pay_element_entries_f.entry_type%TYPE;

780: l_proc varchar2(72) := g_package||'find_dt_del_modes';
781: --
782: l_parent_key_value1 number;
783: l_parent_key_value2 number;
784: l_entry_type pay_element_entries_f.entry_type%TYPE;
785: l_processing_type pay_element_types_f.processing_type%TYPE;
786: --
787: Cursor C_Sel1 Is
788: select pee.assignment_id,

Line 794: pay_element_entries_f pee

790: pee.entry_type,
791: pet.processing_type
792: from pay_element_types_f pet,
793: pay_element_links_f pel,
794: pay_element_entries_f pee
795: where pee.element_entry_id = p_base_key_value
796: and p_effective_date
797: between pee.effective_start_date and pee.effective_end_date
798: and pel.element_link_id = pee.element_link_id

Line 833: p_base_table_name => 'pay_element_entries_f',

829: -- Call the corresponding datetrack api
830: --
831: dt_api.find_dt_del_modes
832: (p_effective_date => p_effective_date,
833: p_base_table_name => 'pay_element_entries_f',
834: p_base_key_column => 'element_entry_id',
835: p_base_key_value => p_base_key_value,
836: p_parent_table_name1 => 'per_all_assignments_f',
837: p_parent_key_column1 => 'assignment_id',

Line 861: p_rec in pay_element_entries_f%ROWTYPE,

857: --
858: Procedure ins_lck
859: (p_effective_date in date,
860: p_datetrack_mode in varchar2,
861: p_rec in pay_element_entries_f%ROWTYPE,
862: p_validation_start_date out nocopy date,
863: p_validation_end_date out nocopy date)
864: Is
865: --

Line 879: p_base_table_name => 'pay_element_entries_f',

875: --
876: dt_api.validate_dt_mode
877: (p_effective_date => p_effective_date,
878: p_datetrack_mode => p_datetrack_mode,
879: p_base_table_name => 'pay_element_entries_f',
880: p_base_key_column => 'element_entry_id',
881: p_base_key_value => p_rec.element_entry_id,
882: p_parent_table_name1 => 'per_all_assignments_f',
883: p_parent_key_column1 => 'assignment_id',

Line 930: from pay_element_entries_f

926: -- ensuring that the object version numbers match.
927: --
928: Cursor C_Sel1 is
929: select *
930: from pay_element_entries_f
931: where element_entry_id = p_element_entry_id
932: and p_effective_date between effective_start_date
933: and effective_end_date
934: for update nowait;

Line 1025: p_base_table_name => 'pay_element_entries_f',

1021: hr_utility.set_location('Entering validation_dt_mode', 15);
1022: dt_api.validate_dt_mode
1023: (p_effective_date => p_effective_date,
1024: p_datetrack_mode => p_datetrack_mode,
1025: p_base_table_name => 'pay_element_entries_f',
1026: p_base_key_column => 'element_entry_id',
1027: p_base_key_value => p_element_entry_id,
1028: p_parent_table_name1 => 'per_all_assignments_f',
1029: p_parent_key_column1 => 'assignment_id',

Line 1066: hr_utility.set_message_token('TABLE_NAME', 'pay_element_entries_f');

1062: -- The object is locked therefore we need to supply a meaningful
1063: -- error message.
1064: --
1065: hr_utility.set_message(801, 'HR_7165_OBJECT_LOCKED');
1066: hr_utility.set_message_token('TABLE_NAME', 'pay_element_entries_f');
1067: hr_utility.raise_error;
1068: When l_object_invalid then
1069: --
1070: -- The object doesn't exist or is invalid

Line 1073: hr_utility.set_message_token('TABLE_NAME', 'pay_element_entries_f');

1069: --
1070: -- The object doesn't exist or is invalid
1071: --
1072: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
1073: hr_utility.set_message_token('TABLE_NAME', 'pay_element_entries_f');
1074: hr_utility.raise_error;
1075: End lck;
1076: --
1077: -- ----------------------------------------------------------------------------