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.HR_API dependencies on HR_LOOKUPS

Line 215: from hr_lookups hl

211: l_argument varchar2(30);
212: --
213: Cursor Sel_Id Is
214: select hl.lookup_code
215: from hr_lookups hl
216: where hl.lookup_type = p_lookup_type
217: and hl.meaning = p_meaning;
218: --
219: Begin

Line 336: -- application context, for reference by HR_LOOKUPS.

332: hr_api.g_legislation_code := l_legislation_code;
333: --
334: -- Call set_legislation_context to store the legislation_code
335: -- for the session in the 'LEG_CODE' namespace of the 'HR_SESSION_DATA'
336: -- application context, for reference by HR_LOOKUPS.
337: --
338: hr_api.set_legislation_context(l_legislation_code);
339: --
340: end if;

Line 803: -- |----------------------< not_exists_in_hr_lookups >------------------------|

799: raise;
800: end return_concat_kf_segments;
801: --
802: -- ----------------------------------------------------------------------------
803: -- |----------------------< not_exists_in_hr_lookups >------------------------|
804: -- ----------------------------------------------------------------------------
805: --
806: function not_exists_in_hr_lookups
807: (p_effective_date in date

Line 806: function not_exists_in_hr_lookups

802: -- ----------------------------------------------------------------------------
803: -- |----------------------< not_exists_in_hr_lookups >------------------------|
804: -- ----------------------------------------------------------------------------
805: --
806: function not_exists_in_hr_lookups
807: (p_effective_date in date
808: ,p_lookup_type in varchar2
809: ,p_lookup_code in varchar2
810: ) return boolean is

Line 820: from hr_lookups

816: -- Declare Local cursors
817: --
818: cursor csr_hr_look is
819: select null
820: from hr_lookups
821: where lookup_code = p_lookup_code
822: and lookup_type = p_lookup_type
823: and enabled_flag = 'Y'
824: and p_effective_date between

Line 839: -- hr_lookups view. Just in case there has been a change to

835: if p_lookup_code = 'Y' or p_lookup_code = 'N' then
836: return false;
837: end if;
838: -- If the value is not known then go onto check against the
839: -- hr_lookups view. Just in case there has been a change to
840: -- the system defined lookup.
841: end if;
842:
843:

Line 845: --hr_utility.set_location(hr_api.g_package||'not_exists_in_hr_lookups', 10);

841: end if;
842:
843:
844: -- DK 2002-11-08 PLSQLSTD
845: --hr_utility.set_location(hr_api.g_package||'not_exists_in_hr_lookups', 10);
846:
847:
848: --
849: open csr_hr_look;

Line 858: end not_exists_in_hr_lookups;

854: else
855: close csr_hr_look;
856: return false;
857: end if;
858: end not_exists_in_hr_lookups;
859: --
860: -- ----------------------------------------------------------------------------
861: -- |-------------------< not_exists_in_leg_lookups >-----------------------|
862: -- ----------------------------------------------------------------------------

Line 897: -- hr_lookups view. Just in case there has been a change to

893: if p_lookup_code = 'Y' or p_lookup_code = 'N' then
894: return false;
895: end if;
896: -- If the value is not known then go onto check against the
897: -- hr_lookups view. Just in case there has been a change to
898: -- the system defined lookup.
899: end if;
900: hr_utility.set_location(hr_api.g_package||'not_exists_in_leg_lookups', 10);
901: --

Line 950: -- hr_lookups view. Just in case there has been a change to

946: if p_lookup_code = 'Y' or p_lookup_code = 'N' then
947: return false;
948: end if;
949: -- If the value is not known then go onto check against the
950: -- hr_lookups view. Just in case there has been a change to
951: -- the system defined lookup.
952: end if;
953: hr_utility.set_location(hr_api.g_package||'not_exists_in_hrstanlookups', 10);
954: --

Line 1003: -- hr_lookups view. Just in case there has been a change to

999: if p_lookup_code = 'Y' or p_lookup_code = 'N' then
1000: return false;
1001: end if;
1002: -- If the value is not known then go onto check against the
1003: -- hr_lookups view. Just in case there has been a change to
1004: -- the system defined lookup.
1005: end if;
1006: hr_utility.set_location(hr_api.g_package||'not_exists_in_fnd_lookups', 10);
1007: --

Line 1020: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|

1016: end if;
1017: end not_exists_in_fnd_lookups;
1018: --
1019: -- ----------------------------------------------------------------------------
1020: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|
1021: -- ----------------------------------------------------------------------------
1022: --
1023: function not_exists_in_dt_hr_lookups
1024: (p_effective_date in date

Line 1023: function not_exists_in_dt_hr_lookups

1019: -- ----------------------------------------------------------------------------
1020: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|
1021: -- ----------------------------------------------------------------------------
1022: --
1023: function not_exists_in_dt_hr_lookups
1024: (p_effective_date in date
1025: ,p_validation_start_date in date
1026: ,p_validation_end_date in date
1027: ,p_lookup_type in varchar2

Line 1032: -- as the not_exists_in_hr_lookups function. Currently the APIs do the

1028: ,p_lookup_code in varchar2
1029: ) return boolean is
1030: --
1031: -- NOTE: At the moment this function does exactly the same validation
1032: -- as the not_exists_in_hr_lookups function. Currently the APIs do the
1033: -- same validation as the Form. i.e. Only check the code exists on the
1034: -- effective_date of the operation. This separate function has been provided
1035: -- because in the future we may want to introduce full date range validation.
1036: -- i.e. Check the lookup_code start_date_active end_date_active values span

Line 1044: return not_exists_in_hr_lookups

1040: -- not_exists_in_dt_fnd_lookups functions.
1041: --
1042: begin
1043: --
1044: return not_exists_in_hr_lookups
1045: (p_effective_date => p_effective_date
1046: ,p_lookup_type => p_lookup_type
1047: ,p_lookup_code => p_lookup_code
1048: );

Line 1050: end not_exists_in_dt_hr_lookups;

1046: ,p_lookup_type => p_lookup_type
1047: ,p_lookup_code => p_lookup_code
1048: );
1049: --
1050: end not_exists_in_dt_hr_lookups;
1051: --
1052: -- ----------------------------------------------------------------------------
1053: -- |---------------------< not_exists_in_dt_leg_lookups >---------------------|
1054: -- ----------------------------------------------------------------------------

Line 1072: -- The same issue applies to the not_exists_in_dt_hr_lookups,

1068: -- because in the future we may want to introduce full date range validation.
1069: -- i.e. Check the lookup_code start_date_active end_date_active values span
1070: -- the vaidation_start_date to validation_end_date range of the DateTrack
1071: -- operation.
1072: -- The same issue applies to the not_exists_in_dt_hr_lookups,
1073: -- and not_exists_in_dt_hrstanlookups and
1074: -- not_exists_in_dt_fnd_lookups functions.
1075: --
1076: begin

Line 1098: -- Refer to code comments in not_exists_in_dt_hr_lookups for details of

1094: ,p_lookup_type in varchar2
1095: ,p_lookup_code in varchar2
1096: ) return boolean is
1097: --
1098: -- Refer to code comments in not_exists_in_dt_hr_lookups for details of
1099: -- why this procedure exists and is currently coded to do the same
1100: -- validation as not_exists_in_hrstanlookups.
1101: --
1102: begin

Line 1124: -- Refer to code comments in not_exists_in_dt_hr_lookups for details of

1120: ,p_lookup_type in varchar2
1121: ,p_lookup_code in varchar2
1122: ) return boolean is
1123: --
1124: -- Refer to code comments in not_exists_in_dt_hr_lookups for details of
1125: -- why this procedure exists and is currently coded to do the same
1126: -- validation as not_exists_in_fnd_lookups.
1127: --
1128: begin

Line 1151: from hr_lookups

1147: -- Cursor to obtain the user description for the hook_type
1148: --
1149: cursor csr_hook_type is
1150: select meaning
1151: from hr_lookups
1152: where lookup_type = 'API_HOOK_TYPE'
1153: and enabled_flag = 'Y'
1154: and lookup_code = p_hook_type;
1155: --

Line 1225: from hr_lookups

1221: -- Cursor to obtain the user description for the hook_type
1222: --
1223: cursor csr_hook_type is
1224: select meaning
1225: from hr_lookups
1226: where lookup_type = 'API_HOOK_TYPE'
1227: and enabled_flag = 'Y'
1228: and lookup_code = p_hook_type;
1229: --