EDIFACT message guide · Healthcare and social
JOBMOD Job order modification
The UN/EDIFACT message used to modify a job order previously sent for one or more vacancies.
- Sent by
- Employer or employment agency
- Received by
- Employment agency or employer
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT JOBMOD message?
JOBMOD is the UN/EDIFACT job order modification. The directory defines it as a message specifying modifications to a previously sent job order for one or more vacancies in an enterprise or organization, transmitted from an employer or employment agency.
Vacancies change: positions are filled, requirements are adjusted or the number of openings changes. Sending modifications keeps the agency from proposing candidates for jobs that no longer exist and keeps published vacancies accurate. It can also cancel a job order entirely. Modifications reference the vacancy numbers the agency confirmed in JOBCON.
How to read this diagram: the top row shows who sends JOBMOD, 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 JOBMOD 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
- Changing the number of vacancies
- Updating requirements or conditions
- Withdrawing a filled or cancelled vacancy
Where it fits in the message flow
Structure
Mandatory segments in JOBMOD (directory D.21A)
In UN/EDIFACT directory D.21A, the JOBMOD message has 58 segment positions arranged in 19 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
- UNS
- SG5 (RFF)
- UNT
Practical example
JOBMOD in practice
The logistics company fills ten of its 15 warehouse positions through its own recruitment. It sends the employment service a JOBMOD reducing the vacancy to five openings and correcting the shift pattern. The service updates the published vacancy and stops proposing candidates beyond the remaining openings.
Implementation
Implementation considerations for JOBMOD
- Reference the agency's vacancy number in every change.
- Send withdrawals promptly when positions are filled.
- Keep internal and agency records in step.
- Agree how partial changes are expressed.
How ECOM helps
Automate JOBMOD 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 JOBMOD?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.