Search Results create_jp_educ_sit

Overview

HR_JPBP_API is a Japanese localizations API package body owned by APPS. Its header, first shipped in file pejpapi.pkb version 120.0 (2005/05/30), identifies it as part of the Oracle HRMS Japan business process layer. The package encapsulates the server-side validation and creation logic required to register Japanese HR and recruitment records in Oracle E-Business Suite. Specifically, it supports the entry of Japanese educational background data — schools, majors, and the corresponding Kana representations — together with employee and applicant records that reference that education data.

The package is classified in ETRM as an API, meaning it is intended to be called from other server-side code rather than executed directly by end users. It provides a controlled, validated gateway to the underlying PER tables, ensuring that Japanese-specific attributes such as school identifiers, school names, school name Kana, major, and major Kana are consistent with the PER_JP_SCHOOL_LOOKUPS lookup table before any row is written.

Key Procedures and Functions

The ETRM metadata documents five entry points in this package body:

• CREATE_JP_EDUC_SIT — Creates a Japanese education situation record. This is the procedure surfaced in the user's search. It accepts education details and persists the validated row against the person, using the school and major validation performed internally (see the chk_school_id_school_name_comb validation routine visible in the source excerpt).
• CREATE_JP_EMPLOYEE_WITH_SIT — Creates a Japanese employee together with the associated situation (education/assignment) records in a single API call, avoiding the need for callers to sequence multiple inserts manually.
• CREATE_JP_EMP_WITH_EDUC_ADD — Creates a Japanese employee and additionally attaches education address/details, a convenience wrapper over the employee creation and education creation paths.
• CREATE_JP_APPLICANT_WITH_SIT — The applicant-side counterpart to employee creation; creates a Japanese applicant record along with the relevant situation records.
• CREATE_JP_APPL_WITH_EDUC_ADD — Creates a Japanese applicant and attaches the corresponding education address/details.

Internal validation is performed by the private routine chk_school_id_school_name_comb, which resolves school information from PER_JP_SCHOOL_LOOKUPS and raises application error HR_72011_API_INVALID_SCL_ID when an invalid school identifier is supplied. Parameter lists are deliberately not restated here; callers should obtain exact signatures from the package specification.

Tables Accessed

The package operates against the following documented tables (accessed through APPS synonyms):

• PER_JP_SCHOOL_LOOKUPS — The Japanese school lookup used for validation. The source excerpt shows cursors that resolve a record by school_id and by the combination of school_name and major, defaulting missing name and major values from the lookup.
• PER_ANALYSIS_CRITERIA — Stores the flexible analysis criteria (segments) into which Japanese education attributes such as school id, school name, school name Kana, major, and major Kana are mapped. The private validation routine types its parameters directly from per_analysis_criteria.segment2 through segment6.
• PER_ALL_PEOPLE_F — The core person/employee datable entity, read and written when employees or applicants are created.
• FND_ID_FLEX_STRUCTURES — The key flexfield definition table, consulted to resolve the descriptive flexfield or key flexfield structure used for the Japanese education information.

Usage Notes

HR_JPBP_API is a server-side API invoked by Oracle HRMS Japanese localization forms, concurrent processes, and custom extensions that need to create Japanese employee or applicant records with education data. Typical callers are the Japanese applicant and employee entry forms, which delegate the multi-table insert to these procedures. Because the package raises standard HR_UTILITY application errors rather than raw Oracle exceptions, callers should trap and translate HR_72011_API_INVALID_SCL_ID and related messages in their error handling. ETRM records no other packages referencing HR_JPBP_API, so it is intended as a leaf-level creation API. Parameter signatures and the complete attribute list should always be verified against the package specification for the specific 12.1.1 or 12.2.2 installation, as the body is shipped with the standard APPLSYNCH/HRMS patch set.