APPS.HZ_LOCATION_V2PUB dependencies on HZ_PARTIES

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

821: p_prefix=>l_debug_prefix,
822: p_msg_level=>fnd_log.level_procedure);
823: END IF;
824:
825: -- update de-normalized location components in HZ_PARTIES for parties
826: -- having this location as an identifying location. There can be multiple
827: -- such parties.
828:
829: -- Bug 2197181: As part of Mix n Match project, the location components

Line 885: FROM hz_parties

881:
882: IF l_party_id <> -1 THEN
883: SELECT party_id
884: INTO l_party_id
885: FROM hz_parties
886: WHERE party_id = l_party_id
887: FOR UPDATE NOWAIT;
888:
889: UPDATE hz_parties

Line 889: UPDATE hz_parties

885: FROM hz_parties
886: WHERE party_id = l_party_id
887: FOR UPDATE NOWAIT;
888:
889: UPDATE hz_parties
890: SET country = DECODE(p_location_rec.country,
891: NULL, db_country,
892: fnd_api.g_miss_char, NULL,
893: p_location_rec.country),

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

942:
943: EXCEPTION
944: WHEN OTHERS THEN
945: fnd_message.set_name('AR', 'HZ_API_RECORD_CHANGED');
946: fnd_message.set_token('TABLE', 'HZ_PARTIES');
947: fnd_msg_pub.add;
948: CLOSE c1;
949: RAISE fnd_api.g_exc_error;
950: END;