JOBAPP — EDIFACT Job Application Proposal Message (D.02B)
The JOBAPP message is the application to a vacant job sent by a job-seeker — directly or via an agency — to an employer or to a public employment service: it carries the candidate identification, work history, qualifications, expectations and reference to the related vacancy. This page summarises the segment structure as published by UN/CEFACT for directory D.02B.
Purpose
The JOBAPP message is the application to a vacant job sent by a job-seeker — directly or via an agency — to an employer or to a public employment service: it carries the candidate identification, work history, qualifications, expectations and reference to the related vacancy.
This page focuses on the structure published by UN/CEFACT for directory D.02B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file jobapp_c.htm hosted on service.unece.org.
Segment structure
The JOBAPP D.02B message has 17 header entries, 41 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.
Header
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | M | ×2 |
0040 | SG1 | Group (×99) | M | ×99 |
0050 | PNA | Party identification | M | 1 |
0060 | ADR | Address | C | 1 |
0070 | LOC | Place/location identification | C | ×5 |
0080 | DTM | Date/time/period | C | ×5 |
0090 | SG2 | Group (×5) | C | ×5 |
0100 | CTA | Contact information | M | 1 |
0110 | COM | Communication contact | C | ×5 |
0120 | SG3 | Group (×5) | C | ×5 |
0130 | RFF | Reference | M | 1 |
0140 | DTM | Date/time/period | C | ×5 |
0150 | SG4 | Group (×5) | C | ×5 |
0160 | GEI | Processing information | M | 1 |
0170 | FTX | Free text | C | 1 |
Detail
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0180 | UNS | Section control | M | 1 |
0190 | SG5 | Group (×999) | M | ×999 |
0200 | RFF | Reference | M | 1 |
0210 | DTM | Date/time/period | C | ×99 |
0220 | SG6 | Group (×1) | C | 1 |
0230 | PNA | Party identification | M | 1 |
0240 | DTM | Date/time/period | C | 1 |
0250 | LOC | Place/location identification | C | ×9 |
0260 | NAT | Nationality | C | ×9 |
0270 | PDI | Person demographic information | C | 1 |
0280 | DOC | Document/message details | C | ×9 |
0290 | SG7 | Group (×5) | C | ×5 |
0300 | GEI | Processing information | M | 1 |
0310 | FTX | Free text | C | 1 |
0320 | SG8 | Group (×99) | M | ×99 |
0330 | RCS | Requirements and conditions | M | 1 |
0340 | FTX | Free text | C | ×99 |
0350 | SG9 | Group (×1) | C | 1 |
0360 | SAL | Remuneration type identification | M | 1 |
0370 | FTX | Free text | C | 1 |
0380 | SG10 | Group (×10) | C | ×10 |
0390 | ATT | Attribute | M | 1 |
0400 | FTX | Free text | C | 1 |
0410 | SG11 | Group (×2) | C | ×2 |
0420 | GEI | Processing information | M | 1 |
0430 | FTX | Free text | C | 1 |
0440 | SG12 | Group (×5) | C | ×5 |
0450 | MOA | Monetary amount | M | 1 |
0460 | RNG | Range details | C | 1 |
0470 | FTX | Free text | C | 1 |
0480 | SG13 | Group (×1) | M | 1 |
0490 | EMP | Employment details | M | 1 |
0500 | LOC | Place/location identification | C | 1 |
0510 | SG14 | Group (×100) | C | ×100 |
0520 | ATT | Attribute | M | 1 |
0530 | FTX | Free text | C | 1 |
0540 | PTY | Priority | C | 1 |
0550 | SG15 | Group (×20) | C | ×20 |
0560 | LAN | Language | M | 1 |
0570 | GEI | Processing information | C | ×3 |
0580 | UNT | Message trailer | M | 1 |
Summary
No segment in this section.
Changes vs D.96A
Top-level differences between D.96A and D.02B for the JOBAPP message (segments directly inside header / detail / summary, ignoring nested groups). The comparison is indicative: a given tag may have evolved inside nested groups without showing up in this synthesis.
Segments added vs D.96A
GEIin the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.GEIin the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
Segments removed vs D.96A
GISin the header section — present in D.96A but missing in D.02B at the same level.GISin the detail section — present in D.96A but missing in D.02B at the same level.
Structural example
Minimal example of an JOBAPP D.02B message with mandatory segments only. The goal is to show the exact version declared in UNH (JOBAPP:D:02B:UN) — not to replicate a full business case (see the JOBAPP D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL002001'
UNH+1+JOBAPP:D:02B:UN'
BGM+316+JOBAPP-2026-0042+9'
DTM+137:20260514:102'
RFF+AHI:VAC-2026-7811'
PNA+APP+CAND-2026-0042::ZZZ+++SU:DUPONT+FN:CLAIRE'
ADR+CD+++75001:PARIS:::FR'
COM+claire.dupont@example.com:EM'
NAD+EM+5410000000456::9'
UNT+9+1'
UNZ+1+CTRL002001'Common errors
- Misaligned UNH tokens — The
UNH+...+JOBAPP:D:02B:UNtoken must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator. - Wrong UNT segment count — The value after
UNT+must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use. - Stale code lists — Between D.96A and D.02B, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.
Related messages
Other versions of this message available on ediverse.io: JOBAPP D.96A, JOBAPP D.01B, JOBAPP D.10A, JOBAPP D.16B, JOBAPP D.21B, JOBAPP D.24A, JOBAPP D.97A, JOBAPP D.99B, JOBAPP D.00B, JOBAPP D.05A, JOBAPP D.08A, JOBAPP D.13B, JOBAPP D.18B, JOBAPP D.20B.