Search Results per_contracts_f_aru_aru

Overview

APPS.PAY_DYT_CONTRACTS_PKG is a dynamically generated PL/SQL package body that implements dynamic trigger logic for the PER_CONTRACTS_F table, the base table of the Oracle EBS Payroll contracts entity. The package belongs to the Oracle Payroll (PAY) schema and is classified under ETRM as an "OTHER" API, meaning it is neither a public business API nor a purely internal utility, but a generated mechanism invoked implicitly to enforce business rules on the Contracts table.

The header comment identifies the package as generated on 30-MAR-2009 and explicitly warns that the code must not be changed manually. It was produced to support dynamic triggers, where the preference between a database trigger and a package-based trigger is controlled through the Dated Table form. When a table is registered for dynamic trigger support, Oracle Payroll generates a package such as this one, and the dynamic trigger mechanism either calls this package implicitly (through a row-level trigger, the "rhi" hook) or explicitly from non-API packages that maintain data on PER_CONTRACTS_F. This design allows trigger logic to be regenerated centrally rather than maintained in hand-coded database triggers.

Key Procedures and Functions

The ETRM metadata documents four procedures in this package body:

• PER_CONTRACTS_F_ARU_ARU — Represents the dynamic trigger code for the UPDATE action on PER_CONTRACTS_F. The naming convention embeds the table name, trigger abbreviation (ARU = After Row Update), and the dynamic trigger suffix. Its documented description is "Continuous Calculation Trigger on Update of PER_CONTRACTS_F," with the full trigger name PER_CONTRACTS_F_ARU. The procedure accepts the new column values (including the ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns) as IN parameters so it can evaluate changed values and drive continuous calculation processing.
• AFTER_INSERT — The generated handler executed when a row is inserted into PER_CONTRACTS_F, supplying the corresponding dynamic trigger logic for insert events.
• AFTER_UPDATE — The generated handler executed when a row is updated, complementing the ARU_ARU procedure in processing post-update logic.
• AFTER_DELETE — The generated handler executed when a row is deleted, allowing the package to respond to removal of contracts data.

All four procedures are generated artifacts; their parameter signatures are produced automatically from the table definition and must not be modified. The ARU_ARU procedure is the most heavily documented, as it is the specific entry point surfaced when users search for "per_contracts_f_aru_aru."

Tables Accessed

The sole documented base table is PER_CONTRACTS_F, the Contracts table in the Oracle Payroll/HR schema. Because the package implements continuous calculation trigger logic, references to PER_CONTRACTS_F occur through the calling trigger (the row-level hook on the table), while the procedure bodies typically read and write related payroll and contract records to perform the calculation. The ETRM extract does not enumerate additional synonym-accessed tables, though continuous calculation processing ordinarily touches payroll assignment and element entry data. The metadata further notes that this package is referenced by three other packages within APPS, indicating that the generated trigger entry points are called from higher-level payroll processing packages rather than solely from database triggers.

Usage Notes

PAY_DYT_CONTRACTS_PKG is not intended for direct invocation by developers. It is wired into the EBS runtime in two ways. First, it is called implicitly by the table row-level trigger (the rhi mechanism) attached to PER_CONTRACTS_F, so any DML against contracts executed through the standard forms or business flows causes the appropriate AFTER_INSERT, AFTER_UPDATE, or AFTER_DELETE procedure to fire. Second, it is called explicitly from non-API packages and from the three referencing packages that maintain contracts data, ensuring consistent behavior when contract records are manipulated programmatically.

Because the package is regenerated whenever the dynamic trigger definition is refreshed through the Dated Table form, manual customization is unsupported and any edits will be overwritten. Oracle EBS 12.1.1 and 12.2.2 behave identically in this respect; the dynamic trigger framework is shared across both releases. Developers diagnosing continuous calculation issues on contracts should inspect this package's generated logic and the Dated Table registration rather than modifying the PL/SQL directly. The "per_contracts_f_aru_aru" search term corresponds precisely to the UPDATE trigger procedure described above, which is the routine most commonly traced when troubleshooting calculation behavior triggered by contract updates.