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.PAP_CMERGE_BB2 dependencies on HZ_CUSTOMER_MERGE_LOG

Line 85: -- Inserting the data into HZ_CUSTOMER_MERGE_LOG table for

81: --
82: /* Added for Tca audit*/
83: IF pap_cmerge.g_audit_profile = 'Y' THEN
84: --
85: -- Inserting the data into HZ_CUSTOMER_MERGE_LOG table for
86: -- PA_PROJECT_CONTACTS table. All rows are inserted that are going
87: -- to be deleted for old customer.
88: --
89: /*DEL_COL11 added for customer account relation enhancement*/

Line 90: INSERT INTO hz_customer_merge_log

86: -- PA_PROJECT_CONTACTS table. All rows are inserted that are going
87: -- to be deleted for old customer.
88: --
89: /*DEL_COL11 added for customer account relation enhancement*/
90: INSERT INTO hz_customer_merge_log
91: ( MERGE_LOG_ID,
92: MERGE_HEADER_ID ,
93: REQUEST_ID,
94: TABLE_NAME,

Line 117: HZ_CUSTOMER_MERGE_LOG_S.nextval,

113: LAST_UPDATED_BY ,
114: LAST_UPDATE_DATE,
115: LAST_UPDATE_LOGIN )
116: (select
117: HZ_CUSTOMER_MERGE_LOG_S.nextval,
118: var_cust_merge_head_id,
119: request_id,
120: 'PA_PROJECT_CONTACTS',
121: var_project_id,

Line 287: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for

283: -- Checking for the profile flag for audit.
284: --
285: IF pap_cmerge.g_audit_profile = 'Y' THEN
286: --
287: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for
288: -- PA_PROJECT_CONTACTS table the new and old contact id.
289: --
290: INSERT INTO hz_customer_merge_log
291: (

Line 290: INSERT INTO hz_customer_merge_log

286: --
287: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for
288: -- PA_PROJECT_CONTACTS table the new and old contact id.
289: --
290: INSERT INTO hz_customer_merge_log
291: (
292: MERGE_LOG_ID,
293: MERGE_HEADER_ID,
294: REQUEST_ID,

Line 309: HZ_CUSTOMER_MERGE_LOG_S.nextval,

305: LAST_UPDATED_BY ,
306: LAST_UPDATE_DATE,
307: LAST_UPDATE_LOGIN )
308: (SELECT
309: HZ_CUSTOMER_MERGE_LOG_S.nextval,
310: var_cust_merge_header_id,
311: req_id,
312: 'PA_PROJECT_CONTACTS',
313: var_project_id,

Line 383: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for

379: be present in var_racm_customer_id fetched from cursor_4*/
380:
381: IF pap_cmerge.g_audit_profile = 'Y' THEN
382: --
383: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for
384: -- PA_PROJECT_CONTACTS table the new and old contact id.
385: --
386: /*The new customer_id will be present in var_customer_id*/
387: INSERT INTO hz_customer_merge_log

Line 387: INSERT INTO hz_customer_merge_log

383: -- Inserting data into HZ_CUSTOMER_MERGE_LOG table for
384: -- PA_PROJECT_CONTACTS table the new and old contact id.
385: --
386: /*The new customer_id will be present in var_customer_id*/
387: INSERT INTO hz_customer_merge_log
388: (
389: MERGE_LOG_ID,
390: MERGE_HEADER_ID,
391: REQUEST_ID,

Line 406: HZ_CUSTOMER_MERGE_LOG_S.nextval,

402: LAST_UPDATED_BY ,
403: LAST_UPDATE_DATE,
404: LAST_UPDATE_LOGIN )
405: (SELECT
406: HZ_CUSTOMER_MERGE_LOG_S.nextval,
407: var_cust_merge_header_id,
408: req_id,
409: 'PA_PROJECT_CONTACTS',
410: var_project_id,