Search Results hr_contingent_worker_api




Overview
Explore in AI Chat

Overview

APPS.HR_CONTINGENT_WORKER_API is a public PL/SQL API package within the Oracle E-Business Suite Human Resources (HR) module, classified as an API by Oracle's ETRM repository. Its purpose is to provide a controlled, business-rule-validated interface for creating, converting, managing, and terminating contingent workers — a worker category that includes contractors, temporary staff, and other non-employee personnel engaged through a period of placement. The package abstracts the complexity of the underlying HR schema, ensuring that contingent worker lifecycle operations respect person type, assignment, payroll, and period-of-placement integrity. The package is owned by the APPS schema and is marked VALID across Oracle EBS 12.1.1 and 12.2.2 environments. It depends directly on APPS.HR_API and SYS.STANDARD, and it is referenced by nineteen other packages, including country-specific localization packages such as HR_AE_CONTINGENT_WORKER_API, HR_DK_CONTINGENT_WORKER_API, HR_IN_CONTINGENT_WORKER_API, and HR_MX_CONTINGENT_WORKER_API. This localization wrapper pattern confirms that HR_CONTINGENT_WORKER_API serves as the centralized, jurisdiction-neutral implementation of contingent worker operations.

Key Procedures and Functions

ETRM documentation identifies nine documented program units within this package.

  • CREATE_CWK — Creates a new contingent worker record, establishing the person, assignment, and placement foundation.
  • CONVERT_TO_CWK — Converts an existing person or worker record into a contingent worker classification.
  • APPLY_FOR_JOB — Applies a contingent worker to a job or requisition context as part of the engagement process.
  • ACTUAL_TERMINATION_PLACEMENT — Executes the actual termination of a period of placement, applying the termination business rules.
  • FINAL_PROCESS_PLACEMENT — Performs final processing on a placement, completing the placement lifecycle.
  • TERMINATE_PLACEMENT — Terminates an active placement, ending the contingent worker's engagement.
  • REVERSE_TERMINATE_PLACEMENT — Reverses a prior placement termination, restoring the placement if the termination should not have occurred.
  • GET_LENGTH_OF_PLACEMENT — A function that returns the calculated length or duration of a period of placement.

Parameter signatures are intentionally not documented in the ETRM excerpt; callers should always reference the packaged API specification via the data dictionary rather than assuming argument lists.

Tables Accessed

The package reads and writes a broad set of PER and PAY tables through APPS synonyms. It maintains core person and assignment data through PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PERSON_TYPES, and PER_PERSON_TYPE_USAGES_F, since contingent worker status is driven by person type. Period-of-placement and status lifecycle data are managed via PER_PERIODS_OF_PLACEMENT, PER_ASSIGNMENT_STATUS_TYPES, and PER_BOOKINGS. Workforce scheduling and performance context are handled through PER_EVENTS and PER_PERFORMANCE_REVIEWS. Payroll-related processing touches PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_PERSONAL_PAYMENT_METHODS_F, PAY_COST_ALLOCATIONS_F, and PAY_GRADE_RULES_F. Budget and assignment value tracking is supported by PER_ASSIGNMENT_BUDGET_VALUES_F. Collectively, these tables reflect the full contingent worker footprint: person, assignment, placement, payroll, cost, and budget.

Usage Notes

HR_CONTINGENT_WORKER_API is typically invoked indirectly. Oracle-provided country localization packages (for example, HR_SE_CONTINGENT_WORKER_API or HR_PL_CONTINGENT_WORKER_API) and shared processes such as HR_PROCESS_PERSON_SS, HR_CWK_TERMINATION_SWI, IRC_PARTY_API, PQP_PERASGADD_RIW, and PER_QH_MAINTAIN_UPDATE call into it during forms-based entry, iRecruitment processing, and concurrent program execution. Custom code should never perform direct DML on the underlying PER/PAY tables; instead, custom integrations should call this API, which encapsulates validation and supports localization. Because termination and final processing affect payroll and placement history, TERMINATE_PLACEMENT, ACTUAL_TERMINATION_PLACEMENT, and REVERSE_TERMINATE_PLACEMENT must be used with the same ordering and commit discipline as the standard HR business flows. In both 12.1.1 and 12.2.2, the API is validated and stable, and any upgrade or patching effort should preserve its specification to avoid breaks in the nineteen dependent packages.