Results for “delete_validate”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PAY_TDU_BUS is a private business-rules package within the Oracle E-Business Suite Payroll (PAY) module. It belongs to the Table Data Unit (TDU) layer generated by Oracle's Table Handler (Row Handler) infrastructure, and its header identifies it as the row handler for the PAY_TIME_DEFINITIONS entity (evidenced by the "pytdurhi.pkh" header comment and the PAY_TDU prefix, where "TDU" denotes the time definitions table). Its role is to hold the business-rule validation logic that must execute whenever a record in the time definitions table is inserted or deleted. The package deliberately separates validation rules from the physical DML performed by the corresponding table handler packages; the *_BUS layer governs *what* is permitted, while the shadow (SHD) and DML layers govern *how* the data is manipulated.

The package is classified as "OTHER" in the ETRM API registry, confirming that it is not a public, callable business API but an internal implementation component. The package specification declares two documented procedures, both intended strictly for internal row-handler use.

Key Procedures and Functions

• INSERT_VALIDATE — Controls the execution of all insert business-rules validation for the time definitions row handler. Per its embedded documentation, it is a private procedure invoked from the generated INS (insert) procedure. It accepts an effective date and a PL/SQL record structure (defined by PAY_TDU_SHD.G_REC_TYPE) carrying the row values being inserted. On success, processing continues; on failure, errors are not handled within this procedure unless explicitly coded. Developers are advised to implement business rules here as straight procedure or function calls, avoiding conditional branching where possible.
• DELETE_VALIDATE — Performs the equivalent role for the delete path. It is called from the generated DEL procedure and controls all delete-time business-rules validation against the time definitions record. Like INSERT_VALIDATE, it receives the effective date and record structure, and applies the same error-handling and implementation conventions.

No update or query validation procedures are documented for this package, and no parameter lists beyond the standard effective-date and record-structure pattern are described in the available metadata.

Tables Accessed

The only documented table referenced through APPS synonyms is PAY_TIME_DEFINITIONS. This table stores the time definition records used by Oracle Payroll and related time-and-labor processing. Because PAY_TDU_BUS is a validation-only layer, it does not itself perform inserts, updates, or deletes on this table; the actual DML is executed by the companion table handler procedures. INSERT_VALIDATE and DELETE_VALIDATE may read PAY_TIME_DEFINITIONS (and, in custom implementations, related reference tables) to confirm that a proposed insert or delete satisfies organizational and application business rules before the row handler proceeds.

Usage Notes

PAY_TDU_BUS is invoked automatically and indirectly. It is never called by end users or by standard public APIs; rather, the generated row handler packages call INSERT_VALIDATE from the insert path and DELETE_VALIDATE from the delete path whenever a time definition record is created or removed. In a standard Oracle EBS 12.1.1 or 12.2.2 environment, such operations are triggered through the Payroll setup forms (for example, the Time Definitions maintenance window), through concurrent processes, or through dataloader/API-based loading routines that ultimately route through the row handler.

Two other packages in the ETRM registry reference PAY_TDU_BUS, confirming its position as a dependent component within the time definitions row-handler stack. Because the package is marked "Internal Row Handler Use Only," direct invocation from custom code is not supported: customers needing to enforce additional validation should extend the business-rules layer through Oracle's supported table-handler extension mechanisms (the CBO/customization hooks) rather than by calling these procedures directly. Any modification to the generated code is overwritten during patching or upgrade, so the supported approach is to attach custom logic through the designated extension points. The presence of the effective-date parameter also means validation logic must be date-effective, aligning with the effective-dating behaviour of the underlying time definitions data.