APPS.PAY_CE_SUPPORT_PKG dependencies on HR_LOOKUPS

Line 46: hr_lookups hrl

42: 'SEGMENT29',pea.segment29,
43: 'SEGMENT30',pea.segment30,
44: 'EMPTY')
45: from pay_external_accounts pea,
46: hr_lookups hrl
47: where external_account_id = p_external_account_id
48: and hrl.lookup_type = p_lookup_type
49: and hrl.lookup_code = p_legislation_code;
50: --

Line 74: -- and the lookup_type is BANK_NAME, then go get the meaning from hr_lookups

70: -- where Bank Name should be. This is easily fixed by updating the lookup/
71: -- segment mappings. However, this then causes the following problem:
72: -- The valueset for Bank Name on the GB Bank key flex stores
73: -- the lookup_code, rather than the meaning. So, if the legislation is GB
74: -- and the lookup_type is BANK_NAME, then go get the meaning from hr_lookups
75: -- so the bank name is inserted into the Cash Management table.
76: --
77: if p_legislation_code = 'GB' then
78: --

Line 83: from hr_lookups

79: if p_lookup_type = 'BANK_NAME' then
80: --
81: select meaning
82: into l_bank_name
83: from hr_lookups
84: where lookup_code = l_segment_value
85: and lookup_type = 'GB_BANKS'
86: and application_id between 800 and 899;
87: --

Line 178: hr_lookups hrl,

174: cursor c_payment_status is
175: select
176: hrl.meaning
177: from
178: hr_lookups hrl,
179: pay_ce_reconciled_payments pcrp
180: where
181: hrl.lookup_code = pcrp.status_code
182: and pcrp.assignment_action_id = p_payment_id

Line 206: l_meaning hr_lookups.meaning%type;

202:
203: end payment_status;
204:
205: function lookup_meaning(p_meaning varchar2,p_code varchar2) return varchar2 is
206: l_meaning hr_lookups.meaning%type;
207: begin
208: --
209: select decode(substr(p_meaning,1,3),p_code||'_',substr(p_meaning,4),p_meaning)
210: into l_meaning