DBA Data[Home] [Help]

APPS.OTA_VSP_API dependencies on HR_API

Line 121: -- another user. This will raise the HR_Api.Object_Locked exception.

117: --
118: -- Post Failure:
119: -- The Lck process can fail for three reasons:
120: -- 1) When attempting to lock the row the row could already be locked by
121: -- another user. This will raise the HR_Api.Object_Locked exception.
122: -- 2) The row which is required to be locked doesn't exist in the HR Schema.
123: -- This error is trapped and reported using the message name
124: -- 'HR_7155_OBJECT_INVALID'.
125: -- 3) The row although existing in the HR Schema has a different object

Line 132: -- call to hr_api.mandatory_arg_error procedure to ensure that these

128: -- 'HR_7155_OBJECT_INVALID'.
129: --
130: -- Developer Implementation Notes:
131: -- For each primary key and the object version number arguments add a
132: -- call to hr_api.mandatory_arg_error procedure to ensure that these
133: -- argument values are not null.
134: --
135: -- {End Of Comments}
136: -- ----------------------------------------------------------------------------

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

177: -- default is false. The validation is controlled by a savepoint and
178: -- rollback mechanism. The savepoint is issued at the beginning of the
179: -- business process and is rollbacked at the end of the business process
180: -- when all the processing has been completed. The rollback is controlled
181: -- by raising and handling the exception hr_api.validate_enabled. We use
182: -- the exception because, by raising the exception with the business
183: -- process, we can exit successfully without having any of the 'OUT'
184: -- arguments being set.
185: --

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

296: -- default is false. The validation is controlled by a savepoint and
297: -- rollback mechanism. The savepoint is issued at the beginning of the
298: -- business process and is rollbacked at the end of the business process
299: -- when all the processing has been completed. The rollback is controlled
300: -- by raising and handling the exception hr_api.validate_enabled. We use
301: -- the exception because, by raising the exception with the business
302: -- process, we can exit successfully without having any of the 'OUT'
303: -- arguments being set.
304: --

Line 366: p_vendor_id in number default hr_api.g_number,

362: -- ----------------------------------------------------------------------------
363: Procedure upd
364: (
365: p_vendor_supply_id in number,
366: p_vendor_id in number default hr_api.g_number,
367: p_activity_version_id in number default hr_api.g_number,
368: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
369: p_comments in varchar2 default hr_api.g_varchar2,
370: p_validate in boolean default false

Line 367: p_activity_version_id in number default hr_api.g_number,

363: Procedure upd
364: (
365: p_vendor_supply_id in number,
366: p_vendor_id in number default hr_api.g_number,
367: p_activity_version_id in number default hr_api.g_number,
368: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
369: p_comments in varchar2 default hr_api.g_varchar2,
370: p_validate in boolean default false
371: );

Line 368: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,

364: (
365: p_vendor_supply_id in number,
366: p_vendor_id in number default hr_api.g_number,
367: p_activity_version_id in number default hr_api.g_number,
368: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
369: p_comments in varchar2 default hr_api.g_varchar2,
370: p_validate in boolean default false
371: );
372: --

Line 369: p_comments in varchar2 default hr_api.g_varchar2,

365: p_vendor_supply_id in number,
366: p_vendor_id in number default hr_api.g_number,
367: p_activity_version_id in number default hr_api.g_number,
368: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
369: p_comments in varchar2 default hr_api.g_varchar2,
370: p_validate in boolean default false
371: );
372: --
373: -- ----------------------------------------------------------------------------

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

406: -- default is false. The validation is controlled by a savepoint and
407: -- rollback mechanism. The savepoint is issued at the beginning of the
408: -- business process and is rollbacked at the end of the business process
409: -- when all the processing has been completed. The rollback is controlled
410: -- by raising and handling the exception hr_api.validate_enabled. We use
411: -- the exception because, by raising the exception with the business
412: -- process, we can exit successfully without having any of the 'OUT'
413: -- arguments being set.
414: --