|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4. Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued. The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags. |
| Message Type: | JINFDE |
|---|---|
| Version: | D |
| Release: | 95B |
| Contr. Agency: | UN |
| Status: | 1 |
| Revision: | 1 |
| Date: | 95-07-07 |
| 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 information demand message (JINFDE) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A message sent by a governmental agency to an employer in response to a work grant request. This message asks for specific additional information (e.g. visa) for further processing of the work grant request.
The Job information demand message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
The message is designed to request additional information about a person and/or a job (e.g. specific documents) for further processing of a work grant or permit request.
A Job Information Demand Message is transmitted from a governmental agency to an employer.
A Job Information Demand Message may contain detailed information about a person and/or the required missing documents.
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 Branching Diagram and 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 does 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 information demand message is JINFDE.
Note: Job information demand messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | JINFDE |
| 0052 | D | |
| 0054 | 95B | |
| 0051 | UN |
A segment by which the sender must uniquely identify the demand of job information 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 Information Demand Message. Identification of the enterprise and the job administration parties is mandatory for the Job Information Demand 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 identifying 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 relevant 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 the demand for job information. There must be at least one occurrence of Segment group 5 within an Job Information Demand Message. This Segment group may be repeated to give information about demands for job information of several other persons. The Segment group 5 gives information about the person and the required documents for further processing.
A segment identifying the administrative operation by a number given by the employment agency, e.g. work grant number of a foreign person.
A group of segments specifying identity and related information regarding the person designated in a work grant or permit request and those involved with the processing of job information.
A segment giving the identity in coded or clear form of the person as designated in the related work grant or permit request. It provides also name of the party involved with the processing of job information.
A segment giving address(es) of the person identified in the previous PNA segment.
A segment giving more specific location information of the party specified in the ADR segment, e.g. administrative location of a person.
A segment specifying date and, when relevant, time relating to the demand of job information. Examples of the use of this DTM segment are: date or time of work grant request.
A segment indicating nationality (or nationalities) of the person identified in the previous PNA segment.
A segment providing personal information about the concerned person: i.e. gender, marital status.
A segment indicating the list of documents the concerned person has in his possession.
A group of segments giving contact details of the specific person or department within the party identified in the PNA segment, e.g. person in a job center.
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, relevant to the demand of job information.
A segment for specifying references related to the demand of job information, e.g. social insurance number of a person.
A segment specifying the date or time related to the reference.
A segment with free text information for the required documents or job information, in coded or clear form. In computer to computer exchanges such text will normally require the receiver to process this segment manually.
A group of segments specifying general processing indicators and, when necessary, additional textual information relevant to the demand of job information.
A segment specifying general indicators related to the required information or documents.
A segment with free text information for the required documents or other 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 service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| ADR | Address | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| FTX | Free text | |
| GIS | General indicator | |
| LOC | Place/location identification | |
| NAT | Nationality | |
| PDI | Person demographic information | |
| PNA | Party name | |
| RFF | Reference | |
| 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 | ×9 | (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) |
| │─├─Segment Group 6 | ×999 | (M) |
| │─│─├─PNA Party name | ×1 | (M) |
| │─│─├─ADR Address | ×1 | (C) |
| │─│─├─LOC Place/location identification | ×2 | (C) |
| │─│─├─DTM Date/time/period | ×5 | (C) |
| │─│─├─NAT Nationality | ×9 | (C) |
| │─│─├─PDI Person demographic information | ×1 | (C) |
| │─│─├─DOC Document/message details | ×9 | (C) |
| │─│─└─Segment Group 7 | ×5 | (C) |
| │─│───├─CTA Contact information | ×1 | (M) |
| │─│───└─COM Communication contact | ×5 | (C) |
| │─├─Segment Group 8 | ×5 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×5 | (C) |
| │─├─FTX Free text | ×30 | (M) |
| │─└─Segment Group 9 | ×30 | (C) |
| │───├─GIS General indicator | ×1 | (M) |
| │───└─FTX Free text | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |