Search Results pay_jp_dbi_pkg




Overview

The APPS.PAY_JP_DBI_PKG package is a Japanese localization utility within the Oracle E-Business Suite Payroll (PAY) module. Its single documented procedure, TRANSLATE, is a multilingual (MLS) maintenance routine whose purpose is to populate or refresh the translated name columns of Japanese payroll configuration entities. The header comment signature (pyjpdbi.pkh) and the "noship" designation indicate that this is an internal, seeded component rather than a customer-facing API, and that it was delivered outside the standard shipping object set. In EBS 12.1.1 and 12.2.2 the package is classified as OTHER under the APPS schema and exposes no public business API surface.

The operational problem it addresses is translation of the descriptive attributes attached to payroll elements, user-defined tables, columns, and rows. Japanese implementations frequently define these objects with Japanese-language names, and DBI (Database Item) metadata — the FastFormula values surfaced to users in Oracle Payroll and related self-service flows — must be presented consistently across enabled languages. PAY_JP_DBI_PKG centralizes that translation activity.

Key Procedures and Functions

The package specification documents exactly one procedure: TRANSLATE. Parameter lists are not published in the ETRM metadata, so no formal signature can be asserted; only the observable purpose should be relied upon. In practice, TRANSLATE is expected to iterate over the Japanese payroll definition entities, invoke the standard FND message/translation mechanisms, and insert or update the corresponding _TL (translated) rows so that each entity carries a value in every installed language. Because the package exposes no other callable unit, it is a purpose-built, single-function utility rather than a general-purpose library, and it should not be treated as an extension point for custom code. No overloads, private helpers, or version-specific variants are documented.

Tables Accessed

The ETRM metadata identifies the tables reached through APPS synonyms. The descriptive payroll entities whose translations are maintained are PAY_ELEMENT_TYPES_F, PAY_USER_TABLES, PAY_USER_COLUMNS, and PAY_USER_ROWS, each paired with its _TL counterpart. These represent element definitions and the user-defined table/column/row structures used to shape payroll input values. FastFormula-related objects include FF_DATABASE_ITEMS, FF_GLOBALS_F, and FF_USER_ENTITIES, again with their _TL translation tables where applicable. The package therefore reads source definitions and writes translated name and description columns.

Supporting reference data is drawn from FND_LANGUAGES, which supplies the set of installed and enabled languages to iterate over, and FND_LOOKUP_VALUES, which provides lookup-based display values that require language-specific rendering.

Usage Notes

This package is not referenced by any other documented package, and the metadata records no inbound dependencies. It is therefore invoked directly rather than through a chain of application logic. Typical invocation paths include run-once or periodic translation maintenance executed by an administrator, or a corrective run after new Japanese payroll definitions are created without accompanying translations. Because it is an MLS maintenance routine, it should not be scheduled as part of routine transactional processing; the operation is idempotent in intent but potentially expensive on large definition sets.

The package is a Japanese localization object and is relevant only where the Japanese Payroll localization is installed. In 12.2.2 the underlying tables remain in the APPS schema with the same synonym access pattern, so any custom invocation must be made against the APPS schema under a suitably privileged application user. Given the sparse published interface, implementations relying on this package should validate behavior in a cloned environment before execution in production.