Search Results hr_jp_standard_pkg




Overview
Explore in AI Chat

Overview

APPS.HR_JP_STANDARD_PKG is a Japanese localization utility package in Oracle E-Business Suite, delivered as part of the Oracle HRMS Japanese (JP) localization layer. Its business purpose is to provide centralized, reusable string, character, numeric, and date handling routines required by Japanese payroll, HR, and reporting processes. The package addresses two persistent requirements in the Japanese localization: conversion between half-width (hankaku) and full-width (zenkaku) character representations, and correct handling of Shift-JIS multibyte character data at the byte level.

The package body carries the version marker $Header: hrjpstnd.pkb 120.9 2006/12/05, indicating a long-lived localization component that is unshipped (noship) yet critical to dependent Japanese functionality. It is classified in the ETRM metadata as an OTHER API rather than a formal public API, meaning it is intended primarily for internal use by Oracle localization code, though it is exposed to the APPS schema.

The package declares two private record types, t_hankaku and t_zenkaku, which enumerate the character sets (upper and lower alphabets, numbers, symbols, kana, voiced kana, upper and lower kana, and Japanese symbols) for each width class. These constants are constructed at package initialization time using sjhextochar, which decodes Shift-JIS hexadecimal byte sequences into database character values. Session language and character set are captured via USERENV('LANGUAGE').

Key Procedures and Functions

The package exposes 29 documented procedures and functions. Core low-level conversion routines include HEXTOCHAR and CHARTOHEX, which translate between hexadecimal string representations and raw character data, and CHARTOSJHEX and SJHEXTOCHAR, which perform the equivalent conversion specifically against Shift-JIS byte encodings. These routines underpin the character-set constants used throughout the package.

Character-width conversion is handled by IS_HANKAKU and IS_ZENKAKU (predicates that test whether a character belongs to the half-width or full-width set), and by TO_HANKAKU and TO_ZENKAKU, which perform the actual transformation between widths. Related routines include UPPER_HANKAKU, LOWER_KANA, and UPPER_KANA, which normalize kana and alphabetic case within the half-width domain.

Text processing utilities include TRANSLATE2, an extended translation routine; STRIP, which removes unwanted characters; and RECURSIVE_REPLACE, which repeatedly applies substitution rules until no further change occurs. Numeric and validation helpers include ROUND2 for two-decimal rounding and IS_INTEGER for integer testing. Table and index helpers TO_TABLE and GET_INDEX_AT support lookup of character positions. Finally, TO_JP_CHAR and TO_JP_DATE format values into Japanese character and Japanese date representations.

Tables Accessed

The package references a small set of APPS synonyms. FND_APPLICATION is used to resolve application identifiers, and FND_NEW_MESSAGES may be accessed for message lookup in error or translation handling paths. DUAL is used for expression evaluation within PL/SQL. PLITBLM supports the index-by or nested table structures used by TO_TABLE and GET_INDEX_AT. UTL_RAW provides the raw byte manipulation primitives on which the hexadecimal and Shift-JIS conversion routines depend.

Usage Notes

HR_JP_STANDARD_PKG is typically invoked from Japanese localizations of Oracle HRMS forms, concurrent programs, and payroll fast formulas that must render or compare Japanese text consistently. The ETRM metadata records that the package is referenced by twelve other packages, indicating broad indirect usage through the Japanese localization stack. Custom code extending Japanese HR or payroll functionality may call the documented routines directly, but because the package is classified as OTHER rather than as a formal public API, Oracle does not guarantee interface stability across releases. The character-set and session-language constants are evaluated once at package instantiation, so behavior depends on the session's NLS_LANGUAGE setting at first load.