DBA Data[Home] [Help]

APPS.PAY_QPA_API dependencies on HR_API

Line 152: -- by raising and handling the exception hr_api.validate_enabled. We use

148: -- default is false. The validation is controlled by a savepoint and
149: -- rollback mechanism. The savepoint is issued at the beginning of the
150: -- business process and is rollbacked at the end of the business process
151: -- when all the processing has been completed. The rollback is controlled
152: -- by raising and handling the exception hr_api.validate_enabled. We use
153: -- the exception because, by raising the exception with the business
154: -- process, we can exit successfully without having any of the 'OUT'
155: -- arguments being set.
156: --

Line 229: ,p_action_status in varchar2 default hr_api.g_varchar2

225: --
226: procedure upd
227: (p_payroll_action_id in number
228: ,p_assignment_action_id in number
229: ,p_action_status in varchar2 default hr_api.g_varchar2
230: ,p_p_object_version_number in out nocopy number
231: ,p_a_object_version_number in number
232: ,p_validate in boolean default false
233: );

Line 314: -- by raising and handling the exception hr_api.validate_enabled. We use

310: -- default is false. The validation is controlled by a savepoint and
311: -- rollback mechanism. The savepoint is issued at the beginning of the
312: -- business process and is rollbacked at the end of the business process
313: -- when all the processing has been completed. The rollback is controlled
314: -- by raising and handling the exception hr_api.validate_enabled. We use
315: -- the exception because, by raising the exception with the business
316: -- process, we can exit successfully without having any of the 'OUT'
317: -- arguments being set.
318: --