eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.VSP_API dependencies on HR_API

Line 345: -- The exception hr_api.check_integrity_violated,

341: -- {Start Of Comments}
342: --
343: -- Description:
344: -- This procedure is called when a constraint has been violated (i.e.
345: -- The exception hr_api.check_integrity_violated,
346: -- hr_api.parent_integrity_violated or hr_api.child_integrity_violated has
347: -- been raised).
348: -- The exceptions can only be raised as follows:
349: -- 1) A check constraint can only be violated during an INSERT or UPDATE

Line 346: -- hr_api.parent_integrity_violated or hr_api.child_integrity_violated has

342: --
343: -- Description:
344: -- This procedure is called when a constraint has been violated (i.e.
345: -- The exception hr_api.check_integrity_violated,
346: -- hr_api.parent_integrity_violated or hr_api.child_integrity_violated has
347: -- been raised).
348: -- The exceptions can only be raised as follows:
349: -- 1) A check constraint can only be violated during an INSERT or UPDATE
350: -- dml operation.

Line 357: -- Either hr_api.check_integrity_violated, hr_api.parent_integrity_violated

353: -- 3) A child integrity constraint can only be violated during an
354: -- DELETE dml operation.
355: --
356: -- Pre Conditions:
357: -- Either hr_api.check_integrity_violated, hr_api.parent_integrity_violated
358: -- or hr_api.child_integrity_violated has been raised with the subsequent
359: -- stripping of the constraint name from the generated error message text.
360: --
361: -- In Arguments:

Line 358: -- or hr_api.child_integrity_violated has been raised with the subsequent

354: -- DELETE dml operation.
355: --
356: -- Pre Conditions:
357: -- Either hr_api.check_integrity_violated, hr_api.parent_integrity_violated
358: -- or hr_api.child_integrity_violated has been raised with the subsequent
359: -- stripping of the constraint name from the generated error message text.
360: --
361: -- In Arguments:
362: -- p_constraint_name is in upper format and is just the constraint name

Line 478: When hr_api.check_integrity_violated Then

474: g_api_dml := false; -- Unset the api dml status
475: --
476: hr_utility.set_location(' Leaving:'||l_proc, 10);
477: Exception
478: When hr_api.check_integrity_violated Then
479: -- A check constraint has been violated
480: g_api_dml := false; -- Unset the api dml status
481: constraint_error
482: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 482: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

478: When hr_api.check_integrity_violated Then
479: -- A check constraint has been violated
480: g_api_dml := false; -- Unset the api dml status
481: constraint_error
482: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
483: When hr_api.parent_integrity_violated then
484: -- Parent integrity has been violated
485: g_api_dml := false; -- Unset the api dml status
486: constraint_error

Line 483: When hr_api.parent_integrity_violated then

479: -- A check constraint has been violated
480: g_api_dml := false; -- Unset the api dml status
481: constraint_error
482: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
483: When hr_api.parent_integrity_violated then
484: -- Parent integrity has been violated
485: g_api_dml := false; -- Unset the api dml status
486: constraint_error
487: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 487: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

483: When hr_api.parent_integrity_violated then
484: -- Parent integrity has been violated
485: g_api_dml := false; -- Unset the api dml status
486: constraint_error
487: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
488: When Others Then
489: g_api_dml := false; -- Unset the api dml status
490: Raise;
491: End insert_dml;

Line 560: When hr_api.check_integrity_violated Then

556: --
557: hr_utility.set_location(' Leaving:'||l_proc, 10);
558: --
559: Exception
560: When hr_api.check_integrity_violated Then
561: -- A check constraint has been violated
562: g_api_dml := false; -- Unset the api dml status
563: constraint_error
564: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 564: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

560: When hr_api.check_integrity_violated Then
561: -- A check constraint has been violated
562: g_api_dml := false; -- Unset the api dml status
563: constraint_error
564: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
565: When hr_api.parent_integrity_violated then
566: -- Parent integrity has been violated
567: g_api_dml := false; -- Unset the api dml status
568: constraint_error

Line 565: When hr_api.parent_integrity_violated then

561: -- A check constraint has been violated
562: g_api_dml := false; -- Unset the api dml status
563: constraint_error
564: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
565: When hr_api.parent_integrity_violated then
566: -- Parent integrity has been violated
567: g_api_dml := false; -- Unset the api dml status
568: constraint_error
569: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 569: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

565: When hr_api.parent_integrity_violated then
566: -- Parent integrity has been violated
567: g_api_dml := false; -- Unset the api dml status
568: constraint_error
569: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
570: When Others Then
571: g_api_dml := false; -- Unset the api dml status
572: Raise;
573: End update_dml;

Line 644: When hr_api.child_integrity_violated then

640: --
641: hr_utility.set_location(' Leaving:'||l_proc, 10);
642: --
643: Exception
644: When hr_api.child_integrity_violated then
645: -- Child integrity has been violated
646: g_api_dml := false; -- Unset the api dml status
647: constraint_error
648: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 648: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

644: When hr_api.child_integrity_violated then
645: -- Child integrity has been violated
646: g_api_dml := false; -- Unset the api dml status
647: constraint_error
648: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
649: When Others Then
650: g_api_dml := false; -- Unset the api dml status
651: Raise;
652: End delete_dml;

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

927: --
928: -- Post Failure:
929: -- The Lck process can fail for three reasons:
930: -- 1) When attempting to lock the row the row could already be locked by
931: -- another user. This will raise the HR_Api.Object_Locked exception.
932: -- 2) The row which is required to be locked doesn't exist in the HR Schema.
933: -- This error is trapped and reported using the message name
934: -- 'HR_7155_OBJECT_INVALID'.
935: -- 3) The row although existing in the HR Schema has a different object

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

938: -- 'HR_7155_OBJECT_INVALID'.
939: --
940: -- Developer Implementation Notes:
941: -- For each primary key and the object version number arguments add a
942: -- call to hr_api.mandatory_arg_error procedure to ensure that these
943: -- argument values are not null.
944: --
945: -- {End Of Comments}
946: -- ----------------------------------------------------------------------------

Line 971: -- hr_api.check_mandatory_arg_error

967: hr_utility.set_location('Entering:'||l_proc, 5);
968: --
969: -- Add any mandatory argument checking here:
970: -- Example:
971: -- hr_api.check_mandatory_arg_error
972: -- (p_api_name => l_proc,
973: -- p_argument => 'object_version_number',
974: -- p_argument_value => p_object_version_number);
975: --

Line 996: When HR_Api.Object_Locked then

992: --
993: -- We need to trap the ORA LOCK exception
994: --
995: Exception
996: When HR_Api.Object_Locked then
997: --
998: -- The object is locked therefore we need to supply a meaningful
999: -- error message.
1000: --

Line 1118: If (p_rec.vendor_id = hr_api.g_number) then

1114: -- p_rec plsql record structure
1115: -- to see if a system default is being used. If a system default
1116: -- is being used then we must set to the 'current' argument value.
1117: --
1118: If (p_rec.vendor_id = hr_api.g_number) then
1119: p_rec.vendor_id := g_old_rec.vendor_id;
1120: End If;
1121: If (p_rec.activity_version_id = hr_api.g_number) then
1122: p_rec.activity_version_id := g_old_rec.activity_version_id;

Line 1121: If (p_rec.activity_version_id = hr_api.g_number) then

1117: --
1118: If (p_rec.vendor_id = hr_api.g_number) then
1119: p_rec.vendor_id := g_old_rec.vendor_id;
1120: End If;
1121: If (p_rec.activity_version_id = hr_api.g_number) then
1122: p_rec.activity_version_id := g_old_rec.activity_version_id;
1123: End If;
1124: If (p_rec.primary_supplier_flag = hr_api.g_varchar2) then
1125: p_rec.primary_supplier_flag := g_old_rec.primary_supplier_flag;

Line 1124: If (p_rec.primary_supplier_flag = hr_api.g_varchar2) then

1120: End If;
1121: If (p_rec.activity_version_id = hr_api.g_number) then
1122: p_rec.activity_version_id := g_old_rec.activity_version_id;
1123: End If;
1124: If (p_rec.primary_supplier_flag = hr_api.g_varchar2) then
1125: p_rec.primary_supplier_flag := g_old_rec.primary_supplier_flag;
1126: End If;
1127: If (p_rec.comments = hr_api.g_varchar2) then
1128: p_rec.comments := g_old_rec.comments;

Line 1127: If (p_rec.comments = hr_api.g_varchar2) then

1123: End If;
1124: If (p_rec.primary_supplier_flag = hr_api.g_varchar2) then
1125: p_rec.primary_supplier_flag := g_old_rec.primary_supplier_flag;
1126: End If;
1127: If (p_rec.comments = hr_api.g_varchar2) then
1128: p_rec.comments := g_old_rec.comments;
1129: End If;
1130: --
1131: -- Return the plsql record structure.

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

1332: -- default is false. The validation is controlled by a savepoint and
1333: -- rollback mechanism. The savepoint is issued at the beginning of the
1334: -- business process and is rollbacked at the end of the business process
1335: -- when all the processing has been completed. The rollback is controlled
1336: -- by raising and handling the exception hr_api.validate_enabled. We use
1337: -- the exception because, by raising the exception with the business
1338: -- process, we can exit successfully without having any of the 'OUT'
1339: -- arguments being set.
1340: --

Line 1393: Raise HR_Api.Validate_Enabled;

1389: --
1390: -- If we are validating then raise the Validate_Enabled exception
1391: --
1392: If p_validate then
1393: Raise HR_Api.Validate_Enabled;
1394: End If;
1395: --
1396: hr_utility.set_location(' Leaving:'||l_proc, 10);
1397: Exception

Line 1398: When HR_Api.Validate_Enabled Then

1394: End If;
1395: --
1396: hr_utility.set_location(' Leaving:'||l_proc, 10);
1397: Exception
1398: When HR_Api.Validate_Enabled Then
1399: --
1400: -- As the Validate_Enabled exception has been raised
1401: -- we must rollback to the savepoint
1402: --

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

1530: -- default is false. The validation is controlled by a savepoint and
1531: -- rollback mechanism. The savepoint is issued at the beginning of the
1532: -- business process and is rollbacked at the end of the business process
1533: -- when all the processing has been completed. The rollback is controlled
1534: -- by raising and handling the exception hr_api.validate_enabled. We use
1535: -- the exception because, by raising the exception with the business
1536: -- process, we can exit successfully without having any of the 'OUT'
1537: -- arguments being set.
1538: --

Line 1602: Raise HR_Api.Validate_Enabled;

1598: --
1599: -- If we are validating then raise the Validate_Enabled exception
1600: --
1601: If p_validate then
1602: Raise HR_Api.Validate_Enabled;
1603: End If;
1604: --
1605: hr_utility.set_location(' Leaving:'||l_proc, 10);
1606: Exception

Line 1607: When HR_Api.Validate_Enabled Then

1603: End If;
1604: --
1605: hr_utility.set_location(' Leaving:'||l_proc, 10);
1606: Exception
1607: When HR_Api.Validate_Enabled Then
1608: --
1609: -- As the Validate_Enabled exception has been raised
1610: -- we must rollback to the savepoint
1611: --

Line 1657: p_vendor_id in number default hr_api.g_number,

1653: -- ----------------------------------------------------------------------------
1654: Procedure upd
1655: (
1656: p_vendor_supply_id in number,
1657: p_vendor_id in number default hr_api.g_number,
1658: p_activity_version_id in number default hr_api.g_number,
1659: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
1660: p_comments in varchar2 default hr_api.g_varchar2,
1661: p_validate in boolean default false

Line 1658: p_activity_version_id in number default hr_api.g_number,

1654: Procedure upd
1655: (
1656: p_vendor_supply_id in number,
1657: p_vendor_id in number default hr_api.g_number,
1658: p_activity_version_id in number default hr_api.g_number,
1659: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
1660: p_comments in varchar2 default hr_api.g_varchar2,
1661: p_validate in boolean default false
1662: ) is

Line 1659: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,

1655: (
1656: p_vendor_supply_id in number,
1657: p_vendor_id in number default hr_api.g_number,
1658: p_activity_version_id in number default hr_api.g_number,
1659: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
1660: p_comments in varchar2 default hr_api.g_varchar2,
1661: p_validate in boolean default false
1662: ) is
1663: --

Line 1660: p_comments in varchar2 default hr_api.g_varchar2,

1656: p_vendor_supply_id in number,
1657: p_vendor_id in number default hr_api.g_number,
1658: p_activity_version_id in number default hr_api.g_number,
1659: p_primary_supplier_flag in varchar2 default hr_api.g_varchar2,
1660: p_comments in varchar2 default hr_api.g_varchar2,
1661: p_validate in boolean default false
1662: ) is
1663: --
1664: l_rec g_rec_type;

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

1726: -- default is false. The validation is controlled by a savepoint and
1727: -- rollback mechanism. The savepoint is issued at the beginning of the
1728: -- business process and is rollbacked at the end of the business process
1729: -- when all the processing has been completed. The rollback is controlled
1730: -- by raising and handling the exception hr_api.validate_enabled. We use
1731: -- the exception because, by raising the exception with the business
1732: -- process, we can exit successfully without having any of the 'OUT'
1733: -- arguments being set.
1734: --

Line 1794: Raise HR_Api.Validate_Enabled;

1790: --
1791: -- If we are validating then raise the Validate_Enabled exception
1792: --
1793: If p_validate then
1794: Raise HR_Api.Validate_Enabled;
1795: End If;
1796: --
1797: hr_utility.set_location(' Leaving:'||l_proc, 10);
1798: Exception

Line 1799: When HR_Api.Validate_Enabled Then

1795: End If;
1796: --
1797: hr_utility.set_location(' Leaving:'||l_proc, 10);
1798: Exception
1799: When HR_Api.Validate_Enabled Then
1800: --
1801: -- As the Validate_Enabled exception has been raised
1802: -- we must rollback to the savepoint
1803: --