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

Line 209: -- the cursor to use per_all_people_f base table because if a person id is

205: -- In testing WebDB stateful mode, we found that in WF Notification
206: -- responsibility, the Business Group Id profile option is never set for the WF
207: -- Notification responsibility. This will cause no record to return because
208: -- the cursor is using the per_people_f view instead of the base table. Changed
209: -- the cursor to use per_all_people_f base table because if a person id is
210: -- passed to this function, the caller should have validation done first to
211: -- make sure if the person is within access or not.
212: -----------------------------------------------------------------------------
213: CURSOR csr_pp(p_person_id in per_people_f.person_id%type

Line 224: FROM per_all_people_f pp -- 02/09/2001 changed from per_people_f

220: ,pp.person_type_id
221: ,pp.email_address
222: ,pp.title
223: ,pp.full_name
224: FROM per_all_people_f pp -- 02/09/2001 changed from per_people_f
225: WHERE pp.person_id = p_person_id;
226:
227:
228: -----------------------------------------------------------------------------

Line 232: -- uses per_people_f view instead of per_all_people_f base table. The view

228: -----------------------------------------------------------------------------
229: -- Fix Bug 1615428:
230: -- Intead of calling per_per_bus.return_legislation_code to derive the
231: -- legislation_code, we query legislation code here because per_per_bus api
232: -- uses per_people_f view instead of per_all_people_f base table. The view
233: -- will cause no rec found error when accessed from WF Notification
234: -- responsibility. In addition, per_per_bus.return_legislation_code function
235: -- uses two global variables in the package body: g_person_id and
236: -- g_legislation_code which may cause obscure error when running in WebDB

Line 239: -- with a change to the table per_all_people_f instead of per_people_f.

235: -- uses two global variables in the package body: g_person_id and
236: -- g_legislation_code which may cause obscure error when running in WebDB
237: -- stateful mode.
238: -- The following cursor is copied from per_per_bus.return_legislation_code
239: -- with a change to the table per_all_people_f instead of per_people_f.
240: -----------------------------------------------------------------------------
241: cursor csr_leg_code is
242: select pbg.legislation_code
243: from per_business_groups pbg

Line 244: , per_all_people_f per

240: -----------------------------------------------------------------------------
241: cursor csr_leg_code is
242: select pbg.legislation_code
243: from per_business_groups pbg
244: , per_all_people_f per
245: where per.person_id = p_person_id
246: and pbg.business_group_id = per.business_group_id
247: and p_effective_date between per.effective_start_date
248: and per.effective_end_date

Line 2087: g_person_id per_all_people_f.person_id%TYPE;

2083: (p_item_type IN VARCHAR2
2084: ,p_item_key IN VARCHAR
2085: ) RETURN BOOLEAN IS
2086: l_text_value VARCHAR2(2000);
2087: g_person_id per_all_people_f.person_id%TYPE;
2088: l_proc constant varchar2(100) := g_package || ' isSelfUpdating';
2089: BEGIN
2090: hr_utility.set_location('Entering: '|| l_proc,5);
2091: l_text_value :=