Search Results hr_dk_contingent_worker_api




Overview
Explore in AI Chat

Overview

The APPS.HR_DK_CONTINGENT_WORKER_API package is a public PL/SQL API within the Oracle E-Business Suite Human Resources (HR) module. It belongs to the country-specific (localization) layer of Oracle HRMS, as indicated by the _DK_ segment in its name, which designates functionality tailored for Denmark. The package provides a programmatic interface for creating and managing contingent worker records—individuals engaged on a non-standard employment basis, such as contractors, temporary staff, or consultants—within the Danish localization framework.

In Oracle EBS 12.1.1 and 12.2.2, contingent workers are managed through the same core HR person and assignment infrastructure used for regular employees, but with distinct business group settings, system person types, and assignment categories. The HR_DK_CONTINGENT_WORKER_API package encapsulates the Danish-specific business rules, validation logic, and data setup required to instantiate these records consistently, shielding callers from the underlying table relationships and localization requirements. It is classified as an API within the ETRM registry and holds a VALID status in the APPS schema.

Key Procedures and Functions

The ETRM documentation records a single documented entry point for this package: CREATE_DK_CWK. Based on the naming convention and the package's stated purpose, this procedure is responsible for creating a Danish contingent worker record. Its responsibilities would typically encompass:

  • Validating the supplied contingent worker attributes against Danish localization requirements.
  • Creating or associating the underlying person record with the appropriate system person type.
  • Establishing the assignment for the contingent worker, including the required assignment status and category.
  • Populating any Danish-specific flexfield or date-tracked attributes mandated by local statutory or business practice.

No parameter list is documented in the ETRM metadata, and therefore none is reproduced here. Consumers should consult the package specification directly in the database (for example, via USER_SOURCE or ALL_SOURCE for HR_DK_CONTINGENT_WORKER_API) to determine the exact signature, parameter names, datatypes, and any IN/OUT modes before invoking the API. The single documented entry point suggests a focused, purpose-built interface rather than a general-purpose CRUD package.

Tables Accessed

The ETRM metadata for this object does not enumerate any tables referenced through APPS synonyms. In practice, an API of this nature would be expected to write to the core HRMS tables that underpin person and assignment data, including PER_PEOPLE_F, PER_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, PER_PERSON_TYPES, and possibly the Danish localization tables that extend the standard HR model. The package may also invoke other HR APIs, such as HR_PERSON_API or HR_ASSIGNMENT_API, rather than performing direct DML against these tables. Because the metadata does not confirm specific table references, all such access should be verified directly against the package body.

Usage Notes

This package is typically invoked from custom PL/SQL code, integration interfaces, or Oracle Application Framework (OAF) pages where Danish contingent workers must be created programmatically—for example, during data conversion, bulk upload, or third-party system integration. The ETRM metadata records zero packages referencing HR_DK_CONTINGENT_WORKER_API, indicating it is not a dependency of other delivered APIs and is intended for direct external callers. Because it is a country-specific API, it should only be used within a Danish legislative context; invoking it in a business group configured for another country may produce inconsistent results. Callers should wrap invocations in appropriate exception handling and commit logic, and should validate inputs against the package specification before execution. Oracle EBS 12.1.1 and 12.2.2 share the same conceptual HRMS data model, so no compatibility divergence is expected between these releases for this API.