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_CONTACT_RELATIONSHIPS_PKG dependencies on PER_CONTACT_EXTRA_INFO_F

Line 85: child records in per_contact_extra_info_f.

81: update.
82: Modified procedure update_contact to handle
83: date_of_death.
84: Modified procedure delete_row to delete
85: child records in per_contact_extra_info_f.
86: 26-Jul-02 irgonzal 115.29 2483186 added hr_security_internal.populate_new_person
87: call to ensure security list maintenance
88: gets properly updated.
89: 06-Sep-02 vramanai 115.30 2533935 modified the cursor defination of check_person_changed

Line 231: -- the given date_end in per_contact_extra_info_f.

227: -- Description:
228: -- Accepts contact_relationship_id, date_start, and date_end, and check if
229: -- neither child record with effective_start_date earlier than the given
230: -- date_start exists nor child records with effective_end_date later than
231: -- the given date_end in per_contact_extra_info_f.
232: --
233: -- Prerequisites:
234: -- None.
235: --

Line 268: FROM per_contact_extra_info_f

264: x_date_end IN per_contact_relationships.date_end%TYPE) IS
265: --
266: CURSOR cel_earlier_child_exists IS
267: SELECT 1
268: FROM per_contact_extra_info_f
269: WHERE contact_relationship_id = x_contact_relationship_id
270: AND effective_start_date < x_date_start;
271: --
272: CURSOR cel_later_child_exists IS

Line 274: FROM per_contact_extra_info_f

270: AND effective_start_date < x_date_start;
271: --
272: CURSOR cel_later_child_exists IS
273: SELECT 1
274: FROM per_contact_extra_info_f
275: WHERE contact_relationship_id = x_contact_relationship_id
276: AND effective_end_date > x_date_end;
277: --
278: l_dummy VARCHAR2(1);

Line 1936: -- This validation guarantees all PER_CONTACT_EXTRA_INFO_F records

1932: END IF;
1933: --
1934: /*
1935: -- Bug.3207660
1936: -- This validation guarantees all PER_CONTACT_EXTRA_INFO_F records
1937: -- are within CTR.DATE_START and CTR.DATE_END date range.
1938: -- Now the validation is relaxed(removed).
1939: -- PER_CONTACT_EXTRA_INFO_F records can stay outside the range of CTR.
1940: -- Note the validation that PER_CONTACT_EXTRA_INFO_F records must be

Line 1939: -- PER_CONTACT_EXTRA_INFO_F records can stay outside the range of CTR.

1935: -- Bug.3207660
1936: -- This validation guarantees all PER_CONTACT_EXTRA_INFO_F records
1937: -- are within CTR.DATE_START and CTR.DATE_END date range.
1938: -- Now the validation is relaxed(removed).
1939: -- PER_CONTACT_EXTRA_INFO_F records can stay outside the range of CTR.
1940: -- Note the validation that PER_CONTACT_EXTRA_INFO_F records must be
1941: -- within the date range of PER_ALL_PEOPLE_F is still alive.
1942: chk_dates(
1943: x_contact_relationship_id => x_contact_relationship_id,

Line 1940: -- Note the validation that PER_CONTACT_EXTRA_INFO_F records must be

1936: -- This validation guarantees all PER_CONTACT_EXTRA_INFO_F records
1937: -- are within CTR.DATE_START and CTR.DATE_END date range.
1938: -- Now the validation is relaxed(removed).
1939: -- PER_CONTACT_EXTRA_INFO_F records can stay outside the range of CTR.
1940: -- Note the validation that PER_CONTACT_EXTRA_INFO_F records must be
1941: -- within the date range of PER_ALL_PEOPLE_F is still alive.
1942: chk_dates(
1943: x_contact_relationship_id => x_contact_relationship_id,
1944: x_date_start => x_date_start,

Line 2294: DELETE FROM per_contact_extra_info_f

2290: --
2291: Delete_Validation(X_Contact_Person_Id
2292: ,X_Contact_Relationship_Id);
2293: --
2294: DELETE FROM per_contact_extra_info_f
2295: WHERE contact_relationship_id = x_contact_relationship_id;
2296: --
2297: -- added for 1931258
2298: ben_person_delete.perform_ri_check(X_Contact_Person_Id);