[Home] [Help]
105: -- {Start Of Comments}
106: --
107: -- Description:
108: -- This procedure is called when a constraint has been violated (i.e.
109: -- The exception hr_api.check_integrity_violated,
110: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
111: -- hr_api.unique_integrity_violated has been raised).
112: -- The exceptions can only be raised as follows:
113: -- 1) A check constraint can only be violated during an INSERT or UPDATE
106: --
107: -- Description:
108: -- This procedure is called when a constraint has been violated (i.e.
109: -- The exception hr_api.check_integrity_violated,
110: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
111: -- hr_api.unique_integrity_violated has been raised).
112: -- The exceptions can only be raised as follows:
113: -- 1) A check constraint can only be violated during an INSERT or UPDATE
114: -- dml operation.
107: -- Description:
108: -- This procedure is called when a constraint has been violated (i.e.
109: -- The exception hr_api.check_integrity_violated,
110: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
111: -- hr_api.unique_integrity_violated has been raised).
112: -- The exceptions can only be raised as follows:
113: -- 1) A check constraint can only be violated during an INSERT or UPDATE
114: -- dml operation.
115: -- 2) A parent integrity constraint can only be violated during an
119: -- 4) A unique integrity constraint can only be violated during INSERT or
120: -- UPDATE dml operation.
121: --
122: -- Prerequisites:
123: -- 1) Either hr_api.check_integrity_violated,
124: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
125: -- hr_api.unique_integrity_violated has been raised with the subsequent
126: -- stripping of the constraint name from the generated error message
127: -- text.
120: -- UPDATE dml operation.
121: --
122: -- Prerequisites:
123: -- 1) Either hr_api.check_integrity_violated,
124: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
125: -- hr_api.unique_integrity_violated has been raised with the subsequent
126: -- stripping of the constraint name from the generated error message
127: -- text.
128: -- 2) Standalone validation test which corresponds with a constraint error.
121: --
122: -- Prerequisites:
123: -- 1) Either hr_api.check_integrity_violated,
124: -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
125: -- hr_api.unique_integrity_violated has been raised with the subsequent
126: -- stripping of the constraint name from the generated error message
127: -- text.
128: -- 2) Standalone validation test which corresponds with a constraint error.
129: --
386: --
387: -- Post Failure:
388: -- The Lck process can fail for three reasons:
389: -- 1) When attempting to lock the row the row could already be locked by
390: -- another user. This will raise the HR_Api.Object_Locked exception.
391: -- 2) The row which is required to be locked doesn't exist in the HR Schema.
392: -- This error is trapped and reported using the message name
393: -- 'HR_7220_INVALID_PRIMARY_KEY'.
394: -- 3) The row although existing in the HR Schema has a different object
405: -- {End Of Comments}
406: -- ----------------------------------------------------------------------------
407: Procedure lck
408: (p_effective_date in date
409: ,p_datetrack_mode in varchar2 default hr_api.g_update
410: ,p_placement_id in number
411: ,p_object_version_number in number
412: ,p_validation_start_date out nocopy date
413: ,p_validation_end_date out nocopy date