Directory   Messages   Segments   Composites   Data elements   Codes Meaning of the change indicators
  UN/EDIFACT  D.03A (Batch) Syntax version 3 Issue date 2003-06-23  
  Message type specification JINFDE
 
 
JINFDE 2 Job information demand message  
  Date:
2003-06-10

Source:
TBG11 Social Security, Employment and Education

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 Data 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.
 
  Generated by GEFEG.FX  
  http://www.gefeg.com