APPS.HXC_TKGQ_SHD dependencies on HR_API

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

140: --
141: -- Post Failure:
142: -- The Lck process can fail for three reasons:
143: -- 1) When attempting to lock the row the row could already be locked by
144: -- another user. This will raise the HR_Api.Object_Locked exception.
145: -- 2) The row which is required to be locked doesn't exist in the HR Schema.
146: -- This error is trapped and reported using the message name
147: -- 'HR_7220_INVALID_PRIMARY_KEY'.
148: -- 3) The row although existing in the HR Schema has a different object

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

151: -- 'HR_7155_OBJECT_INVALID'.
152: --
153: -- Developer Implementation Notes:
154: -- For each primary key and the object version number arguments add a
155: -- call to hr_api.mandatory_arg_error procedure to ensure that these
156: -- argument values are not null.
157: --
158: -- Access Status:
159: -- Internal Development Use Only.

Line 190: hr_api.mandatory_arg_error

186: l_proc := g_package||'lck';
187: hr_utility.set_location('Entering:'||l_proc, 5);
188: end if;
189: --
190: hr_api.mandatory_arg_error
191: (p_api_name => l_proc
192: ,p_argument => 'TK_GROUP_QUERY_ID'
193: ,p_argument_value => p_tk_group_query_id
194: );

Line 220: When HR_Api.Object_Locked then

216: --
217: -- We need to trap the ORA LOCK exception
218: --
219: Exception
220: When HR_Api.Object_Locked then
221: --
222: -- The object is locked therefore we need to supply a meaningful
223: -- error message.
224: --