Search Results fica_status

Overview

PQP_HROSS_INTEGRATION is an Oracle EBS APPS schema PL/SQL package that forms part of the Payroll and HR Operational Support System (HROSS) integration layer within Oracle Human Resources and Oracle Payroll. Its principal business function is to bridge Oracle HRMS person and assignment data with external or downstream systems — in particular student employment records and Oracle Self-Service person data — while also managing the staging structures required to feed Oracle's data pump utilities. In ETRM the object is classified with API type OTHER and carries a VALID status, confirming it is a supported, compiled database object in the APPS schema for both 12.1.1 and 12.2.2.

The package depends on APPS.HR_API and the SYS.STANDARD package, indicating that its person-creation and update routines ultimately delegate to the supported HRMS business APIs rather than writing directly to base HR tables. It is itself referenced by other HROSS-related objects, confirming that it sits within a small internal call hierarchy rather than being a stand-alone utility.

Key Procedures and Functions

The documented package exposes six procedures and functions:

• GET_PERSON_TYPE — Determines the person type classification applicable to a given individual, providing the type value required by subsequent person-creation and update calls.
• CREATE_STUDENT_EMPLOYEE — Creates a student employee record, orchestrating the HRMS person and assignment setup needed for student workers.
• CREATE_BATCHHDR_FOR_DATAPUMP — Inserts a batch header record into the HR pump staging tables so that a data pump batch can be assembled and processed.
• CREATE_OSS_PERSON — Creates a person record originating from an Oracle Self-Service source, applying the appropriate person type and related attributes.
• UPD_OSS_PERSON_ASG — Updates an existing self-service person's assignment details, keeping the HRMS assignment in step with changes made at the self-service layer.
• FICA_STATUS — Returns or derives the FICA (Social Security) status applicable to a person, supporting U.S. payroll tax determination.

Parameter signatures are not reproduced here; callers should obtain the exact interface from the package specification in the target instance before integrating.

Tables Accessed

The package reads and writes a documented set of APPS synonym tables. Person and party data flow through HZ_PARTIES and the HR API modules (HR_API_MODULES). Organizational and positional context is drawn from HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_ALL_POSITIONS_F, HR_ALL_POSITIONS_F_TL, HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL. Payroll grouping uses PAY_PEOPLE_GROUPS. Key flexfield validation and soft coding rely on FND_FLEX_VALUE_SETS, FND_DESCR_FLEX_CONTEXTS and HR_SOFT_CODING_KEYFLEX. The data pump staging structures are HR_PUMP_BATCH_HEADERS, HR_PUMP_BATCH_HEADERS_S and HR_PUMP_BATCH_LINES, consistent with the CREATE_BATCHHDR_FOR_DATAPUMP routine.

Usage Notes

PQP_HROSS_INTEGRATION is typically invoked from HROSS integration logic, concurrent programs and internal callers rather than directly by end users. Because person and assignment changes are routed through HR_API, the package respects HRMS business rules, date-tracked records and validation. It is referenced by one other package, so customizations should avoid modifying it and instead extend or wrap it. Instances upgrading between 12.1.1 and 12.2.2 should re-verify the package specification, as the OSS person-management routines are sensitive to Online Self-Service and person-model changes introduced in later releases.