[Home] [Help]
182: -- default is false. The validation is controlled by a savepoint and
183: -- rollback mechanism. The savepoint is issued at the beginning of the
184: -- business process and is rollbacked at the end of the business process
185: -- when all the processing has been completed. The rollback is controlled
186: -- by raising and handling the exception hr_api.validate_enabled. We use
187: -- the exception because, by raising the exception with the business
188: -- process, we can exit successfully without having any of the 'OUT'
189: -- arguments being set.
190: --
321: -- default is false. The validation is controlled by a savepoint and
322: -- rollback mechanism. The savepoint is issued at the beginning of the
323: -- business process and is rollbacked at the end of the business process
324: -- when all the processing has been completed. The rollback is controlled
325: -- by raising and handling the exception hr_api.validate_enabled. We use
326: -- the exception because, by raising the exception with the business
327: -- process, we can exit successfully without having any of the 'OUT'
328: -- arguments being set.
329: --
398: --
399: procedure upd
400: (p_payroll_action_id in number
401: ,p_assignment_action_id in number
402: ,p_action_status in varchar2 default hr_api.g_varchar2
403: ,p_p_object_version_number in out nocopy number
404: ,p_a_object_version_number in number
405: ,p_validate in boolean default false
406: );
441: -- default is false. The validation is controlled by a savepoint and
442: -- rollback mechanism. The savepoint is issued at the beginning of the
443: -- business process and is rollbacked at the end of the business process
444: -- when all the processing has been completed. The rollback is controlled
445: -- by raising and handling the exception hr_api.validate_enabled. We use
446: -- the exception because, by raising the exception with the business
447: -- process, we can exit successfully without having any of the 'OUT'
448: -- arguments being set.
449: --