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.PER_HRTCA_MERGE dependencies on PER_ALL_PEOPLE_F

Line 7: g_old_email_address per_all_people_f.email_address%type;

3: --
4: g_prev_last_name_len number default null;
5: --
6: --bug no 5546586 starts here
7: g_old_email_address per_all_people_f.email_address%type;
8: --bug no 5546586 ends here
9:
10: TYPE g_party_id_type IS TABLE OF NUMBER(15) index by binary_integer;
11: --

Line 25: (p_rec in out nocopy per_all_people_f%rowtype);

21: (p_number_of_workers in number default 1,
22: p_current_worker in number default 1);
23: --
24: procedure create_tca_person
25: (p_rec in out nocopy per_all_people_f%rowtype);
26: --
27: procedure update_tca_person
28: (p_rec in out nocopy per_all_people_f%rowtype,
29: p_overwrite_data in varchar2 default 'Y');

Line 28: (p_rec in out nocopy per_all_people_f%rowtype,

24: procedure create_tca_person
25: (p_rec in out nocopy per_all_people_f%rowtype);
26: --
27: procedure update_tca_person
28: (p_rec in out nocopy per_all_people_f%rowtype,
29: p_overwrite_data in varchar2 default 'Y');
30: --
31: procedure replicate_person_across_bg
32: (p_rec in out nocopy per_all_people_f%rowtype,

Line 32: (p_rec in out nocopy per_all_people_f%rowtype,

28: (p_rec in out nocopy per_all_people_f%rowtype,
29: p_overwrite_data in varchar2 default 'Y');
30: --
31: procedure replicate_person_across_bg
32: (p_rec in out nocopy per_all_people_f%rowtype,
33: p_overwrite_data in varchar2 default 'Y');
34: --
35:
36: /*Modified the parameters in the procedure create_update_contact_point to avoid the performance issue in bug#12933615*/

Line 38: (p_party_id in per_all_people_f.party_id%type,

34: --
35:
36: /*Modified the parameters in the procedure create_update_contact_point to avoid the performance issue in bug#12933615*/
37: procedure create_update_contact_point
38: (p_party_id in per_all_people_f.party_id%type,
39: p_email_address in per_all_people_f.email_address%type);
40: --
41: procedure per_party_merge
42: (p_entity_name in varchar2,

Line 39: p_email_address in per_all_people_f.email_address%type);

35:
36: /*Modified the parameters in the procedure create_update_contact_point to avoid the performance issue in bug#12933615*/
37: procedure create_update_contact_point
38: (p_party_id in per_all_people_f.party_id%type,
39: p_email_address in per_all_people_f.email_address%type);
40: --
41: procedure per_party_merge
42: (p_entity_name in varchar2,
43: p_from_id in number,

Line 97: -- A valid record should be existing in per_all_people_f table for the

93: -- This function will return a single record for a given party id and
94: -- effective date
95: --
96: -- Prerequisites:
97: -- A valid record should be existing in per_all_people_f table for the
98: -- given party id and effective date
99: --
100: -- In Parameters:
101: -- Name Reqd Type Description

Line 136: -- A valid record should be existing in per_all_people_f table for the

132: -- 'PARTY VALID'
133: -- 'PARTY INVALID'
134: --
135: -- Prerequisites:
136: -- A valid record should be existing in per_all_people_f table for the
137: -- given party id and effective date
138: --
139: -- In Parameters:
140: -- Name Reqd Type Description

Line 175: -- A valid record should be existing in per_all_people_f table for the

171: -- This function will return a single record for a given party id, person_id and
172: -- effective date
173: --
174: -- Prerequisites:
175: -- A valid record should be existing in per_all_people_f table for the
176: -- given party id,person id and effective date
177: --
178: -- In Parameters:
179: -- Name Reqd Type Description