% Response.CharSet="utf-8" %>
| Version: | D |
|---|---|
| Release: | 97A |
| Contr. Agency: | UN |
| Revision: | 1 |
| Date: | 96-12-13 |
| SOURCE: | Western European EDIFACT Board, MD10 |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Job application proposal message (JOBAPP) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message specifying detailed information of proposals for one or more job applicants from an employment agency to an employer. The detailed information is related to profession, occupation, age, education, experiences, salaries, other benefits, requested location of the job, work and contract conditions.
The Job application proposal message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
The intention of the message is to provide information of proposals for one or more job applicants. A Job Application Proposal Message is transmitted from an employment agency to an employer or an employment agency. A Job Application Proposal Message may contain detailed information, in form of advertisements, of one or more applicants. A Job Application Proposal Message may be related to earlier offered jobs or vacancies by an employer.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.
The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message: All specified dates and times should be in the format 'yymmdd' or 'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, months, etc). Where a choice of code or text is given only the code element should be used wherever possible. Conditional data that is not required in the message should not be included. Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of a group.
Information to be provided in the Header section:
A service segment starting and uniquely identifying a message. The message type code for the Job application proposal message is JOBAPP.
Note: Job application proposal messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | JOBAPP |
| 0052 | D | |
| 0054 | 97A | |
| 0051 | UN |
A segment by which the sender must uniquely identify the job application proposal by means of its type and number and, when necessary, its function.
A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the document date. The Date/time/period segment within other Segment groups should be used whenever the date or time or period requires to be logically related to another specified data item.
A group of segments identifying the parties with associated information.
A segment identifying names of the parties, in coded or clear form, and their functions relevant to the Job Application Proposal Message. Identification of the enterprise and the job administration parties is mandatory for the Job Application Proposal Message. It is recommended that, where possible, only the coded form of the party identification should be specified, e.g. where the enterprise and the job administration are known to each other, thus only the coded identification is required, but a job center or a job application address (interview) may vary and would have to be clearly specified, preferably in structured format.
A segment indicating the address of the relevant party.
A segment giving more specific location information of the party specified in the ADR segment, e.g. internal site or building number.
A segment specifying the date or time.
A group of segments giving contact details of the specific person or department within the party identified in the PNA segment.
A segment to identify a person or department and their function, to whom communications should be directed.
A segment to identify a communications type and number for the contact specified in the CTA segment, e.g. telephone-number, fax-number, telex-number.
A group of segments for giving references and, where necessary, their dates, relating to the whole message.
A segment identifying the reference by its number related to the whole message.
A segment specifying the date or time related to the reference.
A group of segments specifying general processing indicators and, when necessary, additional textual information, relevant for the whole message.
A segment specifying general indicators for the whole message.
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
Information to be provided in the Detail section:
A mandatory service segment placed before the first user segment in the detail section to avoid segment collision.
A group of segments providing details of a job application. This Segment group may be repeated to give information about several other job application proposals. The Segment group 5 gives detailed information, in coded or textual form, e.g. job advertisement, of one or more applicants. The information may be related to an earlier sent job order of an employer.
A segment identifying the administrative operation of a job application by a number given by an employment agency, e.g. order number of an employment agency.
A segment specifying date and, when relevant, time relating to the RFF segment. Examples of the use of this DTM segment are: order date or time of the employment agency.
A group of segments identifying an applicant and related information for a job requirement.
A segment giving the identity of the applicant.
A segment specifying the date of birth of the applicant.
A segment indicating the place of birth of the applicant. It may also specify requirements regarding the job location.
A segment indicating nationality (or nationalities) of the person identified in the previous PNA segment.
A segment providing personal information about the applicant: i.e. gender, marital status.
A segment indicating the list of documents the concerned person has in his possession.
A group of segments specifying general processing indicators and, when necessary, additional textual information, relevant for the proposed person.
A segment specifying general indicators related to the proposed person.
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A group of segments identifying requirements or conditions of one or more applicants.
A segment to give in coded form the requirements for a job application.
A segment with free text information (job qualifications and requirements for individual applicants) related to job advertisement, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A group of segments giving information about the requesting remuneration and conditions regarding the remuneration.
A segment identifying the type of the remuneration requested, and if relevant the name of the remuneration type or contract.
A segment used when additional information regarding the remuneration type or contract and which cannot be accommodated within other segment.
A group of segments giving attribute information, in coded form for the remuneration and, where necessary, additional textual information.
A segment identifying additional remuneration information in coded form. The codes are also related to working condition, working time, employment contract, piece work and remuneration benefits.
A segment specifying in free text form the additional information which cannot be accommodate within other segments.
A group of segments specifying processing indicators and, if necessary, additional textual information, relevant to the required remuneration.
A segment specifying general indicator related to the remuneration required.
A segment specifying in free text form a process regarding the required remuneration which cannot be accommodated within another segment.
A group of segments specifying the type and the amount of the remuneration or a remuneration range required.
A segment giving information about the type and the amount of the remuneration required.
A segment to identify a remuneration range when the exact remuneration of the previous MOA segment is not available. The remuneration range is related to the type of remuneration in the MOA segment.
A segment in coded and free text form to specify any other information regarding the remuneration amount.
A group of segments identifying a profession or occupation of an applicant and attributes of a profession or occupation related to the job advertisement.
A segment to identify the related area or sector of a qualification and a qualification, in coded or clear form, related to the job advertisement.
A segment indicating the location or place, where the qualification or job should be performed.
A group of segments giving coded information about the attributes of a profession relating to education and experience and, when necessary, priority of the information and additional textual information.
A segment identifying, in coded form, the attributes of a profession. The codes are related to education, job experience, special knowledge and qualifications.
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A segment identifying the priority of requirements for a job offered.
A group of segments giving information about languages and experiences of languages.
A segment specifying a language in coded or clear form.
A segment specifying general indicators of the experience of a language.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| ADR | Address | |
| ATT | Attribute | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| EMP | Employment details | |
| FTX | Free text | |
| GIS | General indicator | |
| LAN | Language | |
| LOC | Place/location identification | |
| MOA | Monetary amount | |
| NAT | Nationality | |
| PDI | Person demographic information | |
| PNA | Party name | |
| PTY | Priority | |
| RCS | Requirements and conditions | |
| RFF | Reference | |
| RNG | Range details | |
| SAL | Remuneration type identification | |
| UNH | Message header | |
| UNS | Section control | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×2 | (M) |
| ├─Segment Group 1 | ×99 | (M) |
| │─├─PNA Party name | ×1 | (M) |
| │─├─ADR Address | ×1 | (C) |
| │─├─LOC Place/location identification | ×5 | (C) |
| │─├─DTM Date/time/period | ×5 | (C) |
| │─└─Segment Group 2 | ×5 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×5 | (C) |
| ├─Segment Group 3 | ×5 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×5 | (C) |
| ├─Segment Group 4 | ×5 | (C) |
| │─├─GIS General indicator | ×1 | (M) |
| │─└─FTX Free text | ×1 | (C) |
| ├─UNS Section control | ×1 | (M) |
| ├─Segment Group 5 | ×999 | (M) |
| │─├─RFF Reference | ×1 | (M) |
| │─├─DTM Date/time/period | ×99 | (C) |
| │─├─Segment Group 6 | ×1 | (C) |
| │─│─├─PNA Party name | ×1 | (M) |
| │─│─├─DTM Date/time/period | ×1 | (C) |
| │─│─├─LOC Place/location identification | ×9 | (C) |
| │─│─├─NAT Nationality | ×9 | (C) |
| │─│─├─PDI Person demographic information | ×1 | (C) |
| │─│─└─DOC Document/message details | ×9 | (C) |
| │─├─Segment Group 7 | ×5 | (C) |
| │─│─├─GIS General indicator | ×1 | (M) |
| │─│─└─FTX Free text | ×1 | (C) |
| │─├─Segment Group 8 | ×99 | (M) |
| │─│─├─RCS Requirements and conditions | ×1 | (M) |
| │─│─└─FTX Free text | ×99 | (C) |
| │─├─Segment Group 9 | ×1 | (C) |
| │─│─├─SAL Remuneration type identification | ×1 | (M) |
| │─│─├─FTX Free text | ×1 | (C) |
| │─│─├─Segment Group 10 | ×10 | (C) |
| │─│─│─├─ATT Attribute | ×1 | (M) |
| │─│─│─└─FTX Free text | ×1 | (C) |
| │─│─├─Segment Group 11 | ×2 | (C) |
| │─│─│─├─GIS General indicator | ×1 | (M) |
| │─│─│─└─FTX Free text | ×1 | (C) |
| │─│─└─Segment Group 12 | ×5 | (C) |
| │─│───├─MOA Monetary amount | ×1 | (M) |
| │─│───├─RNG Range details | ×1 | (C) |
| │─│───└─FTX Free text | ×1 | (C) |
| │─└─Segment Group 13 | ×1 | (M) |
| │───├─EMP Employment details | ×1 | (M) |
| │───├─LOC Place/location identification | ×1 | (C) |
| │───├─Segment Group 14 | ×100 | (C) |
| │───│─├─ATT Attribute | ×1 | (M) |
| │───│─├─FTX Free text | ×1 | (C) |
| │───│─└─PTY Priority | ×1 | (C) |
| │───└─Segment Group 15 | ×20 | (C) |
| │─────├─LAN Language | ×1 | (M) |
| │─────└─GIS General indicator | ×3 | (C) |
| └─UNT Message trailer | ×1 | (M) |