Search Results pay_ptt_rki

Overview

PAY_PTT_RKI is a row-level database trigger implementation package within the Oracle EBS Payroll (PAY) module. The suffix convention "_RKI" identifies the package as part of Oracle Forms' server-side trigger infrastructure, specifically a Row-Keep-Insert handler that fires after a new row is created on a database table. This package encapsulates the PL/SQL logic required to execute post-insert processing for its associated base table — in this case, the PAY_PTT (Payroll User Table) entity — without embedding that logic directly into compiled trigger code, thereby improving maintainability and allowing the trigger body to remain a thin wrapper around a packaged procedure.

In Oracle EBS 12.1.1 and 12.2.2, such "I" handler packages are generated artifact layers sitting between the database table and the Forms user interface. They exist to guarantee that insert-time business rules execute consistently no matter whether the row is created through the Forms UI, an interface API, or a batch process. The package is owned by APPS and is classified as an OTHER API in the ETRM repository, meaning it is a supporting internal component rather than a public, customer-callable API.

The package header is timestamped from the 12.0 development stream ($Header: pypttrhi.pkh 120.0) and remains in the shipped file system as "noship", indicating it is distributed but not intended for direct customer modification.

Key Procedures and Functions

ETRM documents a single procedure within this package:

• AFTER_INSERT — The row-level post-insert handler invoked immediately after a new record is successfully written to the underlying user-table row. Its parameter set covers the user table identifier, the language and source language of the inserted row, the user table name, and a descriptive row title. The procedure is responsible for any post-insert side effects required by the Payroll user-table framework, such as propagating contextual attributes that cannot be derived until the primary row exists. No additional procedures or functions are documented for this package.

Tables Accessed

The ETRM metadata does not enumerate base tables referenced through APPS synonyms for PAY_PTT_RKI, because access occurs indirectly: the AFTER_INSERT handler operates against the user-defined table identified at runtime by the p_user_table_id and p_user_table_name parameters rather than against a statically bound table. The package therefore manipulates rows in whatever user table the parent form or API is currently maintaining, using the passed identifiers to resolve the correct target. Because PAY_PTT is the parent entity named in the package, the practical write path is the Payroll user-table row just inserted, with language-attribute handling applied for the row's description and title columns.

Usage Notes

PAY_PTT_RKI is not invoked directly by end users or by conventional custom code. It is called by the generated database trigger on the corresponding base table whenever a Forms block — or an equivalent programmatic insert path — commits a new row. The ETRM repository records that the package is referenced by one other package, confirming its role as a subordinate handler in the Payroll trigger-handler chain rather than an entry-point API.

Practitioners should treat PAY_PTT_RKI as read-only shipped code. Customizations requiring additional insert-time behavior should be implemented through a supported hook or by extending the calling package, not by editing this handler, since regeneration or patching of the Payroll trigger layer will overwrite modifications. Because it is an internal handler, it carries no Oracle support commitment for direct invocation and should not be called from standalone concurrent programs or client extensions.