Search Results pay_ter_ins




Overview
Explore in AI Chat

Overview

PAY_TER_INS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified within the ETRM repository under the generic API classification OTHER. Its name follows the Oracle naming convention for termination-related database objects; the PAY_TER prefix associates it with the Oracle Payroll termination processing family, and the _INS suffix indicates an insert-oriented role. The package operates in support of termination element template configuration, providing the programmatic layer through which termination template exclusion rules are inserted into the underlying payroll tables. In this capacity it functions as a low-level data maintenance utility rather than a user-facing business API, and it exists to isolate the insert logic required when the termination element template framework must persist new exclusion rule records. The package maintains a status of VALID in the documented environment, confirming that it compiles cleanly against its declared dependencies under EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM documentation records a single documented program unit within PAY_TER_INS, identified as INS.

  • INS — The package's sole documented procedure, responsible for the insertion of termination element template exclusion rule data. Consistent with its naming and the package's dependency profile, INS encapsulates the DML logic that adds rows to the exclusion rules tables accessed by the package. Its purpose is to centralize the insert operation so that calling programs do not embed direct SQL against these payroll configuration tables. No parameter list is documented in the ETRM metadata, and none should be assumed; the exact signature must be confirmed from the deployed package specification in the target instance.

The package specification and package body are both listed among the object's subcomponents, and the object is additionally documented as referencing itself, indicating internal recursive or helper usage within the body.

Tables Accessed

The documented table references, resolved through APPS synonyms, are:

  • PAY_TEMPLATE_EXCLUSION_RULES — the base transactional table holding element template exclusion rules used during termination processing. The INS procedure writes records to this table.
  • PAY_TEMPLATE_EXCLUSION_RULES_S — the corresponding shadow table that stores the audit and correction history for the base table. Inserts into the base table are mirrored into this table so that Oracle Forms-based maintenance and the underlying payroll engine remain consistent.

PAY_TER_INS additionally depends on the APPS-owned package PAY_TER_SHD, whose suffix indicates shared or shadow processing routines that support the same termination table family. This dependency suggests that PAY_TER_INS delegates part of its insert handling, most likely the shadow-row maintenance for PAY_TEMPLATE_EXCLUSION_RULES_S, to PAY_TER_SHD rather than issuing the shadow insert directly.

Usage Notes

PAY_TER_INS is not intended for direct invocation by end users. It is an internal implementation package invoked by higher-level payroll configuration code. The ETRM dependency list documents exactly one referencing package: APPS.PAY_IN_ELEMENT_TEMPLATE_PKG, which owns the element template setup logic and calls PAY_TER_INS to persist exclusion rule rows as part of termination template maintenance. The self-reference to PAY_TER_INS in the referenced-by list indicates internal calls between units of the same package body.

In practice the package executes in the context of termination element template configuration, triggered when template exclusion rules are created through the payroll setup forms or through batch setup processes that populate element templates. Because the exclusion rule tables are date-tracked, callers must rely on this package, or the parent processing package, to keep the shadow table synchronized; direct DML against PAY_TEMPLATE_EXCLUSION_RULES outside this framework risks corrupting the date-tracked configuration data. Custom code should invoke PAY_IN_ELEMENT_TEMPLATE_PKG rather than PAY_TER_INS wherever possible, since the parent package controls validation and sequencing that the lower-level insert routine does not enforce. Any modification of termination template configuration through SQL or custom PL/SQL should be followed by concurrent request submission to regenerate the relevant payroll objects, ensuring the changes are reflected in element processing.