pub:data_element_directory_for_dcs_passenger_messages
Различия
Показаны различия между двумя версиями страницы.
| Предыдущая версия справа и слеваПредыдущая версияСледующая версия | Предыдущая версияСледующая версияСледующая версия справа и слева | ||
| pub:data_element_directory_for_dcs_passenger_messages [2019/10/31 13:00] – kov | pub:data_element_directory_for_dcs_passenger_messages [2020/04/27 01:44] – mmaxm | ||
|---|---|---|---|
| Строка 5: | Строка 5: | ||
| < | < | ||
| Note 1: Each of the following elements starts on a new line when used; precede each element with a carriage return | Note 1: Each of the following elements starts on a new line when used; precede each element with a carriage return | ||
| - | and line feed (< | + | and line feed (<≡). |
| - | Note 2: “Data Field Name” refers to entries in the DCS Data Field Dictionary found in Recommended Practice 1707a. | + | Note 2: “Data Field Name” refers to entries in the DCS Data Field Dictionary found in Recommended Practice 1707a. |
| Note 3: Each line of a message has a limit of 64 characters as defined in the IATA Systems and Communications | Note 3: Each line of a message has a limit of 64 characters as defined in the IATA Systems and Communications | ||
| Reference Manual. When an element on a line causes the line to go beyond 64 characters, reposition the entire element | Reference Manual. When an element on a line causes the line to go beyond 64 characters, reposition the entire element | ||
| - | on the next line. | + | on the next line. \\ |
| - | 2.1 ADDRESS ELEMENT | + | 2.1 ADDRESS ELEMENT |
| - | 2.1.1 The address or addresses which are used for a message depend on bilateral agreements between the | + | 2.1.1 The address or addresses which are used for a message depend on bilateral agreements between the |
| - | carrier controlling the flight and the Handling Agent at the Boarding Point. | + | carrier controlling the flight and the Handling Agent at the Boarding Point. |
| 2.1.2 The construction of the Address Element for the “to” address is governed by the IATA Systems and | 2.1.2 The construction of the Address Element for the “to” address is governed by the IATA Systems and | ||
| - | Communications Reference. | + | Communications Reference. |
| - | Example of a double address: | + | Example of a double address: |
| - | ZRHKKSR AMSKKKL | + | ZRHKKSR AMSKKKL |
| 2.2 COMMUNICATIONS REFERENCE ELEMENT | 2.2 COMMUNICATIONS REFERENCE ELEMENT | ||
| This element for the “originator” is governed by the IATA Systems and Communications Reference. | This element for the “originator” is governed by the IATA Systems and Communications Reference. | ||
| Строка 599: | Строка 599: | ||
| - | **3.35 .X/ (NOT IN USE)**\\ | + | 3.35 .X/ (NOT IN USE)\\ |
| - | + | ||
| Construction Example Data Field Name 3.35.1 element ID .X/ element ID\\ | Construction Example Data Field Name 3.35.1 element ID .X/ element ID\\ | ||
| - | **3.36 .Y/ (NOT IN USE)**\\ | + | 3.36 .Y/ (NOT IN USE) \\ |
| Строка 611: | Строка 609: | ||
| - | **3.37 .Z/ (NOT IN USE)**\\ | + | 3.37 .Z/ (NOT IN USE) \\ |
| + | Construction Example Data Field Name 3.37.1 element ID .Z/ element ID\\ | ||
| - | Construction Example Data Field Name 3.37.1 element ID .Z/ element ID\\ | + | 3.38 PASSENGER IDENTIFICATION (ID)\\ |
| + | |||
| + | |||
| + | Passenger Identification is optional on a passenger element entry. | ||
| + | • If the element applies to all passengers in a family name (such as 3SMITH/ | ||
| + | • If the element applies to one or some, but not all, of the passengers in a family name, then the passenger ID element is mandatory (such as an element that applies only to Mr Brown in a name element of 2BROWN/ | ||
| + | • A passenger identification element can appear only once per element, as shown in the examples below. | ||
| + | |||
| + | 3.38.1 applicable passenger name(s) | ||
| + | |||
| + | -1COTE/ | ||
| + | |||
| + | Examples: | ||
| + | The PNR holds The DCS message entry is One passenger: | ||
| + | |||
| + | Passenger ID is optional: 1FOX/ABEMR 1FOX/ | ||
| + | .R/FQTV AI 43211 (with an SSR FQTV for Mr. A. Fox) or 1FOX/ | ||
| + | .R/FQTV AI 43211-1FOX/ | ||
| + | |||
| + | The PNR holds The DCS message entry is Multiple passengers with multiple surnames: | ||
| + | |||
| + | Elements with and without passenger ID: \\ | ||
| + | 3BAKER/ | ||
| + | |||
| + | .L/ | ||
| + | .R/FQTV JD 98765432-1BAKER/ | ||
| + | .R/FQTR JD 12345678 (with an SSR FQTR for Mrs. Upton) \\ | ||
| + | |||
| + | The PNR holds The DCS message entry is Multiple passengers with the same surname: \\ | ||
| + | Elements with and without passenger ID: \\ | ||
| + | 3DAHL/ | ||
| + | .L/ | ||
| + | .R/VGML HK3 an SSR BIKE for Mrs. DAHL and for Ms. DAHL) \\ | ||
| + | .R/BIKE HK2-2DAHL/ | ||
| + | Recommended Practice 1707b 3.39 SSR/OSI/AUX SERVICES ELEMENT \\ | ||
| + | |||
| + | This element lists the SSR/OSI/AUX code(s) that apply to a passenger. \\ | ||
| + | |||
| + | Construction Example Data Field Name \\ | ||
| + | |||
| + | 3.39.1 space → information separator \\ | ||
| + | 3.39.2 SSR, OSI or AUX code WCHR SSR/OSI/AUX code \\ | ||
| + | 3.39.3 space(if free text follows) → information separator \\ | ||
| + | 3.39.4 free text BROKEN LEG free flow text (If free text exceeds one line, end the line at the end of a word, indent six spaces on the next line and continue the free text.) \\ | ||
| + | |||
| + | Examples: BLND TRAVELLING WITH SERVICE DOG NAMED GINGER MEDA THIS PASSENGER IS TRAVELLING WITH WIFE AND MEDICAL ASST. \\ | ||
| + | DAPO TO MEET AND ASSIST WITH DEBOARDING VIP MR LARSON IS THE PRESIDENT OF OUR EUROPE OPERATIONS OF THE NEW ORGANIZATION OF ECONOMIC DEVELOPMENT \\ | ||
| + | |||
| + | 3.40 API (ADVANCE PASSENGER INFORMATION) ELEMENTS These elements are used to record the API SSR codes for travel documents, travel related information, | ||
| + | This becomes an important factor in the creation of PAXLST Elements in DCS messages, in that the PAXLST DOCx rule for mandatory separator obliques will show the empty fields (up to the last present field). | ||
| + | For example, the ‘Known Traveler’ in \\ | ||
| + | .R/DOCO does not have a ‘place or date of issue’; therefore, the two fields will be blank with mandatory obliques in their place. \\ | ||
| + | |||
| + | 3.40.1 API DOCS Element This element lists Passenger primary travel documents. | ||
| + | Where the components of a DOCS element are not provided, an oblique (/) is inserted to indicate an element is missing. This is not required when no further components are provided. The Passenger Identification Element may follow the final element entered. The elements Travel Document Surname, Travel Document First Given Name and Travel Document Second Given Name must match the surname, first given name and second given name (if applicable) as shown in the official travel document. If the name is from the Machine Readable Zone (MRZ) of an official document, e.g. passport, the chevron character (<) in the MRZ should be interpreted as a space character. A double chevron (<<) should be interpreted as a change of field, e.g. from surname to given name. Spaces in the name fields of the SSR DOCS should not be removed and should be transmitted in messages to business partners and governments. Construction Example Data Field Name \\ | ||
| + | |||
| + | 3.40.1.1 element ID for Remarks Element \\ | ||
| + | .R/ element ID \\ | ||
| + | |||
| + | 3.40.1.2 SSR code DOCS SSR/OSI/AUX code \\ | ||
| + | |||
| + | 3.40.1.3 space → information separator \\ | ||
| + | |||
| + | 3.40.1.4 action/ | ||
| + | |||
| + | 3.40.1.5 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.6 travel document type I a(a) \\ | ||
| + | |||
| + | 3.40.1.7 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.8 travel document issuing country/ | ||
| + | |||
| + | 3.40.1.9 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.10 travel document number D23145890 m[..15] \\ | ||
| + | |||
| + | 3.40.1.11 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.12 passenger nationality US country code \\ | ||
| + | |||
| + | 3.40.1.13 oblique / information separator 32ND EDITION, JUNE 2012 845 Passenger Services Conference Resolutions Manual Construction Example Data Field Name \\ | ||
| + | |||
| + | 3.40.1.14 date of birth 12JUL64 date of birth \\ | ||
| + | |||
| + | 3.40.1.15 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.16 gender code M gender code \\ | ||
| + | |||
| + | 3.40.1.17 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.18 travel document expiry date 12JUL04 date/full \\ | ||
| + | |||
| + | 3.40.1.19 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.20 travel document surname STEVENSON surname \\ | ||
| + | |||
| + | 3.40.1.21 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.22 travel document first given name THOMAS first name \\ | ||
| + | |||
| + | 3.40.1.23 oblique / information separator \\ | ||
| + | |||
| + | 3.40.1.24 travel document second given name RICHARD first name \\ | ||
| + | |||
| + | 3.40.1.25 oblique (if H follows) / information separator \\ | ||
| + | |||
| + | 3.40.1.26 multi-passenger passport holder indicator H H \\ | ||
| + | |||
| + | 3.40.1.27 passenger identification -1STEVENSON/ | ||
| + | |||
| + | ID Example showing a DOCS for an adult male, with a continuation element: \\ | ||
| + | |||
| + | .R/DOCS HK1/ | ||
| + | .RN/ | ||
| + | Example showing a DOCS for an adult, female, multi-name passport holder (H), accompanied by a female infant (FI) on the same passport: \\ | ||
| + | .R/DOCS HK1/ | ||
| + | .R/DOCS HK1/ | ||
| + | |||
| + | 3.40.2 API DOCO Element This element lists Passenger other travel related information. \\ | ||
| + | Where the components of a DOCO element provided, an oblique (/) is inserted to indicate an element is missing. This is not required when no further components are provided. | ||
| + | The Passenger Identification Element may follow the final element entered. Construction Example Data Field Name \\ | ||
| + | |||
| + | 3.40.2.1 element ID .R/ element ID \\ | ||
| + | 3.40.2.2 SSR code DOCO SSR/OSI/AUX code \\ | ||
| + | 3.40.2.3 space → information separator | ||
| + | 3.40.2.4 action/ | ||
| + | 3.40.2.5 oblique / information separator | ||
| + | 3.40.2.6 place of birth AMBER HILL GBR a(..35) | ||
| + | 3.40.2.7 oblique / information separator | ||
| + | 3.40.2.8 travel document type V a(a) \\ | ||
| + | 3.40.2.9 oblique / information separator | ||
| + | 3.40.2.10 travel document number 9891404 m[..25] | ||
| + | 3.40.2.11 oblique / information separator | ||
| + | 3.40.2.12 travel document place of issue LONDON a(..35) | ||
| + | 3.40.2.13 oblique / information separator | ||
| + | 3.40.2.14 travel document issue date 12JUL64 date/ | ||
| + | 3.40.2.15 oblique / information separator | ||
| + | 3.40.2.16 country/ | ||
| + | 3.40.2.17 oblique (if Infant indicator follows) / information separator \\ | ||
| + | 3.40.2.18 infant indicator I I \\ | ||
| + | 3.40.2.19 passenger identification -1ADDAMS/ | ||
| + | Examples: \\ | ||
| - | **3.38 PASSENGER IDENTIFICATION (ID)**\\ | + | .R/DOCO HK1/AMBER HILL GBR-1BROSNAN/ |
| + | .R/DOCO HK1/BREMEN DEU \\ | ||
| + | //// | ||
| + | 3.40.3 API DOCA Element This element lists Passenger address information. Where the components of a DOCA element are not provided, an oblique (/) is inserted to indicate an element is missing. This is not required when no further components are provided. The Passenger Identification Element may follow the final element entered. Construction Example Data Field Name | ||
| + | 3.40.3.1 element ID .R/ element ID \\ | ||
| + | 3.40.3.2 SSR code DOCA SSR/OSI/AUX code \\ | ||
| + | 3.40.3.3 space → information separator \\ | ||
| + | 3.40.3.4 action/ | ||
| + | 3.40.3.5 number of passengers to whom the element applies 2 number/ | ||
| + | 3.40.3.6 oblique / information separator 3.40.3.7 type of address: D-Destination, | ||
| + | 3.40.3.8 oblique / information separator \\ | ||
| + | 3.40.3.9 country US country code \\ | ||
| + | 3.40.3.10 oblique / information separator \\ | ||
| + | 3.40.3.11 address details 1600 SMITH STREET m[..35] \\ | ||
| + | 3.40.3.12 oblique / information separator \\ | ||
| + | 3.40.3.13 city HOUSTON a(..35) \\ | ||
| + | 3.40.3.14 oblique / information separator 3.40.3.15 state/ | ||
| + | 3.40.3.16 oblique / information separator 3.40.3.17 zip/postal code 77001 m[..17] \\ | ||
| + | 3.40.3.18 oblique (if Infant indicator follows) / information separator \\ | ||
| + | 3.40.3.19 infant indicator I I \\ | ||
| + | 3.40.3.20 passenger identification -1BREKKE/ | ||
| - | Passenger Identification is optional on a passenger element entry. • If the element applies to all passengers in a family name (such as 3SMITH/ | + | Example: |
| + | .R/DOCA HK1/ | ||
| + | .R/DOCA HK1/ | ||
| + | .R/DOCA HK3/R/CH/33 ROUTE DE LAEROPORT/ | ||
pub/data_element_directory_for_dcs_passenger_messages.txt · Последнее изменение: 2020/04/27 02:12 — mmaxm