Search Results hr_jpbp_api




Overview
Explore in AI Chat

Overview

HR_JPBP_API is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an API in the ETRM repository. It implements business process APIs specific to the Japan localization of Oracle Human Resources, as reflected in its source header comment stating that it "contains business process APIs for Japan" and its registered display name, "Business Process for Japan." The package is declared with AUTHID CURRENT_USER, meaning that its unqualified database references resolve against the privileges of the invoking session rather than the package owner. The header identifies the underlying source file as pejpapi.pkh, with a version history originating in 2005, consistent with the long-standing Japanese localization delivered within the PER product family.

The central business function of the package is the creation of Japanese-specific person records and their associated "special information" data. Special information in Oracle HRMS stores country-specific or statutory attributes that are not represented in the standard person model, including JP Educational Background details. The package therefore provides a programmatic, validation-aware interface for populating these records rather than requiring direct table maintenance.

Key Procedures and Functions

The documented API surface consists of five procedures. Each follows the standard HRMS API pattern, accepting a p_validate parameter as documented for CREATE_JP_EDUC_SIT, whereby a true value performs validation only and leaves the database unchanged, while a false value commits the changes once all validation checks pass.

  • CREATE_JP_EDUC_SIT — Creates a special information record of type JP Educational Background for an existing person identified by person_id. Documented prerequisites require the person to belong to a JP business group and the JP Educational Background information type to be enabled against that business group. Documented parameters include p_person_id, p_business_group_id, p_effective_date, p_comments, and the effective date range columns p_date_from and p_date_to, which map to PER_PERSON_ANALYSES.DATE_FROM and DATE_TO.
  • CREATE_JP_EMPLOYEE_WITH_SIT — Creates a Japanese employee record together with the associated special information, providing a single-call entry point for employee and localization data.
  • CREATE_JP_EMP_WITH_EDUC_ADD — Creates a Japanese employee with additional educational background details, extending the employee creation path with the educational attributes handled by the special information structure.
  • CREATE_JP_APPLICANT_WITH_SIT — Creates a Japanese applicant record together with the associated special information.
  • CREATE_JP_APPL_WITH_EDUC_ADD — Creates a Japanese applicant with additional educational background details.

The naming pattern confirms a symmetric design: separate creation paths for employees and applicants, each available with either generic special information or education-specific additions.

Tables Accessed

The package accesses four documented tables through APPS synonyms. PER_ALL_PEOPLE_F is the primary person table, read to validate that the referenced person exists and to drive person-related derivations. PER_ANALYSIS_CRITERIA defines the special information types, including JP Educational Background, and is consulted to verify that the relevant information type is enabled. PER_JP_SCHOOL_LOOKUPS holds Japanese school and educational institution reference data used when populating educational background records. FND_ID_FLEX_STRUCTURES is the key flexfield definition table, referenced for the descriptive or key flexfield structures associated with person records in the Japan localization.

Usage Notes

HR_JPBP_API is intended for programmatic invocation rather than direct end-user execution. The ETRM metadata records no other packages referencing it, indicating that within the documented repository it is a leaf-level API. Typical invocation paths include Japan-localized Oracle HRMS forms that need to create employee or applicant records with statutory educational data, concurrent programs or batch loaders that import Japanese personnel data, and custom PL/SQL integrations and conversions that must respect the localization validation rules. Because the records are effective-dated through p_effective_date and the date range parameters, callers should supply an effective date consistent with the business group's date-tracked person records. Implementations should first run with p_validate set to true to confirm prerequisites, particularly business group membership and the enabled special information type, before committing data with a false value.