EDIFACT message guide · Healthcare and social
JOBAPP Job application proposal
The UN/EDIFACT message an employment agency uses to propose one or more job applicants to an employer.
- Sent by
- Employment agency
- Received by
- Employer
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT JOBAPP message?
JOBAPP is the UN/EDIFACT job application proposal. The directory defines it as a message specifying detailed information on proposals for one or more job applicants, sent from an employment agency to an employer. The information relates to the applicants' profession, occupation, age, education, experience and other characteristics.
The employer reviews the proposals and reports interviews, hires and rejections back with JAPRES. Because the message contains personal data, its use is governed by data protection and employment laws. Proposals typically reference the vacancy numbers the agency assigned.
How to read this diagram: the top row shows who sends JOBAPP, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around JOBAPP and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.
When it is used
- Proposing candidates for a vacancy
- Sending applicant profiles to employers
- Proposing candidates for several vacancies
Where it fits in the message flow
Structure
Mandatory segments in JOBAPP (directory D.21A)
In UN/EDIFACT directory D.21A, the JOBAPP message has 43 segment positions arranged in 15 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.
- UNH
- BGM
- DTM
- SG1 (PNA)
- UNS
- SG5 (RFF)
- UNT
Practical example
JOBAPP in practice
The employment service matches job seekers to the warehouse vacancies and sends the employer a JOBAPP proposing eight candidates, with their relevant experience, qualifications and availability. The employer invites five to interview and reports the outcomes with JAPRES.
Implementation
Implementation considerations for JOBAPP
- Share only the personal data needed and permitted by law.
- Reference the vacancy the candidates are proposed for.
- Secure the channel used to send personal data.
- Track proposals through to the employer's decisions.
How ECOM helps
Automate JOBAPP with ECOM
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
Solution
B2B Integration
Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.
Industry
Trucking and Transportation
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related healthcare and social messages
Need help with JOBAPP?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.