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.ISC_FS_TASK_PARTY_MERGE_PKG dependencies on ISC_FS_TASKS_F

Line 62: -- For ISC_FS_TASKS_F table, if party_id 1000 got merged to party_id 2000

58:
59:
60: -- If the parent has changed(ie. Parent is getting merged) then transfer the
61: -- dependent record to the new parent.
62: -- For ISC_FS_TASKS_F table, if party_id 1000 got merged to party_id 2000
63: -- then we have to insert an event row for each task. When the incremental
64: -- load is next run it will capture the "current" (party_id 2000) data from JTF_TASKS_B
65:
66: insert into isc_fs_party_merge_events

Line 90: isc_fs_tasks_f

86: , hz_utility_pub.user_id
87: , hz_utility_pub.last_update_date
88: , hz_utility_pub.last_update_login
89: from
90: isc_fs_tasks_f
91: where customer_id = p_from_fk_id;
92:
93: exception
94: when others then

Line 160: -- For ISC_FS_TASKS_F table, if party_site_id 1111 got merged to party_site_id 2222

156:
157:
158: -- If the parent has changed(ie. Parent is getting merged) then transfer the
159: -- dependent record to the new parent.
160: -- For ISC_FS_TASKS_F table, if party_site_id 1111 got merged to party_site_id 2222
161: -- then we have to insert an event row for each task. When the incremental
162: -- load is next run it will capture the "current" (party_site_id 2222) data from JTF_TASKS_B
163:
164: insert into isc_fs_party_merge_events

Line 188: isc_fs_tasks_f

184: , hz_utility_pub.user_id
185: , hz_utility_pub.last_update_date
186: , hz_utility_pub.last_update_login
187: from
188: isc_fs_tasks_f
189: where address_id = p_from_fk_id;
190:
191: exception
192: when others then