Search Results per_abv_ovn




Overview

PER_ABV_SHD is a shadow (SHD) validation package within the Oracle EBS Human Resources (PER) schema, owned by the APPS schema and classified under the "OTHER" API category. It supports the Assignment Budget Values (ABV) business area, which stores and maintains budget-related assignment attributes such as budgeted headcount and budgeted FTE against an assignment. The package encapsulates the low-level logic required to validate and apply changes to the PER_ASSIGNMENT_BUDGET_VALUES_F table, including effective date handling, row locking, and update-mode determination. It is not intended for direct invocation by end users; instead it functions as a supporting layer beneath the public ABV business packages (PER_ABV_BUS, PER_ABV_INS, PER_ABV_UPD, PER_ABV_DEL, and PER_ABV_OVN), which in turn are called by the Assignment Budget Values form and related HR processes. The "SHD" suffix and the presence of an API_DML_STATUS mechanism indicate that this is a shadow package that records the success or failure of DML operations performed on its behalf, so that the calling business layer can report accurate outcomes to the user interface or to concurrent processing.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within PER_ABV_SHD. Their names and roles are:

  • RETURN_API_DML_STATUS — Returns the overall DML status of the most recent API call, allowing callers to determine whether the operation succeeded or failed.
  • CONSTRAINT_ERROR — Handles or reports constraint-related errors raised during DML against the ABV table, translating them into a form the business layer can interpret.
  • API_UPDATING — Indicates whether an update operation is currently being performed through the API, typically used to control downstream logic within the package.
  • FIND_DT_UPD_MODES — Determines the correct date-track update modes to apply when an update affects dated (effective-dated) rows.
  • FIND_DT_DEL_MODES — Determines the correct date-track deletion modes when a dated row is removed or end-dated.
  • UPD_EFFECTIVE_END_DATE — Sets or adjusts the effective end date on an existing ABV row, supporting date-tracked changes.
  • LCK — Performs row locking to prevent concurrent modification of ABV records during validation and DML.
  • CONVERT_ARGS — Converts incoming arguments into the internal representation expected by the ABV API routines.

Tables Accessed

The package references the underlying ABV table through the APPS synonym PER_ASSIGNMENT_BUDGET_VALUES_F, which is the primary target of its validation and DML support logic. In addition, the metadata lists a dependency on ALL_CONSTRAINTS, an Oracle data dictionary view used to inspect database constraint definitions. This dependency confirms that PER_ABV_SHD performs constraint-aware validation (consistent with the CONSTRAINT_ERROR routine) rather than relying solely on hard-coded rules. Because the package sits beneath the ABV business layer, it is responsible for the accurate maintenance of effective-dated ABV rows within PER_ASSIGNMENT_BUDGET_VALUES_F.

Usage Notes

PER_ABV_SHD is referenced by five ABV packages: PER_ABV_BUS, PER_ABV_INS, PER_ABV_UPD, PER_ABV_DEL, and PER_ABV_OVN. These form the standard invocation path. Typical use is through the Assignment Budget Values form in Oracle HRMS, where insert, update, delete, and override actions against assignment budget values trigger the corresponding ABV business package, which delegates validation and DML support to PER_ABV_SHD. Custom PL/SQL should not call PER_ABV_SHD directly, since its procedures depend on the calling context established by the business layer; developers integrating with assignment budget values should use the documented PER_ABV business APIs instead. Because the package manipulates effective dates and locks rows, it must be executed in a transaction that respects date-tracked entity rules, and any error surfaced through CONSTRAINT_ERROR or RETURN_API_DML_STATUS should be handled by the caller before committing. This package is valid in Oracle EBS 12.1.1 and 12.2.2.