Search Results pay_pct_ins




Overview
Explore in AI Chat

Overview

PAY_PCT_INS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Payroll (PAY) application module. Its name follows the Oracle naming convention for installation and setup utilities: "PCT" denotes the Payroll user-defined Column Table/definition domain, and "INS" indicates an insert-oriented utility. The package serves as a low-level loader that inserts translated (language-specific) definition rows into the repository that underpins user-defined columns in Payroll and related modules.

Introduced and maintained across both the 12.1.1 and 12.2.2 releases, PAY_PCT_INS is classified in the EBS Technical Reference Manual (ETRM) as an OTHER API — that is, a package that is syntactically valid and callable, but is not published or supported as a formal public API. It exists primarily to support the seed/definition load pathway for user column metadata, and is invoked indirectly by higher-level APIs and maintenance utilities rather than by end users or external integrations.

Key Procedures and Functions

ETRM documents a single entry point for this package:

  • INS_TL — The sole documented procedure. The "_TL" suffix is the standard EBS convention for translatable (language-dependent) entity handling. INS_TL performs the insert operation against the translation table for user column definitions, writing the language-specific name and description rows associated with a user-defined column. It is the mechanism through which a given column definition is made available in one or more installed languages.

No formal parameter list is published in the ETRM metadata; consumers should treat INS_TL as a private implementation routine and not build direct dependencies against its signature.

Tables Accessed

PAY_PCT_INS references the following tables through APPS synonyms:

  • PAY_USER_COLUMNS_TL — The translation table for user-defined columns. This is the primary write target: INS_TL inserts the language-specific display name and description rows that allow a user column definition to render correctly for each installed language.
  • FND_LANGUAGES — The Oracle Application Object Library table of installed and available languages. It is read to validate the target language code and, typically, to drive multi-language insertion or to confirm that a language is active before writing translation rows.

Usage Notes

PAY_PCT_INS is a supporting, non-public package. ETRM records that it is referenced by three other packages within APPS:

  • PAY_PCT_MNT_TL_ARI — a translation maintenance/generation package, which is the most likely direct caller of INS_TL during language-row creation.
  • PAY_USER_COLUMNS_PKG — the primary maintenance package for user column definitions.
  • PAY_USER_COLUMN_API — the public-facing API for creating and maintaining user columns, which ultimately funnels translation inserts down into this package.

Consequently, the package is normally invoked indirectly: through the Payroll user-column setup forms, through the PAY_USER_COLUMN_API when creating or updating a user column, or during translation maintenance runs that generate rows for newly installed languages. It is not a concurrent program entry point and carries no Oracle-seeded concurrent program association.

Because PAY_PCT_INS is classified as OTHER and is documented with only a single internal procedure, customizations should never call it directly. Direct inserts bypassing PAY_USER_COLUMN_API risk orphaning translation rows or violating the expected relationship between PAY_USER_COLUMNS_TL and its base definition table. Any requirement to add or extend user columns, or to add a language for an existing column, should be implemented through PAY_USER_COLUMN_API, which guarantees that this insertion logic and its validations are applied consistently in both 12.1.1 and 12.2.2 environments.