Search Results insupd_assig_extra_info




Overview
Explore in AI Chat

Overview

APPS.PQP_HROSS_INTEGRATION_SWI is a stored PL/SQL package body within the Oracle E-Business Suite that supports the integration between Oracle Human Resources and the Oracle iRecruitment / HR Onboarding (OSS) footprint. It is classified under the ETRM metadata as an "OTHER" API package, indicating that it is not one of the principal public HRMS APIs but rather a supporting integration layer invoked by Oracle-delivered flows and, in some cases, extensible by customers.

The package name, PQP_HROSS_Integration_SWI, reflects its dual role: "PQP" identifies it as part of the Oracle Payroll/HR product family, while "HROSS" indicates the HR Onboarding / OSS integration scope. The "SWI" suffix conventionally denotes a Server-side Web Interface or service wrapper, meaning the package is designed to be called from mid-tier components such as OAF pages, concurrent programs, or BPEL/Workflow processes rather than directly from end-user forms. The header comment records a version identifier reflective of the 11i/12.x codebase lineage, and the package remains present and valid in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

ETRM documents five program units in this package body:

  • CREATE_OSS_PERSON — The procedure most commonly searched for ("create_oss_person"). It creates a person record in the OSS/onboarding context, accepting parameters that include business group, an optional duplicate person identifier, an effective date, and person-level attributes such as party ID, last name, middle name, and first name. It is the entry point for materializing a new hire or applicant person from the onboarding integration layer into the HR person model.
  • UPD_OSS_PERSON_ASG — Updates the assignment associated with an OSS person, aligning assignment attributes maintained by the onboarding flow with the underlying PER_ASSIGNMENTS records.
  • INSUPD_ASSIG_EXTRA_INFO — Performs insert-or-update (upsert) logic against assignment-level descriptive flexfield extra information, ensuring onboarding-supplied attributes are persisted on the assignment.
  • INSUPD_PERSON_EXTRA_INFO — Performs the equivalent upsert against person-level extra information, writing onboarding data to PER_PEOPLE_EXTRA_INFO.
  • INSUPD_SIT_INFO — Upserts situational or supplementary information associated with the onboarding record.

In addition, the excerpt shows a private helper, Get_PK_For_Validation, which verifies whether a visa history record already exists for a given port of entry and country entry form number before allowing a create or update. This helper queries IGS_PE_VISIT_HISTRY and returns a Boolean result, guarding against duplicate visa history rows.

Tables Accessed

The package body references several tables through APPS synonyms:

  • PER_PEOPLE_EXTRA_INFO — Stores person-level descriptive flexfield and extra attribute information written by INSUPD_PERSON_EXTRA_INFO.
  • PER_ASSIGNMENT_EXTRA_INFO — Stores assignment-level extra information maintained by INSUPD_ASSIG_EXTRA_INFO.
  • PER_ANALYSIS_CRITERIA and PER_PERSON_ANALYSES — Support the person analysis and criteria model used to classify or categorize people during onboarding and subsequent HR processing.
  • IGS_PE_VISIT_HISTRY — Referenced by Get_PK_For_Validation to confirm the existence of visa history records keyed by port of entry and country entry form number.

The package also works implicitly with the core HR person and assignment tables (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F) through the CREATE_OSS_PERSON and UPD_OSS_PERSON_ASG routines, which persist the person and assignment records themselves.

Usage Notes

PQP_HROSS_INTEGRATION_SWI is not referenced by any other documented package (Referenced by: 0), which indicates it is a top-level integration wrapper called from outside the PL/SQL API layer. Typical invocations occur from Oracle iRecruitment, Oracle Onboarding, or the HR "New Hire" OAF-based flows, as well as from customer-written concurrent programs or workflow activities that need to push externally sourced person data into EBS HRMS.

Because CREATE_OSS_PERSON is the public entry point most often sought by developers searching "create_oss_person", it is the recommended procedure for programmatic person creation in the OSS integration context. Callers should supply a valid business group, effective date, and the required name attributes, and should be aware that duplicate detection and visa-history validation are performed inside the package. As with all HRMS integration APIs, calls should be wrapped in a savepoint and committed explicitly, and the package should be invoked with the appropriate HR security context so that the resulting person and assignment rows are visible to downstream HR, payroll, and reporting processes in both EBS 12.1.1 and 12.2.2.