Search Results pay_ptt_ins




Overview
Explore in AI Chat

Overview

PAY_PTT_INS is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite, classified under the Oracle HRMS/Payroll product family (the "PAY" prefix). The package forms part of the Payroll Translation Tables (PTT) infrastructure, which supports the maintenance of translated, multi-language content for user-defined payroll objects. Its name follows the EBS naming convention shared across the ETRM toolset, where "PTT" identifies the Payroll Translation Table domain and "INS" denotes an insert-oriented interface package.

In the Oracle EBS multi-language architecture, seed data and user-defined payroll objects must be presented in the session language and, where required, stored or propagated across all installed languages. PAY_PTT_INS exists to provide the insertion layer for the translation (TL) component of these objects, working in concert with sibling packages such as PAY_PTT_BUS (business logic), PAY_PTT_RKI (row key information / primary key resolution), and PAY_PTT_SHD (shadow table maintenance). The package is recorded as VALID at version 12.1.1 and 12.2.2, and is not referenced by any other database object, indicating that it is invoked as a top-level API rather than as an internal dependency of another package.

Key Procedures and Functions

The ETRM metadata documents a single procedure for this package:

  • INS_TL — The sole documented entry point, whose name follows the standard EBS translation-insert convention in which the "_TL" suffix indicates operation against a translation table. INS_TL performs the insertion of translated rows for the parent payroll user-table entity. It operates within the framework of HR_API, which supplies the standard error-handling, validation, and API-registration wrapper behavior, and HR_MULTI_MESSAGE, which provides the multi-language message handling used to report validation failures consistently across installed languages.

No further documented procedures or functions are recorded, and parameter signatures are intentionally not reproduced here; the procedure's purpose is limited to the insert of translation records for the associated base entity, with multi-language validation delegated to the HR API and messaging infrastructure.

Tables Accessed

The package accesses the following tables through APPS synonyms:

  • PAY_USER_TABLES_TL — The translation table for user-defined payroll tables. INS_TL inserts the language-specific descriptive content for its parent entity into this table, which stores the translated name and description keyed by language.
  • FND_LANGUAGES — The Oracle Application Object Library language definition table. The package reads this table to validate the target language code and to determine which installed languages require translation rows, ensuring consistency with the application's configured language set.

The dependency list additionally cites HR_API, HR_MULTI_MESSAGE, HR_UTILITY, PAY_PTT_BUS, PAY_PTT_RKI, and PAY_PTT_SHD. These are code dependencies rather than data dependencies, but they confirm that insertion is coordinated with the parent business object and its shadow-table maintenance before the translation row is committed.

Usage Notes

PAY_PTT_INS is typically invoked indirectly rather than through a standalone form or concurrent program in the standard Oracle EBS 12.1.1 / 12.2.2 applications. Audit and diagnostic output for the same functional area (the "System Administrator > Oracle Applications Manager > Diagnostic" path, and the "Payroll > (N) Translation" navigations in HRMS) exercise the underlying business package PAY_PTT_BUS, which in turn drives the insert and row-key packages. Custom code and migration scripts that create user-defined payroll tables in multiple languages will call INS_TL directly, supplying the parent row identifier and the target language. Because the package raises errors through HR_API and HR_MULTI_MESSAGE, callers should always inspect the standard error stack and the returned message table rather than relying on SQLCODE alone. Direct DML against PAY_USER_TABLES_TL is not supported; INS_TL is the supported insertion path and preserves the integrity checks, language validations, and audit conventions required by the Payroll translation framework.