APPS.BEN_ESH_SHD dependencies on BEN_ELIG_SCHEDD_HRS_PRTE_F

Line 119: from ben_elig_schedd_hrs_prte_f

115: esh_attribute30,
116: object_version_number ,
117: criteria_score,
118: criteria_weight
119: from ben_elig_schedd_hrs_prte_f
120: where elig_schedd_hrs_prte_id = p_elig_schedd_hrs_prte_id
121: and p_effective_date
122: between effective_start_date and effective_end_date;
123: --

Line 192: from ben_elig_schedd_hrs_prte_f t

188: l_parent_key_value1 number;
189: --
190: Cursor C_Sel1 Is
191: select t.eligy_prfl_id
192: from ben_elig_schedd_hrs_prte_f t
193: where t.elig_schedd_hrs_prte_id = p_base_key_value
194: and p_effective_date
195: between t.effective_start_date and t.effective_end_date;
196: --

Line 214: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',

210: -- Call the corresponding datetrack api
211: --
212: dt_api.find_dt_del_modes
213: (p_effective_date => p_effective_date,
214: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',
215: p_base_key_column => 'elig_schedd_hrs_prte_id',
216: p_base_key_value => p_base_key_value,
217: p_parent_table_name1 => 'ben_eligy_prfl_f',
218: p_parent_key_column1 => 'eligy_prfl_id',

Line 248: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',

244: -- Call the corresponding datetrack api
245: --
246: dt_api.find_dt_upd_modes
247: (p_effective_date => p_effective_date,
248: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',
249: p_base_key_column => 'elig_schedd_hrs_prte_id',
250: p_base_key_value => p_base_key_value,
251: p_correction => p_correction,
252: p_update => p_update,

Line 281: (p_base_table_name => 'ben_elig_schedd_hrs_prte_f',

277: -- version number.
278: --
279: l_object_version_number :=
280: dt_api.get_object_version_number
281: (p_base_table_name => 'ben_elig_schedd_hrs_prte_f',
282: p_base_key_column => 'elig_schedd_hrs_prte_id',
283: p_base_key_value => p_base_key_value);
284: --
285: hr_utility.set_location(l_proc, 10);

Line 291: update ben_elig_schedd_hrs_prte_f t

287: --
288: -- Update the specified datetrack row setting the effective
289: -- end date to the specified new effective end date.
290: --
291: update ben_elig_schedd_hrs_prte_f t
292: set t.effective_end_date = p_new_effective_end_date,
293: t.object_version_number = l_object_version_number
294: where t.elig_schedd_hrs_prte_id = p_base_key_value
295: and p_effective_date

Line 379: from ben_elig_schedd_hrs_prte_f

375: esh_attribute30,
376: object_version_number ,
377: criteria_score,
378: criteria_weight
379: from ben_elig_schedd_hrs_prte_f
380: where elig_schedd_hrs_prte_id = p_elig_schedd_hrs_prte_id
381: and p_effective_date
382: between effective_start_date and effective_end_date
383: for update nowait;

Line 438: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',

434: --
435: dt_api.validate_dt_mode
436: (p_effective_date => p_effective_date,
437: p_datetrack_mode => p_datetrack_mode,
438: p_base_table_name => 'ben_elig_schedd_hrs_prte_f',
439: p_base_key_column => 'elig_schedd_hrs_prte_id',
440: p_base_key_value => p_elig_schedd_hrs_prte_id,
441: p_parent_table_name1 => 'ben_eligy_prfl_f',
442: p_parent_key_column1 => 'eligy_prfl_id',

Line 475: fnd_message.set_token('TABLE_NAME', 'ben_elig_schedd_hrs_prte_f');

471: -- The object is locked therefore we need to supply a meaningful
472: -- error message.
473: --
474: fnd_message.set_name('PAY', 'HR_7165_OBJECT_LOCKED');
475: fnd_message.set_token('TABLE_NAME', 'ben_elig_schedd_hrs_prte_f');
476: fnd_message.raise_error;
477: When l_object_invalid then
478: --
479: -- The object doesn't exist or is invalid

Line 482: fnd_message.set_token('TABLE_NAME', 'ben_elig_schedd_hrs_prte_f');

478: --
479: -- The object doesn't exist or is invalid
480: --
481: fnd_message.set_name('PAY', 'HR_7155_OBJECT_INVALID');
482: fnd_message.set_token('TABLE_NAME', 'ben_elig_schedd_hrs_prte_f');
483: fnd_message.raise_error;
484: End lck;
485: --
486: -- ----------------------------------------------------------------------------