Object-Specific Guidelines for Loading Job Offers

Consider these guidelines for each object when loading job offers using HCM Data Loader.

Job Offer

  • You can create and update a job offer only when the job application is in the Draft state.
  • The value of the ProposedStartDate attribute must be the same as or later than the person start date and effective start date of the offer assignment during a job offer create or update.

Action Code Attribute

These values are predefined for the Action Code attribute:
Action Code Action Name
ADD_PEN_WKR Add Pending Worker
ORA_ADD_PWK_WORK_RELATION Add Pending Work Relationship
GLB_TRANSFER Global Transfer
GLB_TEMP_ASG Global Temporary Assignment
HIRE_ADD_WORK_RELATION Add Employee Work Relationship
ADD_CWK_WORK_RELATION Add Contingent Work Relationship
ADD_ASSIGN Add Assignment
TEMP_ASG Temporary Assignment
ASG_CHANGE Change Assignment
PROMOTION Promotion
TRANSFER Transfer
JOB_CHANGE Job Change
LOCATION_CHANGE Location Change
POSITION_CHANGE Position Change
HIRE_ADD_WORK_RELATION Add Employee Work Relationship
ADD_CWK_WORK_RELATION Add Contingent Work Relationship

In addition to these, custom actions can also be created.

Job Offer Team

Job Offer Attachment

Attachments can be of these categories:

  • MISC – Miscellaneous
  • IRC_INTERNAL – Internal attachments with security applied. Document of Record (DoR) isn’t available for this category. It’s visible only in Oracle Recruiting if you have the Recruiter role.
  • IRC_JOB_OFFER_CANDIDATE – Visible to both the candidate (DoR) and the recruiter.

Worker

You can create and update a job offer assignment using the Worker object.

  • While it is required to include the Work Relationship, Work Terms, and Assignment child objects as part of the Worker.dat file, it’s optional to include Work Measures (FTE) and Contract objects, as it depends on the business requirement.
  • The following SET instruction should be placed at the top of the Worker.dat file used to load any job offer assignments:

    SET OFFER_ASSIGNMENTS_FILE Y

    Note: This SET instruction will validate for offer-related information in the Worker.dat file. If you load record types that don’t pertain to job offer assignments, your upload will fail.
  • If a source key is used in the Worker.dat file to reference the job offer on the Assignment object, then it must have the same value as the source key for the job offer in the JobOffer.dat file.

Work Relationship

You can create and update work relationship details using this object.

  • The PrimaryFlag attribute should be set to N.

Work Terms

Using this object, you can create and update the terms and conditions associated with one or more assignments in a work relationship.

  • You must load the WorkTerms object for every create and update operation on the Assignment object.

Assignment

Using this object, you can create and update assignment details such as a worker's job, position, grade, department and location.

  • You can’t update the ProjectedStartDate attribute using the Assignment object. Instead, update it using the JobOffer.dat file.

Assignment Work Measures (FTE)

You can optionally create and update the Assignment Work Measures object.
  • The Full Time Equivalent (FTE) record is automatically created by including this SET instruction at the top of the Worker.dat file:

    SET CALCULATE_FTE Y

    Note: You must not include an AssignmentWorkMeasure record for the candidate when using this SET instruction.

Contract

You can create and update the contract details associated with an assignment or terms of employment.

  • The Contract object must be provided only if the legal employer is configured to have a contract.

Payroll

These two objects, Assigned Payroll and Payroll Assignment Details, are relevant while loading job offers.

Assigned Payroll

Using this object, you can create, update, and delete the payroll frequency details for an assignment.

  • You need to load this object if the salary is based on a payroll process. Otherwise, it’s optional.
  • You can’t provide date-effective changes when loading assigned payroll data for job offers.

Payroll Assignment Details

Using this object, you can create or update payroll assignment details for an employee, such as time card required status and overtime period. However, you can’t delete these details.

It’s optional to load this object.

Salary

You can create, update, and delete proposed salary details for worker assignments.

  • You must load the Salary object as part of the Job Offer load.
  • Salary with rates isn’t supported.
  • You can’t load date-effective changes for a job offer salary.

Element Entry

An element entry holds the actual payroll element and benefits granted to a worker. You can create, update, and delete element entries.

  • Element entries represent the Individual Compensation Plans (ICPs) assigned in the offer. It maps to the Other Comp section in the offer. The number of element entries should be the same as the number of ICPs awarded to the candidate.
  • It is optional to load the Element Entry object as part of the Job Offer load.
  • The OtherCompElementCount attribute value in the JobOfferLetter.dat file must match the number of element entries in the offer.

Job Offer Letter

You can create and update offer letters using the Job Offer Letter object.

  • You must load the Job Offer Letter object as part of the Job Offer load.
  • You must specify an active offer letter template for submitting the offer and generating the offer letter.
    • The offer letter template must be defined for the same candidate type as the candidate mentioned in the job offer.
    • Offer letter templates are defined in the Recruiting Content Library.
  • You must include a reference to the job offer for which the letter is intended.
  • If the SubmitOffer attribute is set to Y, the offer gets submitted and the approval workflow is triggered. If it’s set to N, the offer is created, but not submitted.