Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D04B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Job information demand message

Version:D
Release:04B
Contr. Agency:UN
Revision:2
Date:2004-11-23
SOURCE:TBG11 Social Security, Employment and Education

CONTENTS
Job information demand message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
      1. Header section
      2. Detail section
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, 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

0. INTRODUCTION

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.


1. SCOPE


1.1. Functional definition

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.


1.2. Field of application

The Job information demand 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.


1.3. Principles

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.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates 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.


4.1.1. Header section

Information to be provided in the Header section:

0010 UNH, Message header

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 element0065JINFDE
0052D
005404B
0051UN

0020 BGM, Beginning of message

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.

0030 DTM, Date/time/period

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.

0040 Segment Group 1: PNA-ADR-LOC-DTM-SG2

A group of segments identifying the parties with associated information.

0050 PNA, Party identification

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.

0060 ADR, Address

A segment identifying the address of the relevant party.

0070 LOC, Place/location identification

A segment giving more specific location information of the party specified in the ADR segment, e.g. internal site or building number.

0080 DTM, Date/time/period

A segment specifying the relevant date or time.

0090 Segment Group 2: CTA-COM

A group of segments giving contact details of the specific person or department within the party identified in the PNA segment.

0100 CTA, Contact information

A segment to identify a person or department and their function, to whom communications should be directed.

0110 COM, Communication contact

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.

0120 Segment Group 3: RFF-DTM

A group of segments for giving references and, where necessary, their dates, relating to the whole message.

0130 RFF, Reference

A segment identifying the reference by its number related to the whole message.

0140 DTM, Date/time/period

A segment specifying the date or time related to the reference.

0150 Segment Group 4: GEI-FTX

A group of segments specifying general processing indicators and, when necessary, additional textual information, relevant for the whole message.

0160 GEI, Processing information

A segment specifying general indicators for the whole message.

0170 FTX, Free text

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.


4.1.2. Detail section

Information to be provided in the Detail section:

0180 UNS, Section control

A mandatory service segment placed before the first user segment in the detail section to avoid segment collision.

0190 Segment Group 5: RFF-SG6-SG8-FTX-SG9

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.

0200 RFF, Reference

A segment identifying the administrative operation by a number given by the employment agency, e.g. work grant number of a foreign person.

0210 Segment Group 6: PNA-ADR-LOC-DTM-NAT-PDI-DOC-SG7

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.

0220 PNA, Party identification

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.

0230 ADR, Address

A segment giving address(es) of the person identified in the previous PNA segment.

0240 LOC, Place/location identification

A segment giving more specific location information of the party specified in the ADR segment, e.g. administrative location of a person.

0250 DTM, Date/time/period

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.

0260 NAT, Nationality

A segment indicating nationality (or nationalities) of the person identified in the previous PNA segment.

0270 PDI, Person demographic information

A segment providing personal information about the concerned person: i.e. gender, marital status.

0280 DOC, Document/message details

A segment indicating the list of documents the concerned person has in his possession.

0290 Segment Group 7: CTA-COM

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.

0300 CTA, Contact information

A segment to identify a person or department and their function, to whom communications should be directed.

0310 COM, Communication contact

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.

0320 Segment Group 8: RFF-DTM

A group of segments for giving references and, where necessary, their dates, relevant to the demand of job information.

0330 RFF, Reference

A segment for specifying references related to the demand of job information, e.g. social insurance number of a person.

0340 DTM, Date/time/period

A segment specifying the date or time related to the reference.

0350 FTX, Free text

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.

0360 Segment Group 9: GEI-FTX

A group of segments specifying general processing indicators and, when necessary, additional textual information relevant to the demand of job information.

0370 GEI, Processing information

A segment specifying general indicators related to the required information or documents.

0380 FTX, Free text

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.

0390 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.


4.2. Segment index (alphabetical sequence by tag)

ADR Address
BGM Beginning of message
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FTX Free text
GEI Processing information
LOC Place/location identification
NAT Nationality
PDI Person demographic information
PNA Party identification
RFF Reference
UNH Message header
UNS Section control
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×2 (M)
├─Segment Group 1 ×9 (M)
├─PNA Party identification ×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)
├─GEI Processing information ×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 identification ×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)
──├─GEI Processing information ×1 (M)
──└─FTX Free text ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D04B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.