Search Results chk_ddf




Overview

APPS.PER_JP_PEM_RULES is a Japan-specific localization package body in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that supports validation logic for the Previous Employment Information (PEM) region of Oracle HRMS. The name derives from "PER" (the Human Resources product schema) and "JP" (Japan), with "PEM" denoting the Previous Employers module. The package encapsulates country-specific data-quality rules required under Japanese payroll and social insurance reporting, most notably the requirement that certain employer-related name and address fields be entered in single-byte (hankaku) katakana characters.

The package header comment identifies the source file as pejppemr.pkb, version 120.0, indicating a long-standing, essentially static localization object delivered with the Japanese HRMS legislation. Its role is narrow and defensive: rather than performing payroll or tax computation, it enforces the input conventions that downstream Japanese statutory processes assume.

Key Procedures and Functions

The ETRM metadata documents a single procedure: CHK_DDF. This is the validation entry point for the Previous Employer Information block. Its purpose is to verify that user-supplied employer details conform to Japanese formatting standards before the record is committed.

Tables Accessed

No base tables are documented as read or written by this package. Although the error registration references the column PER_PREVIOUS_EMPLOYERS.PEM_INFORMATION1 and .PEM_INFORMATION2, these are supplied as descriptive context to HR_MULTI_MESSAGE.ADD so that the Forms client can attribute the message to the correct field; the package itself does not query or manipulate PER_PREVIOUS_EMPLOYERS directly.

Usage Notes

CHK_DDF is invoked from the Japanese HRMS forms that capture previous-employer data, typically as a field-level or block-level validation trigger on the Previous Employment Information block. It is also referenced by two other packages within the ETRM repository, which call it from their own validation flows. Because it relies on FND_MESSAGE and HR_MULTI_MESSAGE, it is designed to run inside an active Forms or concurrent-processing session where the FND message stack is available. Customizations should call the procedure rather than duplicate the hankaku check, ensuring consistent error messaging after Japanese legislation upgrades.