DBA Data[Home] [Help]

APPS.IRC_IAD_UPD dependencies on DT_API

Line 77: dt_api.get_object_version_number

73: -- Because we are updating a row we must get the next object
74: -- version number.
75: --
76: p_rec.object_version_number :=
77: dt_api.get_object_version_number
78: (p_base_table_name => 'irc_assignment_details_f'
79: ,p_base_key_column => 'assignment_details_id'
80: ,p_base_key_value => p_rec.assignment_details_id
81: );

Line 271: dt_api.get_object_version_number

267: --
268: -- Reset the Latest Details flag for the current effective date range rows.
269: hr_utility.set_location(l_proc, 30);
270: p_rec.object_version_number :=
271: dt_api.get_object_version_number
272: (p_base_table_name => 'irc_assignment_details_f'
273: ,p_base_key_column => 'assignment_id'
274: ,p_base_key_value => p_rec.assignment_id
275: );

Line 581: dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode);

577: hr_utility.set_location('Entering:'||l_proc, 5);
578: --
579: -- Ensure that the DateTrack update mode is valid
580: --
581: dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode);
582: --
583: -- We must lock the row which we need to update.
584: --
585: irc_iad_shd.lck