APPS.BEN_LER_SHD dependencies on DT_API

Line 222: dt_api.find_dt_del_modes

218: Close C_Sel1;
219: --
220: -- Call the corresponding datetrack api
221: --
222: dt_api.find_dt_del_modes
223: (p_effective_date => p_effective_date,
224: p_base_table_name => 'ben_ler_f',
225: p_base_key_column => 'ler_id',
226: p_base_key_value => p_base_key_value,

Line 256: dt_api.find_dt_upd_modes

252: hr_utility.set_location('Entering:'||l_proc, 5);
253: --
254: -- Call the corresponding datetrack api
255: --
256: dt_api.find_dt_upd_modes
257: (p_effective_date => p_effective_date,
258: p_base_table_name => 'ben_ler_f',
259: p_base_key_column => 'ler_id',
260: p_base_key_value => p_base_key_value,

Line 290: dt_api.get_object_version_number

286: -- Because we are updating a row we must get the next object
287: -- version number.
288: --
289: l_object_version_number :=
290: dt_api.get_object_version_number
291: (p_base_table_name => 'ben_ler_f',
292: p_base_key_column => 'ler_id',
293: p_base_key_value => p_base_key_value);
294: --

Line 420: -- dt_api.validate_dt_mode.

416: -- Cursor for special locking code :
417: --
418: -- Do not select rows where the rsltg_ler_id = ler_id because
419: -- those rows would have already been locked by the call to
420: -- dt_api.validate_dt_mode.
421: --
422: Cursor C_lock (p_ler_id in number) is
423: select t1.effective_end_date effective_end_date
424: from ben_css_rltd_per_per_in_ler_f t1

Line 488: dt_api.validate_dt_mode

484: --
485: -- Validate the datetrack mode mode getting the validation start
486: -- and end dates for the specified datetrack operation.
487: --
488: dt_api.validate_dt_mode
489: (p_effective_date => p_effective_date,
490: p_datetrack_mode => p_datetrack_mode,
491: p_base_table_name => 'ben_ler_f',
492: p_base_key_column => 'ler_id',

Line 517: dt_api.validate_dt_mode

513: p_enforce_foreign_locking => false, --true, -- 3301171
514: p_validation_start_date => l_val_start_date1,
515: p_validation_end_date => l_val_end_date1);
516:
517: dt_api.validate_dt_mode
518: (p_effective_date => p_effective_date,
519: p_datetrack_mode => p_datetrack_mode,
520: p_base_table_name => 'ben_ler_f',
521: p_base_key_column => 'ler_id',

Line 532: -- because we call dt_api.validate_dt_mode twice, we must check

528: p_validation_start_date => l_val_start_date2,
529: p_validation_end_date => l_val_end_date2);
530:
531: --
532: -- because we call dt_api.validate_dt_mode twice, we must check
533: -- which set of validation dates we should use.
534: --
535: -- PETER, DO WE REALLY NEED TO DO THIS HERE, SINCE WE ARE ONLY CALLING
536: -- IT TWICE DUE TO ADDITIONAL CHILD TABLES, NOT ADDITIONAL PARENT