APPS.HZ_LOCATION_V2PUB dependencies on HZ_PARTIES

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

808: p_prefix=>l_debug_prefix,
809: p_msg_level=>fnd_log.level_procedure);
810: END IF;
811:
812: -- update de-normalized location components in HZ_PARTIES for parties
813: -- having this location as an identifying location. There can be multiple
814: -- such parties.
815:
816: -- Bug 2197181: As part of Mix n Match project, the location components

Line 872: FROM hz_parties

868:
869: IF l_party_id <> -1 THEN
870: SELECT party_id
871: INTO l_party_id
872: FROM hz_parties
873: WHERE party_id = l_party_id
874: FOR UPDATE NOWAIT;
875:
876: UPDATE hz_parties

Line 876: UPDATE hz_parties

872: FROM hz_parties
873: WHERE party_id = l_party_id
874: FOR UPDATE NOWAIT;
875:
876: UPDATE hz_parties
877: SET country = DECODE(p_location_rec.country,
878: NULL, db_country,
879: fnd_api.g_miss_char, NULL,
880: p_location_rec.country),

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

929:
930: EXCEPTION
931: WHEN OTHERS THEN
932: fnd_message.set_name('AR', 'HZ_API_RECORD_CHANGED');
933: fnd_message.set_token('TABLE', 'HZ_PARTIES');
934: fnd_msg_pub.add;
935: CLOSE c1;
936: RAISE fnd_api.g_exc_error;
937: END;