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 2884: | merge in HZ_CUST_CONTACT POINTS.

Line 2906: | do not delete rows in hz_cust_contact_points.

2902: | site is stripped by operating unit. We need to
2903: | check if this account has (active)sites in
2904: | HZ_CUST_ACCT_SITES_ALL.
2905: | Jianying Huang 12-DEC-00 Remove cursor c2 and c4 because we
2906: | do not delete rows in hz_cust_contact_points.
2907: | Jianying Huang 16-DEC-00 As per discussion with Gautam Prothia,
2908: | since we changed veiw RA_PHONES (see bug 1487607),
2909: | we will migrate phones and org contacts no matter the
2910: | account is active or inactive after merge. Also, we

Line 2914: | because table hz_cust_contact_points has been obsoleted.

2910: | account is active or inactive after merge. Also, we
2911: | will migrate these contact points in party level, not
2912: | in account level.
2913: | Jianying Huang 03-APR-01 The procedure is not being calling anymore
2914: | because table hz_cust_contact_points has been obsoleted.
2915: |
2916: +===========================================================================*/
2917:
2918: PROCEDURE ra_ph (

Line 2927: FROM hz_cust_contact_points yt, ra_customer_merges m

2923:
2924: --cursor c1 and c2 are used in 'inactivate' mode
2925: CURSOR c1 IS
2926: SELECT cust_contact_point_id
2927: FROM hz_cust_contact_points yt, ra_customer_merges m
2928: WHERE cust_account_site_id = m.duplicate_address_id
2929: AND m.process_flag = 'N'
2930: AND m.request_id = req_id
2931: AND m.set_number = set_num

Line 2936: FROM hz_cust_contact_points yt, ra_customer_merges m

2932: FOR UPDATE NOWAIT;
2933:
2934: CURSOR c2 is
2935: SELECT cust_contact_point_id
2936: FROM hz_cust_contact_points yt, ra_customer_merges m
2937: WHERE cust_account_id = m.duplicate_id
2938: AND m.process_flag = 'N'
2939: AND m.request_id = req_id
2940: AND m.set_number = set_num

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

2948: /* locking tables by opening and closing cursors */
2949: IF process_mode = 'LOCK' THEN
2950:
2951: arp_message.set_name( 'AR', 'AR_LOCKING_TABLE' );
2952: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2953:
2954: OPEN c1;
2955: CLOSE c1;
2956:

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

2961:
2962: /************** account site level inactivate ************/
2963:
2964: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2965: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2966:
2967: UPDATE HZ_CUST_CONTACT_POINTS yt
2968: SET (cust_account_id, cust_account_site_id) = (
2969: SELECT min(m.customer_id), min(m.customer_address_id)

Line 2967: UPDATE HZ_CUST_CONTACT_POINTS yt

2963:
2964: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2965: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2966:
2967: UPDATE HZ_CUST_CONTACT_POINTS yt
2968: SET (cust_account_id, cust_account_site_id) = (
2969: SELECT min(m.customer_id), min(m.customer_address_id)
2970: FROM ra_customer_merges m
2971: WHERE yt.cust_account_id = m.duplicate_id

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

2994:
2995: /************** account level inactivate ************/
2996:
2997: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2998: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2999:
3000: UPDATE HZ_CUST_CONTACT_POINTS yt
3001: SET cust_account_id = (
3002: SELECT DISTINCT m.customer_id

Line 3000: UPDATE HZ_CUST_CONTACT_POINTS yt

2996:
2997: arp_message.set_name( 'AR', 'AR_UPDATING_TABLE' );
2998: arp_message.set_token( 'TABLE_NAME', 'HZ_CUST_CONTACT_POINTS', FALSE );
2999:
3000: UPDATE HZ_CUST_CONTACT_POINTS yt
3001: SET cust_account_id = (
3002: SELECT DISTINCT m.customer_id
3003: FROM ra_customer_merges m
3004: WHERE yt.cust_account_id = m.duplicate_id

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

4249:
4250: END IF;
4251:
4252: /**
4253: --comments out the following statement because table hz_cust_contact_points
4254: --has been obsoleted.
4255: -- Update the customer contact points with the new contact point id.
4256: UPDATE hz_cust_contact_points
4257: SET contact_point_id = x_contact_point_id

Line 4256: UPDATE hz_cust_contact_points

4252: /**
4253: --comments out the following statement because table hz_cust_contact_points
4254: --has been obsoleted.
4255: -- Update the customer contact points with the new contact point id.
4256: UPDATE hz_cust_contact_points
4257: SET contact_point_id = x_contact_point_id
4258: WHERE contact_point_id = l_contact_point_id
4259: AND cust_account_id = p_from_account_id;
4260: **/