Search Results pay_bth_rki

Overview

PAY_BTH_RKI is a database package in the APPS schema of Oracle E-Business Suite, classified within the ETRM repository as an "OTHER" API rather than a public or private PL/SQL API. The suffix "RKI" follows Oracle's standard naming convention for row-level trigger implementation packages — specifically the "Row Keeping Insert" variant. Packages bearing this suffix are not intended to be called directly by application logic or custom code; instead, they contain the procedural bodies that Oracle Forms or the database trigger framework invokes through the corresponding row-level trigger on a base table. In this instance, APPS.PAY_BTH_INS (the insert trigger handler on the underlying table) delegates to PAY_BTH_RKI to perform the actual insert-time processing.

The package belongs to the Payroll (PAY) product family, and the "BTH" component identifies the underlying entity as part of the payroll batch header/distribution structure maintained by Oracle Payroll. Its principal role is to support automatic auditing and record maintenance whenever a row is inserted into that base table, ensuring consistent population of audit columns and other derived values required by the application's data integrity model.

Key Procedures and Functions

ETRM documents a single procedure or function within the package:

• AFTER_INSERT — Executes the row-level processing associated with an AFTER INSERT event on the underlying Payroll base table. This routine handles audit and maintenance logic — typically stamping WHO columns (creation date, created-by, last-update attributes), deriving key or reference values, and any dependent side effects that must occur once the insert has been registered. ETRM does not document the formal parameter list; consistent with standard Oracle trigger-body conventions, it is presumed to accept the row's column values and/or a trigger context that identifies the affected record.

No other procedures or functions are exposed by this package. Its body exists solely to service the insert path and does not represent a callable business API.

Tables Accessed

ETRM lists no tables accessed through APPS synonyms. This is consistent with the package's narrow purpose: as a trigger implementation body, PAY_BTH_RKI typically operates on the row supplied by the invoking trigger context (the :NEW pseudo-record) rather than issuing standalone SELECT or DML against the base table. Any data manipulation is performed implicitly through the trigger's own insert operation, with the package contributing derived and audit values to that row. The absence of documented synonym-based table references confirms that the package does not perform independent, set-based queries against application tables.

Usage Notes

PAY_BTH_RKI is not a public interface and should not be invoked from custom code, concurrent programs, or Oracle Forms business logic. It is called exclusively by the trigger layer: APPS.PAY_BTH_INS references PAY_BTH_RKI during the insert processing path on the Payroll base table. The package's dependency on STANDARD indicates a standard PL/SQL environment requirement.

Because the package is marked VALID and is referenced by only one other database object, it is tightly coupled to the PAY_BTH_INS trigger and the base table it protects. Modification of this package carries significant risk: any change to its AFTER_INSERT logic affects every insert into the underlying Payroll table, including inserts performed by standard concurrent payroll processes, data loading utilities, and patching operations. Customization or extension of behavior at this layer should be performed through supported APIs and personalization frameworks rather than by altering the trigger implementation package directly. The package should be treated, in effect, as internal application infrastructure rather than as a supported extension point.