Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D03B Messages page. Job information demand message
0. INTRODUCTIONThis 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. SCOPE1.1. Functional definitionA 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 applicationThe 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. PrinciplesThe 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. REFERENCESSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Segment clarificationThis 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 sectionInformation to be provided in the Header section: 0010 UNH, Message headerA 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:
0020 BGM, Beginning of messageA 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/periodA 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-SG2A group of segments identifying the parties with associated information. 0050 PNA, Party identificationA 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, AddressA segment identifying the address of the relevant party. 0070 LOC, Place/location identificationA 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/periodA segment specifying the relevant date or time. 0090 Segment Group 2: CTA-COMA group of segments giving contact details of the specific person or department within the party identified in the PNA segment. 0100 CTA, Contact informationA segment to identify a person or department and their function, to whom communications should be directed. 0110 COM, Communication contactA 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-DTMA group of segments for giving references and, where necessary, their dates, relating to the whole message. 0130 RFF, ReferenceA segment identifying the reference by its number related to the whole message. 0140 DTM, Date/time/periodA segment specifying the date or time related to the reference. 0150 Segment Group 4: GEI-FTXA group of segments specifying general processing indicators and, when necessary, additional textual information, relevant for the whole message. 0160 GEI, Processing informationA segment specifying general indicators for the whole message. 0170 FTX, Free textA 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 sectionInformation to be provided in the Detail section: 0180 UNS, Section controlA 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-SG9A 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, ReferenceA 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-SG7A 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 identificationA 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, AddressA segment giving address(es) of the person identified in the previous PNA segment. 0240 LOC, Place/location identificationA 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/periodA 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, NationalityA segment indicating nationality (or nationalities) of the person identified in the previous PNA segment. 0270 PDI, Person demographic informationA segment providing personal information about the concerned person: i.e. gender, marital status. 0280 DOC, Document/message detailsA segment indicating the list of documents the concerned person has in his possession. 0290 Segment Group 7: CTA-COMA 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 informationA segment to identify a person or department and their function, to whom communications should be directed. 0310 COM, Communication contactA 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-DTMA group of segments for giving references and, where necessary, their dates, relevant to the demand of job information. 0330 RFF, ReferenceA segment for specifying references related to the demand of job information, e.g. social insurance number of a person. 0340 DTM, Date/time/periodA segment specifying the date or time related to the reference. 0350 FTX, Free textA 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-FTXA group of segments specifying general processing indicators and, when necessary, additional textual information relevant to the demand of job information. 0370 GEI, Processing informationA segment specifying general indicators related to the required information or documents. 0380 FTX, Free textA 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 trailerA 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)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D03B Messages page. |
![]() |
Site Map | Privacy Policy | Terms of Use | Trademarks |