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.ARP_CMERGE_ARCUS dependencies on HZ_CUST_CONTACT_POINTS

Line 241: --hz_cust_contact_points has been obsoleted.

237: --merge org contact
238: ra_cont( req_id, set_num, process_mode );
239:
240: --the procedure ra_ph is not being called anymore because table
241: --hz_cust_contact_points has been obsoleted.
242: --merge contact points: phone
243: --ra_ph( req_id, set_num, process_mode );
244:
245: arp_message.set_line( 'ARP_CMERGE_ARCUS.MERGE()-' );

Line 2576: | merge in HZ_CUST_CONTACT POINTS.

Line 2598: | do not delete rows in hz_cust_contact_points.

2594: | site is stripped by operating unit. We need to
2595: | check if this account has (active)sites in
2596: | HZ_CUST_ACCT_SITES_ALL.
2597: | Jianying Huang 12-DEC-00 Remove cursor c2 and c4 because we
2598: | do not delete rows in hz_cust_contact_points.
2599: | Jianying Huang 16-DEC-00 As per discussion with Gautam Prothia,
2600: | since we changed veiw RA_PHONES (see bug 1487607),
2601: | we will migrate phones and org contacts no matter the
2602: | account is active or inactive after merge. Also, we

Line 2606: | because table hz_cust_contact_points has been obsoleted.

2602: | account is active or inactive after merge. Also, we
2603: | will migrate these contact points in party level, not
2604: | in account level.
2605: | Jianying Huang 03-APR-01 The procedure is not being calling anymore
2606: | because table hz_cust_contact_points has been obsoleted.
2607: |
2608: +===========================================================================*/
2609:
2610: PROCEDURE ra_ph (

Line 2619: FROM hz_cust_contact_points yt, ra_customer_merges m

2615:
2616: --cursor c1 and c2 are used in 'inactivate' mode
2617: CURSOR c1 IS
2618: SELECT cust_contact_point_id
2619: FROM hz_cust_contact_points yt, ra_customer_merges m
2620: WHERE cust_account_site_id = m.duplicate_address_id
2621: AND m.process_flag = 'N'
2622: AND m.request_id = req_id
2623: AND m.set_number = set_num

Line 2628: FROM hz_cust_contact_points yt, ra_customer_merges m

2624: FOR UPDATE NOWAIT;
2625:
2626: CURSOR c2 is
2627: SELECT cust_contact_point_id
2628: FROM hz_cust_contact_points yt, ra_customer_merges m
2629: WHERE cust_account_id = m.duplicate_id
2630: AND m.process_flag = 'N'
2631: AND m.request_id = req_id
2632: AND m.set_number = set_num

Line 2644: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );

2640: /* locking tables by opening and closing cursors */
2641: IF process_mode = 'LOCK' THEN
2642:
2643: arp_message.set_name( 'AR', 'AR_LOCKING_TABLE' );
2644: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2645:
2646: OPEN c1;
2647: CLOSE c1;
2648:

Line 2657: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );

2653:
2654: /************** account site level inactivate ************/
2655:
2656: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2657: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2658:
2659: UPDATE HZ_CUST_CONTACT_POINTS yt
2660: SET (cust_account_id, cust_account_site_id) = (
2661: SELECT min(m.customer_id), min(m.customer_address_id)

Line 2659: UPDATE HZ_CUST_CONTACT_POINTS yt

2655:
2656: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2657: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2658:
2659: UPDATE HZ_CUST_CONTACT_POINTS yt
2660: SET (cust_account_id, cust_account_site_id) = (
2661: SELECT min(m.customer_id), min(m.customer_address_id)
2662: FROM ra_customer_merges m
2663: WHERE yt.cust_account_id = m.duplicate_id

Line 2690: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );

2686:
2687: /************** account level inactivate ************/
2688:
2689: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2690: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2691:
2692: UPDATE HZ_CUST_CONTACT_POINTS yt
2693: SET cust_account_id = (
2694: SELECT DISTINCT m.customer_id

Line 2692: UPDATE HZ_CUST_CONTACT_POINTS yt

2688:
2689: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2690: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2691:
2692: UPDATE HZ_CUST_CONTACT_POINTS yt
2693: SET cust_account_id = (
2694: SELECT DISTINCT m.customer_id
2695: FROM ra_customer_merges m
2696: WHERE yt.cust_account_id = m.duplicate_id

Line 3945: --comments out the following statement because table hz_cust_contact_points

3941:
3942: END IF;
3943:
3944: /**
3945: --comments out the following statement because table hz_cust_contact_points
3946: --has been obsoleted.
3947: -- Update the customer contact points with the new contact point id.
3948: UPDATE hz_cust_contact_points
3949: SET contact_point_id = x_contact_point_id

Line 3948: UPDATE hz_cust_contact_points

3944: /**
3945: --comments out the following statement because table hz_cust_contact_points
3946: --has been obsoleted.
3947: -- Update the customer contact points with the new contact point id.
3948: UPDATE hz_cust_contact_points
3949: SET contact_point_id = x_contact_point_id
3950: WHERE contact_point_id = l_contact_point_id
3951: AND cust_account_id = p_from_account_id;
3952: **/