Search Results update_tl_row
Overview
PAY_JP_DBI_PKG is a Japanese localizations package in the Oracle EBS Payroll (PAY) module. Its principal purpose is to synchronize and translate the Japanese-language descriptive text associated with user-defined payroll tables, rows, and columns. These structures are defined through the "Define User Tables," "Define User Rows," and "Define User Columns" functionality and are widely used by Japanese payroll legislation to drive the DBI (Database Item) framework and associated element configuration. Because Oracle EBS stores the base definitions in the non-translated (base) tables and the localized Japanese text in corresponding "_TL" translation tables, the package reconciles the two sets of records so that Japanese users see correctly translated table names, row titles, ranges, and column names within the regional payroll setup and reporting flows.
Key Procedures and Functions
- TRANSLATE — The single documented procedure in the package body. It performs the synchronization of Japanese translated text against the base payroll user table, row, and column definitions. Internally it declares lookup-based range variables and drives three explicit cursors: csr_tab, which selects base and translated user tables filtered by range_or_match and Japanese legislation; csr_row, which selects base and translated user rows grouped by row identifier; and csr_col, which selects base and translated user column names. An internal function ja_installed verifies that the Japanese language is installed in FND_LANGUAGES (installed_flag of B or I) before any translation processing proceeds, guarding against unnecessary work when the JA language pack is absent.
The procedure name recorded in the user's search term ("update_tl_row") reflects the conceptual operation performed by TRANSLATE: updating the translated (_TL) rows that correspond to a given base user table row so that the Japanese-language description remains consistent with the base definition.
Tables Accessed
- PAY_USER_TABLES / PAY_USER_TABLES_TL — base and translated user table definitions; source for table name and row title translation.
- PAY_USER_ROWS_F / PAY_USER_ROWS_F_TL — base and translated user row ranges and names, grouped by user_row_id.
- PAY_USER_COLUMNS / PAY_USER_COLUMNS_TL — base and translated user column names.
- FND_LANGUAGES — installation check for Japanese (language_code 'JA').
- FF_DATABASE_ITEMS / FF_DATABASE_ITEMS_TL — FastFormula database item names and their Japanese translations.
- FF_GLOBALS_F / FF_GLOBALS_F_TL — FastFormula global value translations.
- FF_USER_ENTITIES — user entity definitions referenced for the DBI translation context.
- FND_LOOKUP_VALUES — lookup meanings used to derive range boundaries.
- PAY_ELEMENT_TYPES_F / PAY_ELEMENT_TYPES_F_TL — element type base and translated names.
Usage Notes
The package is typically invoked as a maintenance utility rather than from an end-user form. Common invocation points include payroll localization setup scripts, patch or post-install routines for the Japanese legislation, and custom concurrent programs or PL/SQL scripts run when user tables, rows, or columns are added or modified and their Japanese translations must be regenerated. ETRM records no other packages depending on PAY_JP_DBI_PKG, so its calls are generally either external (custom code, SQL*Plus, or concurrent manager) or triggered manually by a functional administrator. Because all cursors filter on legislation_code = 'JP' and business_group_id is null, the procedure applies only to global Japanese definitions. It should be run while the Japanese language is installed; otherwise the internal installation check causes it to exit without processing.
-
APPS.PAY_JP_DBI_PKG SQL Statements
12.1.1
-
APPS.PAY_JP_DBI_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PAY_JP_DBI_PKG
12.1.1
-
PACKAGE BODY: APPS.PAY_JP_DBI_PKG
12.2.2
-
APPS.AME_ITEM_CLASSES_API SQL Statements
12.2.2
-
APPS.AME_ACTION_TYPES_API SQL Statements
12.1.1
-
APPS.AME_ACTION_TYPES_API SQL Statements
12.2.2
-
APPS.AME_ITEM_CLASSES_API SQL Statements
12.1.1
-
PACKAGE: APPS.FF_DATABASE_ITEMS_PKG
12.1.1
-
APPS.AME_ACTIONS_API SQL Statements
12.1.1
-
PACKAGE: APPS.FF_DATABASE_ITEMS_PKG
12.2.2
-
APPS.AME_ACTIONS_API SQL Statements
12.2.2
-
APPS.AME_APPROVAL_GROUPS_LOAD_API SQL Statements
12.1.1
-
APPS.AME_APPROVAL_GROUPS_LOAD_API SQL Statements
12.2.2
-
APPS.AMV_C_CATEGORIES_PKG SQL Statements
12.1.1
-
APPS.AMV_C_CATEGORIES_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.AME_ITEM_CLASSES_API
12.1.1
-
PACKAGE BODY: APPS.AME_ITEM_CLASSES_API
12.2.2
-
PACKAGE BODY: APPS.AME_ACTION_TYPES_API
12.2.2
-
PACKAGE: APPS.AMV_C_CATEGORIES_PKG
12.1.1
-
PACKAGE BODY: APPS.AME_ACTION_TYPES_API
12.1.1
-
PACKAGE: APPS.AMV_C_CATEGORIES_PKG
12.2.2
-
APPS.FND_DOCUMENTS_PKG SQL Statements
12.2.2
-
APPS.FND_DOCUMENTS_PKG SQL Statements
12.1.1
-
APPS.AME_CALLING_APPS_API SQL Statements
12.2.2
-
PACKAGE BODY: APPS.AME_ACTIONS_API
12.2.2
-
PACKAGE BODY: APPS.AME_ACTIONS_API
12.1.1
-
APPS.AME_CALLING_APPS_API SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AME_APPROVAL_GROUPS_LOAD_API
12.1.1
-
PACKAGE BODY: APPS.AME_APPROVAL_GROUPS_LOAD_API
12.2.2
-
APPS.FF_DATABASE_ITEMS_PKG SQL Statements
12.2.2
-
APPS.FF_DATABASE_ITEMS_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AMV_C_CATEGORIES_PKG
12.2.2
-
PACKAGE BODY: APPS.AMV_C_CATEGORIES_PKG
12.1.1
-
PACKAGE BODY: APPS.AME_CALLING_APPS_API
12.1.1
-
PACKAGE BODY: APPS.AME_CALLING_APPS_API
12.2.2
-
PACKAGE BODY: APPS.FND_DOCUMENTS_PKG
12.1.1
-
PACKAGE: APPS.FND_DOCUMENTS_PKG
12.1.1
-
PACKAGE: APPS.FND_DOCUMENTS_PKG
12.2.2
-
PACKAGE BODY: APPS.FND_DOCUMENTS_PKG
12.2.2
-
PACKAGE BODY: APPS.FF_DATABASE_ITEMS_PKG
12.1.1
-
PACKAGE BODY: APPS.FF_DATABASE_ITEMS_PKG
12.2.2
-
APPS.PAY_JP_DBI_PKG dependencies on STANDARD
12.1.1
-
APPS.PAY_JP_DBI_PKG dependencies on HR_JP_STANDARD_PKG
12.1.1
-
APPS.PAY_JP_DBI_PKG dependencies on FF_DBI_UTILS_PKG
12.1.1
-
APPS.PAY_JP_DBI_PKG dependencies on FF_DBI_UTILS_PKG
12.2.2
-
APPS.HRDYNDBI dependencies on FF_DATABASE_ITEMS_PKG
12.1.1
-
APPS.HRDYNDBI dependencies on FF_DATABASE_ITEMS_PKG
12.2.2
-
APPS.FF_DATABASE_ITEMS_PKG dependencies on FND_GLOBAL
12.2.2
-
APPS.FF_DATABASE_ITEMS_PKG dependencies on FND_GLOBAL
12.1.1