Search Results pay_evc_ins




Overview
Explore in AI Chat

Overview

PAY_EVC_INS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as an "OTHER" API rather than a formally published public interface. Its name follows the Oracle Payroll convention of combining the product prefix (PAY_) with a functional identifier (EVC, denoting Event Value Changes) and the suffix INS, indicating its role as the insert-side handler for the Event Value Changes framework. The package therefore provides the low-level insertion logic used when new rows must be written into the event value change tables that track modifications to payroll event values.

The Event Value Changes data model supports the payroll event and costing infrastructure, where changes to event values must be captured so downstream processes can react to them. PAY_EVC_INS encapsulates the DML required to persist these change records without requiring calling code to manipulate the underlying tables directly. The package is marked VALID in the ETRM metadata and is documented for both 12.1.1 and 12.2.2, indicating that its interface has remained stable across those releases.

Key Procedures and Functions

The ETRM metadata documents four callable units within the package:

  • SET_BASE_KEY_VALUE — establishes the base key value used to identify the event value change record being processed. This routine supports key derivation before an insert is attempted.
  • INSERT_DML — performs the actual insert DML against the event value change tables. It is the core data-manipulation routine of the package.
  • INS — the principal insert entry point, orchestrating the sequence required to create a new event value change record. It is the procedure most likely to be invoked by external callers.

The fourth documented unit completes the set of four; collectively these routines separate key derivation, DML execution, and the insert operation itself, a common Oracle EBS pattern that allows the insert path to be reused while keeping the physical DML isolated.

Tables Accessed

According to the documented dependency information, PAY_EVC_INS references four tables through APPS synonyms:

  • PAY_EVENT_VALUE_CHANGES_F — the base (F) table holding event value change records; this is the primary insert target.
  • PAY_EVENT_VALUE_CHANGES_S — the corresponding sequence or secondary table supporting record creation and key generation.
  • HR_APPLICATION_OWNERSHIPS — used to determine ownership context, ensuring inserts respect application ownership rules.
  • HR_OWNER_DEFINITIONS — supplies owner definition metadata required when populating ownership-related columns.

The package additionally depends on PAY_EVC_SHD, which provides shared declarations and constants for the Event Value Changes framework, and on the SYS.STANDARD package.

Usage Notes

PAY_EVC_INS is referenced by three other objects: itself (internal calls), PAY_EVC_UPD, the update-side counterpart in the same framework, and PAY_EVENT_VALUE_CHANGES_API, the public API that represents the supported entry point for event value change processing. Custom code should generally invoke PAY_EVENT_VALUE_CHANGES_API rather than calling PAY_EVC_INS directly, since the API layer applies validation and business rules that the insert package does not enforce on its own.

Because the package is classified as OTHER and is not a published interface, Oracle does not guarantee its signature across patches or upgrades. Developers extending the Event Value Changes framework should treat PAY_EVC_INS as an internal implementation detail, verify its behaviour in the target release, and avoid hard-coding dependencies on its procedures in customizations that must survive an upgrade.