DBA Data[Home] [Help]

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 338: -- application context, for reference by HR_LOOKUPS.

334: hr_api.g_legislation_code := l_legislation_code;
335: --
336: -- Call set_legislation_context to store the legislation_code
337: -- for the session in the 'LEG_CODE' namespace of the 'HR_SESSION_DATA'
338: -- application context, for reference by HR_LOOKUPS.
339: --
340: hr_api.set_legislation_context(l_legislation_code);
341: -- Initialize the session context for bug 8250782.
342: g_session_context := FND_GLOBAL.Get_Session_Context;

Line 807: -- |----------------------< not_exists_in_hr_lookups >------------------------|

803: raise;
804: end return_concat_kf_segments;
805: --
806: -- ----------------------------------------------------------------------------
807: -- |----------------------< not_exists_in_hr_lookups >------------------------|
808: -- ----------------------------------------------------------------------------
809: --
810: function not_exists_in_hr_lookups
811: (p_effective_date in date

Line 810: function not_exists_in_hr_lookups

806: -- ----------------------------------------------------------------------------
807: -- |----------------------< not_exists_in_hr_lookups >------------------------|
808: -- ----------------------------------------------------------------------------
809: --
810: function not_exists_in_hr_lookups
811: (p_effective_date in date
812: ,p_lookup_type in varchar2
813: ,p_lookup_code in varchar2
814: ) return boolean is

Line 824: from hr_lookups

820: -- Declare Local cursors
821: --
822: cursor csr_hr_look is
823: select null
824: from hr_lookups
825: where lookup_code = p_lookup_code
826: and lookup_type = p_lookup_type
827: and enabled_flag = 'Y'
828: and p_effective_date between

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

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

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

845: end if;
846:
847:
848: -- DK 2002-11-08 PLSQLSTD
849: --hr_utility.set_location(hr_api.g_package||'not_exists_in_hr_lookups', 10);
850:
851:
852: --
853: open csr_hr_look;

Line 862: end not_exists_in_hr_lookups;

858: else
859: close csr_hr_look;
860: return false;
861: end if;
862: end not_exists_in_hr_lookups;
863: --
864: -- ----------------------------------------------------------------------------
865: -- |-------------------< not_exists_in_leg_lookups >-----------------------|
866: -- ----------------------------------------------------------------------------

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

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

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

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

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

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

Line 1024: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|

1020: end if;
1021: end not_exists_in_fnd_lookups;
1022: --
1023: -- ----------------------------------------------------------------------------
1024: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|
1025: -- ----------------------------------------------------------------------------
1026: --
1027: function not_exists_in_dt_hr_lookups
1028: (p_effective_date in date

Line 1027: function not_exists_in_dt_hr_lookups

1023: -- ----------------------------------------------------------------------------
1024: -- |--------------------< not_exists_in_dt_hr_lookups >-----------------------|
1025: -- ----------------------------------------------------------------------------
1026: --
1027: function not_exists_in_dt_hr_lookups
1028: (p_effective_date in date
1029: ,p_validation_start_date in date
1030: ,p_validation_end_date in date
1031: ,p_lookup_type in varchar2

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

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

Line 1048: return not_exists_in_hr_lookups

1044: -- not_exists_in_dt_fnd_lookups functions.
1045: --
1046: begin
1047: --
1048: return not_exists_in_hr_lookups
1049: (p_effective_date => p_effective_date
1050: ,p_lookup_type => p_lookup_type
1051: ,p_lookup_code => p_lookup_code
1052: );

Line 1054: end not_exists_in_dt_hr_lookups;

1050: ,p_lookup_type => p_lookup_type
1051: ,p_lookup_code => p_lookup_code
1052: );
1053: --
1054: end not_exists_in_dt_hr_lookups;
1055: --
1056: -- ----------------------------------------------------------------------------
1057: -- |---------------------< not_exists_in_dt_leg_lookups >---------------------|
1058: -- ----------------------------------------------------------------------------

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

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

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

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

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

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

Line 1155: from hr_lookups

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

Line 1229: from hr_lookups

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