Search Results hr_mx_contingent_worker_api
Overview
APPS.HR_MX_CONTINGENT_WORKER_API is a PL/SQL package that belongs to the Oracle E-Business Suite Human Resources (HR) product family, specifically addressing Mexican (MX) statutory requirements for contingent workers. In the EBS 12.1.1 and 12.2.2 releases, Mexican labor and payroll legislation imposes distinct classification, registration, and reporting obligations on employers who engage contingent, temporary, or outsourced personnel (often referred to under the concept of "trabajadores eventuales" or third-party supplied labor subject to REPSE and related regulations). This package encapsulates the application logic required to create and register a Mexican contingent worker record within the HR foundation tables, allowing the records to flow correctly into downstream payroll, costing, and statutory reporting processes.
Based on the documented ETRM metadata, the package is classified as an API and carries an owner of APPS, with a status of VALID. Its dependency footprint is minimal — it references only SYS.STANDARD in the extracted metadata, and it is not referenced by any other package in the ETRM index, which indicates it is a leaf-level API intended to be invoked directly by users, forms, or concurrent processes rather than by other PL/SQL packages.
Key Procedures and Functions
The ETRM documentation records a single documented program unit within this package:
- CREATE_MX_CWK — The sole documented procedure. Its purpose is to create a Mexican contingent worker record. Invoking this routine performs the necessary insertions and validations against the HR tables so that the contingent worker is recognized by EBS as a valid person/assignment of the contingent worker category. Because the ETRM metadata lists only this procedure and does not publish its signature, no parameter list should be assumed; integrators should inspect the package specification in the target environment or obtain the corresponding Oracle technical reference for the exact arguments before calling it from custom code.
Tables Accessed
The ETRM metadata excerpt provided does not enumerate the underlying tables accessed through APPS synonyms; the "Tables referenced" list is empty in the documented metadata. In practice, a contingent worker creation API of this type would write to the core HR person and assignment structures (such as the PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F tables) along with any Mexico-specific extension tables used to hold contingent worker attributes. However, because no table names are confirmed in the supplied metadata, this should be treated as a general architectural expectation rather than a documented fact. Readers requiring the authoritative table list should query the package body or the data dictionary dependencies in their own environment.
Usage Notes
HR_MX_CONTINGENT_WORKER_API is intended to be called programmatically rather than through the standard HR forms, because it is registered as an API object. Typical invocation patterns include custom PL/SQL routines, integration scripts, or interface/concurrent programs that load contingent worker data from external systems such as staffing agencies or third-party payroll providers. Because the package is owned by APPS and depends only on SYS.STANDARD, it can be granted to and executed from custom schemas following standard EBS API wrapping conventions: callers should not commit inside the API, should use the documented FND_API style error handling if present, and should resolve APPS synonyms for any referenced objects. As no other packages reference it, dependency risk from within the EBS codebase is low, making it a relatively safe target for extension. When migrating between 12.1.1 and 12.2.2, the API's validity should be confirmed after each patch cycle using the standard EBS dependency and compilation checks.
-
PACKAGE: APPS.HR_MX_CONTINGENT_WORKER_API
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_MX_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE BODY: APPS.HR_MX_CONTINGENT_WORKER_API
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:HR_MX_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE BODY: APPS.HR_MX_CONTINGENT_WORKER_API
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:HR_MX_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE: APPS.HR_MX_CONTINGENT_WORKER_API
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_MX_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE: APPS.HR_MX_UTILITY
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_MX_UTILITY, status:VALID,
-
PACKAGE: APPS.HR_CONTINGENT_WORKER_API
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE: APPS.HR_CONTINGENT_WORKER_API
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_CONTINGENT_WORKER_API, status:VALID,
-
PACKAGE: APPS.HR_MX_UTILITY
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_MX_UTILITY, status:VALID,
-
PACKAGE BODY: APPS.HR_MX_CONTINGENT_WORKER_API
12.2.2
-
PACKAGE BODY: APPS.HR_MX_CONTINGENT_WORKER_API
12.1.1
-
PACKAGE: APPS.HR_MX_CONTINGENT_WORKER_API
12.2.2
-
PACKAGE: APPS.HR_MX_CONTINGENT_WORKER_API
12.1.1
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_MX_CONTINGENT_WORKER_API
12.2.2
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_MX_CONTINGENT_WORKER_API
12.1.1
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_UTILITY
12.1.1
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_UTILITY
12.2.2
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_CONTINGENT_WORKER_API
12.2.2
-
APPS.HR_MX_CONTINGENT_WORKER_API dependencies on HR_CONTINGENT_WORKER_API
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: APPS.HR_UTILITY
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_UTILITY, status:VALID,
-
PACKAGE: APPS.HR_UTILITY
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_UTILITY, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,