APPS.HZ_GNR_UTIL_PKG dependencies on HZ_PARTIES

Line 299: -- update de-normalized location components in HZ_PARTIES for parties

295: l_program_application_id := hz_utility_v2pub.program_application_id;
296: l_request_id := NVL(hz_utility_v2pub.request_id, -1);
297: l_program_update_date := hz_utility_v2pub.program_update_date;
298:
299: -- update de-normalized location components in HZ_PARTIES for parties
300: -- having this location as an identifying location. There can be multiple
301: -- such parties.
302: DECLARE
303: l_party_id NUMBER;

Line 352: FROM hz_parties

348:
349: IF l_party_id <> -1 THEN
350: SELECT party_id
351: INTO l_party_id
352: FROM hz_parties
353: WHERE party_id = l_party_id
354: FOR UPDATE NOWAIT;
355:
356: UPDATE hz_parties

Line 356: UPDATE hz_parties

352: FROM hz_parties
353: WHERE party_id = l_party_id
354: FOR UPDATE NOWAIT;
355:
356: UPDATE hz_parties
357: SET country = p_new_location_rec.country,
358: address1 = p_new_location_rec.address1,
359: address2 = p_new_location_rec.address2,
360: address3 = p_new_location_rec.address3,

Line 384: fnd_message.set_token('TABLE', 'HZ_PARTIES');

380: EXCEPTION
381: WHEN OTHERS THEN
382: /*
383: fnd_message.set_name('AR', 'HZ_API_RECORD_CHANGED');
384: fnd_message.set_token('TABLE', 'HZ_PARTIES');
385: fnd_msg_pub.add;
386: */
387: CLOSE c1;
388: -- RAISE fnd_api.g_exc_error;

Line 2521: -- 1. Update de-normalized location components in HZ_PARTIES

2517: END IF;
2518: END IF;
2519:
2520: -- Call post_location_update to do post update process.
2521: -- 1. Update de-normalized location components in HZ_PARTIES
2522: -- 2. Call to indicate location update to DQM(HZ_DQM_SYNC.sync_location).
2523: -- 3. 6. Invoke business event system.
2524: begin
2525: post_location_update( p_old_location_rec => l_old_location_rec,