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.HZ_LOCATION_PROFILE_PVT dependencies on HZ_LOCATIONS

Line 25: FROM hz_locations hl

21: SELECT hl.country, hl.address1, hl.address2, hl.address3,
22: hl.address4, hl.city, hl.postal_code, hl.state,
23: hl.province, hl.county, hl.actual_content_source,
24: hl.validation_status_code, hl.date_validated
25: FROM hz_locations hl
26: WHERE hl.location_id = l_location_id;
27:
28: l_location_profile_rec location_profile_rec_type;
29: db_country HZ_LOCATIONS.COUNTRY%TYPE;

Line 29: db_country HZ_LOCATIONS.COUNTRY%TYPE;

25: FROM hz_locations hl
26: WHERE hl.location_id = l_location_id;
27:
28: l_location_profile_rec location_profile_rec_type;
29: db_country HZ_LOCATIONS.COUNTRY%TYPE;
30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;

Line 30: db_county HZ_LOCATIONS.COUNTY%TYPE;

26: WHERE hl.location_id = l_location_id;
27:
28: l_location_profile_rec location_profile_rec_type;
29: db_country HZ_LOCATIONS.COUNTRY%TYPE;
30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;

Line 31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;

27:
28: l_location_profile_rec location_profile_rec_type;
29: db_country HZ_LOCATIONS.COUNTRY%TYPE;
30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;

Line 32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;

28: l_location_profile_rec location_profile_rec_type;
29: db_country HZ_LOCATIONS.COUNTRY%TYPE;
30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;

Line 33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;

29: db_country HZ_LOCATIONS.COUNTRY%TYPE;
30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;

Line 34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;

30: db_county HZ_LOCATIONS.COUNTY%TYPE;
31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;

Line 35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;

31: db_validation_status_code HZ_LOCATIONS.VALIDATION_STATUS_CODE%TYPE;
32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;

Line 36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;

32: db_date_validated HZ_LOCATIONS.DATE_VALIDATED%TYPE;
33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;

Line 37: db_city HZ_LOCATIONS.CITY%TYPE;

33: db_address1 HZ_LOCATIONS.ADDRESS1%TYPE;
34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;
41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;

Line 38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;

34: db_address2 HZ_LOCATIONS.ADDRESS2%TYPE;
35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;
41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;
42:

Line 39: db_state HZ_LOCATIONS.STATE%TYPE;

35: db_address3 HZ_LOCATIONS.ADDRESS3%TYPE;
36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;
41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;
42:
43: BEGIN

Line 40: db_province HZ_LOCATIONS.PROVINCE%TYPE;

36: db_address4 HZ_LOCATIONS.ADDRESS4%TYPE;
37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;
41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;
42:
43: BEGIN
44:

Line 41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;

37: db_city HZ_LOCATIONS.CITY%TYPE;
38: db_postal_code HZ_LOCATIONS.POSTAL_CODE%TYPE;
39: db_state HZ_LOCATIONS.STATE%TYPE;
40: db_province HZ_LOCATIONS.PROVINCE%TYPE;
41: db_content_source HZ_LOCATIONS.ACTUAL_CONTENT_SOURCE%TYPE;
42:
43: BEGIN
44:
45: l_location_profile_rec := p_location_profile_rec;

Line 163: -- denormalize validation_status_code to HZ_LOCATIONS

159: );
160:
161: x_location_profile_id := l_location_profile_rec.location_profile_id;
162:
163: -- denormalize validation_status_code to HZ_LOCATIONS
164:
165: -- SSM SST Integration and Extension
166: -- Changed the hard coded value of DNB and instead will check if the content source is of type 'PURCHASED'.
167:

Line 172: UPDATE HZ_LOCATIONS

168: --IF(NOT(l_location_profile_rec.actual_content_source in ('USER_ENTERED','DNB'))) THEN
169: IF(NOT(l_location_profile_rec.actual_content_source = 'USER_ENTERED' OR
170: HZ_UTILITY_V2PUB.is_purchased_content_source(l_location_profile_rec.actual_content_source) = 'Y' )
171: ) THEN
172: UPDATE HZ_LOCATIONS
173: SET date_validated = sysdate
174: , validation_status_code = l_location_profile_rec.validation_status_code
175: , last_update_date = hz_utility_v2pub.last_update_date
176: , last_updated_by = hz_utility_v2pub.last_updated_by

Line 244: FROM hz_locations

240:
241: -- check if the current location record has been validated
242: CURSOR is_standardized(l_location_id NUMBER) IS
243: SELECT 'X'
244: FROM hz_locations
245: WHERE location_id = l_location_id
246: AND date_validated IS NOT NULL
247: AND validation_status_code IS NOT NULL;
248:

Line 479: -- denormalize validation_status_code to HZ_LOCATIONS only if location can be updated

475: );
476:
477: END IF;
478:
479: -- denormalize validation_status_code to HZ_LOCATIONS only if location can be updated
480:
481: -- SSM SST Integration and Extension
482: -- Instead of hard-coding, check if source system is of type PURCHASED.
483:

Line 488: -- if update standardized is ok, then update HZ_LOCATIONS, otherwise do nothing

484: --IF(NOT(l_location_profile_rec.actual_content_source in ('USER_ENTERED','DNB'))) THEN
485: IF (NOT(l_location_profile_rec.actual_content_source = 'USER_ENTERED' OR
486: HZ_UTILITY_V2PUB.is_purchased_content_source(l_location_profile_rec.actual_content_source)= 'Y' )
487: )THEN
488: -- if update standardized is ok, then update HZ_LOCATIONS, otherwise do nothing
489: IF(l_validation_sst_flag = 'Y') THEN
490: UPDATE HZ_LOCATIONS
491: SET date_validated = sysdate,
492: validation_status_code = l_location_profile_rec.validation_status_code

Line 490: UPDATE HZ_LOCATIONS

486: HZ_UTILITY_V2PUB.is_purchased_content_source(l_location_profile_rec.actual_content_source)= 'Y' )
487: )THEN
488: -- if update standardized is ok, then update HZ_LOCATIONS, otherwise do nothing
489: IF(l_validation_sst_flag = 'Y') THEN
490: UPDATE HZ_LOCATIONS
491: SET date_validated = sysdate,
492: validation_status_code = l_location_profile_rec.validation_status_code
493: WHERE location_id = l_location_profile_rec.location_id;
494:

Line 518: UPDATE HZ_LOCATIONS

514: END;
515: END IF;
516: ELSE -- nullify if actual_content_source in ('USER_ENTERED', 'DNB')
517: IF(l_validation_sst_flag = 'Y') THEN
518: UPDATE HZ_LOCATIONS
519: SET date_validated = null,
520: validation_status_code = null
521: WHERE location_id = l_location_profile_rec.location_id;
522: END IF;

Line 733: -- This procedure will update both HZ_LOCATIONS.validation_status_code

729:
730: END set_effective_end_date;
731:
732: --
733: -- This procedure will update both HZ_LOCATIONS.validation_status_code
734: -- and HZ_LOCATION_PROFILES.validation_status_code
735: -- This procedure should not be invoked along. It should be called
736: -- after creating or updating location. It is required for those
737: -- content source which is NOT USER_ENTERED.

Line 739: -- parameter to pass validation_status_code in HZ_LOCATIONS_V2PUB

735: -- This procedure should not be invoked along. It should be called
736: -- after creating or updating location. It is required for those
737: -- content source which is NOT USER_ENTERED.
738: -- The reason is that when creating/updating location, there is no
739: -- parameter to pass validation_status_code in HZ_LOCATIONS_V2PUB
740: -- api. As location is being created/updated, location profile
741: -- will also be created/updated base on the profile
742: -- HZ_MAINTAIN_LOC_HISTORY and whether there is an existing
743: -- active profile record for that content source.

Line 745: -- the caller program that calls HZ_LOCATIONS_V2PUB should also

741: -- will also be created/updated base on the profile
742: -- HZ_MAINTAIN_LOC_HISTORY and whether there is an existing
743: -- active profile record for that content source.
744: -- Therefore, after location profile is being created/updated,
745: -- the caller program that calls HZ_LOCATIONS_V2PUB should also
746: -- set the validation_status_code appropriately if the actual_content_source
747: -- passed in is NOT USER_ENTERED record.
748: --
749: PROCEDURE set_validation_status_code (

Line 776: UPDATE hz_locations

772: UPDATE hz_location_profiles
773: SET validation_status_code = p_validation_status_code
774: WHERE location_profile_id = p_location_profile_id;
775:
776: UPDATE hz_locations
777: SET validation_status_code = p_validation_status_code
778: WHERE location_id =
779: ( SELECT location_id
780: FROM HZ_LOCATION_PROFILES