Examples of Loading Job Offers
Here are sample files that show how to create a job offer using HCM Data Loader.
Example for an External Candidate
You can use the sample JobOffer.dat file provided here to create or update a job offer for external candidates.
Job Offer
This example creates an offer for the candidate CAN614005. The source key VISION | CAN614005-R23522 uniquely identifies the job offer. This source key value is used to identify the team members and the attachment for the job offer.
METADATA|JobOffer|SourceSystemOwner|SourceSystemId|CandidateNumber|RequisitionNumber|Comments|OfferComments|Additionaltext1|Additionaltext2|HiringManagerPersonNumber|HiringManagerAssignmentNumber|RecruiterPersonNumber|RecruiterAssignmentNumber|ProposedStartDate|LegalEmployer|WorkerType|ActionCode|ObjectStatus|FLEX:IRC_OFFERS_DFF|OfferText(IRC_OFFERS_DFF=FxF_Offer_Context)
MERGE|JobOffer|VISION|CAN614005-R23522|CAN614005|R23522|Comments for the job offer|CAN614005-R23522_OfferComments.txt|CAN614005-R23522_Additionaltext1.txt|CAN614005-R23522_Additionaltext2.txt|431509|E431509|451255|E451255|2022/10/03|VISION US|Employee|ADD_PEN_WKR||VISION_Offer_Context|Custom descriptive flexfield example
METADATA|JobOfferTeam|SourceSystemOwner|SourceSystemId|OfferId(SourceSystemId)|CollaboratorType|MemberType|PersonNumber|AssignmentNumber
MERGE|JobOfferTeam|VISION|CAN614005-R23522-E411302|CAN614005-R23522||ORA_COLLABORATOR|411302|E411302
MERGE|JobOfferTeam|VISION|CAN614005-R23522-E396684|CAN614005-R23522|ORA_HIRING_TEAM_COLLABORATOR|ORA_COLLABORATOR|396684|E396684
METADATA|JobOfferAttachment|OfferId(SourceSystemOwner)|Title|CandidateNumber|RequisitionNumber|OfferId(SourceSystemId)|File|DataTypeCode|Category|URLorFileName
MERGE|JobOfferAttachment|VISION|CAN614005-Resume-File|CAN614005|R23522|CAN614005-R23522|CAN614005_Resume.docx|FILE|IRC_INTERNAL|CAN614005_Resume.docx
To load data into a Character Large Object (CLOB) object, name the file that contains the data to be loaded and place that file in a subfolder of the same compressed zip file used to load the JobOffer.dat file. The subfolder must be named ClobFiles.
The values for these attributes need to be provided in separate files within the ClobFiles subfolder:
- OfferComments
- Additionaltext1
- Additionaltext2
Offer Assignment
Use the Worker.dat file to create the offer assignment.
You must always include the SET OFFER_ASSIGNMENTS_F Y
instruction at
the top of the file. Optionally, include the SET CALCULATE_FTE Y
instruction if you want the full-time equivalent to be created.
This example creates the work relationship, employment (work) terms and assignment for the candidate referenced in the Job Offer example provided earlier.
The job offer is referenced on the Assignment record using the OfferId(SourceSystemId) attribute. The source system ID value CAN614005-R23522 is the same as supplied to the SourceSystemId attribute on the JobOffer record in the previous example.
SET OFFER_ASSIGNMENTS_FILE Y
SET CALCULATE_FTE Y
METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|PersonId|DateStart|WorkerType|LegalEmployerName|PrimaryFlag|ActionCode
MERGE|WorkRelationship|VISION|WRCAN614005|300100574088451|2022/10/03|O|VISION US|N|EMPL_OFFER_CREATE
METADATA|WorkTerms|SourceSystemOwner|SourceSystemId|PeriodOfServiceId(SourceSystemId)|EffectiveStartDate|EffectiveSequence|EffectiveLatestChange|SystemPersonType|ActionCode|AssignmentType|BusinessUnitShortCode|GradeLadderPgmName|PersonTypeCode|AssignmentNumber
MERGE|WorkTerms|VISION|WTCAN614005|WRCAN614005|2022/10/03|1|Y|ORA_CANDIDATE|EMPL_OFFER_CREATE|OT|Vision Business Unit|CMP_SBwithGLST|Recruiting Candidate|
METADATA|Assignment|SourceSystemOwner|SourceSystemId|WorkTermsAssignmentId(SourceSystemId)|EffectiveStartDate|EffectiveSequence|EffectiveLatestChange|OfferId(SourceSystemId)|ActionCode|AssignmentType|BusinessUnitShortCode|GradeLadderPgmName|PersonTypeCode|AssignmentNumber|NormalHours|Frequency|PositionCode|JobCode|GradeCode|LocationCode|DepartmentName|ProjectedStartDate|ProposedUserPersonType|SystemPersonType|TaxReportingUnit
MERGE|Assignment|VISION|ECAN614005|WTCAN614005|2022/10/03|1|Y|CAN614005-R23522|EMPL_OFFER_CREATE|O|Vision Business Unit|CMP_SBwithGLST|Recruiting Candidate||30|W|Analyst Position|Analyst|IC3|VUSSF_01|US HCM|2022/10/03|Employee|ORA_CANDIDATE|VIS USA
Payroll Assignment Details
Use the PayrollAssignmentDetails.dat file to create and maintain the payroll assignment details, such as time card required status and overtime period.
The offer assignment for which the payroll assignment details are being created is referenced by its source key using the AssignmentId(SourceSystemId) attribute and AssignmentId(SourceSystemOwner) attributes.
METADATA|PayrollAssignmentDetails|AssignmentId(SourceSystemOwner)|AssignmentId(SourceSystemId)|EffectiveStartDate|LegislativeDataGroupName|TimecardRequiredFlag|OvertimePeriodCode
MERGE|PayrollAssignmentDetails|VISION|ECAN614005|2022/10/03|United States LDG|Y|VIS_WK
Assigned Payroll
Use the AssignedPayroll.dat file to create and maintain payroll assignment details, such as the payroll name, frequency details, and related start and end dates.
The offer assignment for which the assigned payroll details are being created is referenced by its source key using the attributes AssignmentId(SourceSystemId) and SourceSystemOwner. The source key value ECAN614005 | VISION that you defined when creating the offer assignment is used in this example.
METADATA|AssignedPayroll|SourceSystemOwner|SourceSystemId|AssignmentId(SourceSystemId)|EffectiveStartDate|PayrollDefinitionCode|LegislativeDataGroupName|StartDate|OvertimePeriodCode|TimecardRequiredFlag
MERGE|AssignedPayroll|VISION|ECAN614005_AP|ECAN614005|2022/10/03|VIS_MONTHLY_PAYROLL|United States LDG|2022/10/03|VIS_WK|Y
Salary
Use the Salary.dat file to create or update salary proposals.
The offer assignment for which salary details are being created is referenced by its source key using the attributes AssignmentId(SourceSystemId) and SourceSystemOwner. The source key value ECAN614005 | VISION that you defined when creating the offer assignment is used in this example.
This example uses salary components.
METADATA|Salary|SourceSystemOwner|SourceSystemId|SalaryBasisName|AssignmentId(SourceSystemId)|DateFrom|SalaryAmount|MultipleComponents|NextSalReviewDate|SalaryApproved|ActionCode
MERGE|Salary|VISION|ECAN614005_1|STD_CMP_AUTO_BUZoneGR_001|ECAN614005|2022/10/03|0|Y|2022/11/01|Y|EMPL_OFFER_CREATE
METADATA|SalarySimpleComponent|SourceSystemOwner|SourceSystemId|SalaryId(SourceSystemId)|AssignmentId(SourceSystemId)|SalaryDateFrom|ComponentCode|Amount|Percentage
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_BAS|ECAN614005_1|ECAN614005|2022/10/03|ORA_BASIC|60000|
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_CTY|ECAN614005_1|ECAN614005|2022/10/03|ORA_CITY_ALLOWANCE||10
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_TRN|ECAN614005_1|ECAN614005|2022/10/03|ORA_TRANSPORT_ALLOWANCE|2500|
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_TVL|ECAN614005_1|ECAN614005|2022/10/03|ORA_TRAVEL_ALLOWANCE||8
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_SPC|ECAN614005_1|ECAN614005|2022/10/03|ORA_SPECIAL_ALLOWANCE||100
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_HOU|ECAN614005_1|ECAN614005|2022/10/03|ORA_HOUSING_ALLOWANCE|10000|
MERGE|SalarySimpleComponent|VISION|ECAN614005_1_SAL|ECAN614005_1|ECAN614005|2022/10/03|ORA_OVERALL_SALARY||
Element Entry
Use the ElementEntry.dat file to create or maintain compensation elements for the candidate.
The offer assignment for the element entries is referenced by its source key using the HrAssignmentId(SourceSystemId) and SourceSystemOwner attributes. The source key value ECAN614005 | VISION that you defined when creating the offer assignment is used in this example.
This example creates three element entries:
Element Entry | Amount |
---|---|
SpotBonus | 1000.325 |
HiringBonus | 5467.25 |
INF_ISO | 100 shares |
METADATA|ElementEntry|SourceSystemOwner|SourceSystemId|HrAssignmentId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|ElementName|LegislativeDataGroupName|EntryType|MultipleEntryCount|CreatorType
MERGE|ElementEntry|VISION|ECAN614005_SB|ECAN614005|2022/10/03|2022/10/30|SpotBonus|United States LDG|E||VC
MERGE|ElementEntry|VISION|ECAN614005_HB|ECAN614005|2022/10/03||HiringBonus|United States LDG|E|1|VC
MERGE|ElementEntry|VISION|ECAN614005_STK|ECAN614005|2022/10/03||INF_ISO|United States LDG|E|1|VC
METADATA|ElementEntryValue|SourceSystemOwner|SourceSystemId|ElementEntryId(SourceSystemId)|EffectiveStartDate|EffectiveEndDate|ElementName|LegislativeDataGroupName|EntryType|MultipleEntryCount|InputValueName|ScreenEntryValue
MERGE|ElementEntryValue|VISION|ECAN614005_SB_AMT|ECAN614005_SB|2022/10/03|2022/10/30|SpotBonus|United States LDG|E||Amount|1000.325
MERGE|ElementEntryValue|VISION|ECAN614005_HB_AMT|ECAN614005_HB|2022/10/03||HiringBonus|United States LDG|E|1|Amount|5467.25
MERGE|ElementEntryValue|VISION|ECAN614005_STK_GRNT|ECAN614005_STK|2022/10/03||INF_ISO|United States LDG|E|1|Shares Granted|100
Job Offer Letter
Use the JobOfferLetter.dat file to create or update a job offer letter.
Specify a value of Y
in the HasPayroll attribute if you want to
validate that the candidate has a payroll record. Specify a number in the
OtherCompElementCount attribute to validate the total number of compensation
elements expected in the offer.
The SubmitOffer attribute is used to submit the job offer for approval. When the job offer is submitted, it moves to the Approved or Pending Approval status depending on whether Bypass Approval is enabled.
METADATA|JobOfferLetter|CandidateNumber|RequisitionNumber|OfferLetterContentItemCode|HasPayroll|OtherCompElementCount|SubmitOffer|ExpirationDate
MERGE|JobOfferLetter|CAN614005|R23522|OR_28SEP2022_2009PM|N|3|Y|2022/10/12 21:00:00
Example for an Internal Candidate
You can use the sample JobOffer.dat file provided here to create or update a job offer for internal candidates.
For the other objects, you can refer to the sample files provided earlier for external candidates, and use data that’s relevant for internal candidates.
Job Offer
This example creates an offer for an internal candidate 283706. The source key VISION | 283706_R712413 uniquely identifies the job offer. This source key value is used to identify the team members and attachment for the job offer.
This example differs from the external candidate job offer in the value for the ActionCode. Here the action is global transfer (GLB_TRANSFER).
METADATA|JobOffer|SourceSystemOwner|SourceSystemId|CandidateNumber|RequisitionNumber|Comments|OfferComments|Additionaltext1|Additionaltext2|HiringManagerPersonNumber|HiringManagerAssignmentNumber|RecruiterPersonNumber|RecruiterAssignmentNumber|ProposedStartDate|LegalEmployer|WorkerType|ActionCode
MERGE|JobOffer|VISION|283706_R712413|283706|R712413|Global Transfer US-UK, GT-HDLINT, OFF-Virgillo Past Date|283706_R712413 OfferComments.txt|283706_R712413 Additionaltext1.txt|283706_R712413 Additionaltext2.txt|131509|E131509|132552|E132552|2022/11/06|VISION US|Employee|GLB_TRANSFER
METADATA|JobOfferTeam|SourceSystemOwner|SourceSystemId|OfferId(SourceSystemId)|CollaboratorType|MemberType|PersonNumber|AssignmentNumber
MERGE|JobOfferTeam|VISION|283706_R712413_E121302|283706_R712413|IRC_INTERVIEW_TEAM|ORA_COLLABORATOR|121302|E121302
MERGE|JobOfferTeam|VISION|283706_R712413_E211337|283706_R712413|IRC_REC_COORDINATOR|ORA_COLLABORATOR|211337|E211337
MERGE|JobOfferTeam|VISION|283706_R712413_E231502|283706_R712413|ORA_HIRING_TEAM_COLLABORATOR|ORA_COLLABORATOR|231502|E231502
MERGE|JobOfferTeam|VISION|283706_R712413_E233001|283706_R712413||ORA_COLLABORATOR|233001|E233001
METADATA|JobOfferAttachment|OfferId(SourceSystemOwner)|OfferId(SourceSystemId)|CandidateNumber|RequisitionNumber|Title|File|DataTypeCode|URLorFileName|Category
MERGE|JobOfferAttachment|VISION|283706_R712413|283706|R712413|Resume-File1|283706 Resume1.docx|FILE|Resume1.docx|IRC_JOB_OFFER_CANDIDATE
MERGE|JobOfferAttachment|VISION|283706_R712413|283706|R712413|Resume-File2|283706 Resume2.docx|FILE|Resume2.docx|IRC_INTERNAL
MERGE|JobOfferAttachment|VISION|283706_R712413|283706|R712413|Resume-Link1||WEB_PAGE|http://www.google.com|MISC