pub:data_element_directory_for_dcs_passenger_messages
Различия
Показаны различия между двумя версиями страницы.
| Предыдущая версия справа и слеваПредыдущая версия | |||
| pub:data_element_directory_for_dcs_passenger_messages [2020/04/27 01:54] – mmaxm | pub:data_element_directory_for_dcs_passenger_messages [2020/04/27 02:12] (текущий) – mmaxm | ||
|---|---|---|---|
| Строка 513: | Строка 513: | ||
| < | < | ||
| - | Note 1: “Data Field Name” refers to entries in the DCS Data Dictionary found in Recommended Practice 1707a. Note 2: Each line of a message has a limit of 64 characters as defined in the IATA Systems and Communications Reference Manual. When any DCS element at the passenger level causes a line of text to exceed 64 positions, reposition and begin the entire element on the next line. If it still overflows, then use the element continuation procedures outlined for each element (where present). Where continuation procedures are not present, the element is to be truncated at the 64th position. Generally, truncate or breakoff an element for continuation on the boundary of a full data field. For example, the date 12JUN99 or the city pair LAXHKG should be taken as a whole for truncation or continuation on the next line. Never break at a partial field, such as 12JU or LAXHK in this example. Free flow text can be broken at any point. Note 3: DCS Elements at the passenger level appear only after the Name Element and can be in any order. | + | Note 1: “Data Field Name” refers to entries in the DCS Data Dictionary found in Recommended Practice 1707a. |
| + | Note 2: Each line of a message has a limit of 64 characters as defined in the IATA Systems and Communications Reference Manual. | ||
| + | When any DCS element at the passenger level causes a line of text to exceed 64 positions, reposition and begin the entire element on the next line. | ||
| + | If it still overflows, then use the element continuation procedures outlined for each element (where present). | ||
| + | Where continuation procedures are not present, the element is to be truncated at the 64th position. | ||
| + | Generally, truncate or breakoff an element for continuation on the boundary of a full data field. | ||
| + | For example, the date 12JUN99 or the city pair LAXHKG should be taken as a whole for truncation or continuation on the next line. | ||
| + | Never break at a partial field, such as 12JU or LAXHK in this example. Free flow text can be broken at any point. | ||
| + | Note 3: DCS Elements at the passenger level appear only after the Name Element and can be in any order. | ||
| + | 3.1 .A/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.1.1 element ID .A/ element ID | ||
| - | **3.31 .U/PASSENGER SYSTEM IDENTIFIER PER SEGMENT | + | 3.2 .B/ (NOT IN USE) Construction Example Data Field Name |
| + | 3.2.1 element ID .B/ element ID | ||
| + | 3.3 .BG/ BAGGAGE POOLING ELEMENT This element is used to associate all members of a party/group back to a single member when all of the baggage for the party/group has been | ||
| + | “pooled” (checked) with that one member, the “head of the pooled baggage”. | ||
| + | The purpose of pooling baggage is to expedite the check-in process for large parties/ | ||
| + | Construction Example Data Field Name | ||
| + | 3.3.1 element ID .BG/ element ID | ||
| + | 3.3.2 pooling reference number 001 number/ | ||
| + | Example: | ||
| + | .BG/ | ||
| - | This element conveys a unique passenger system identifier for each flight segment. The identifier is assigned by the sending system for purposes of data collection and statistical analysis. It is composed of the following information: | + | 3.4 .C/ CORPORATE OR GROUP NAME ELEMENT |
| + | Construction Example Data Field Name | ||
| + | 3.4.1 element ID .C/ element ID | ||
| + | 3.4.2 corporate name USA/TOUR corporate name | ||
| + | Example: | ||
| + | .C/ | ||
| - | **3.32 .V/ (NOT IN USE)**\\ | + | 3.5 .D/ DEFINED TOUR OPERATOR ELEMENT Construction |
| + | Example Data Field Name | ||
| + | 3.5.1 element ID .D/ element ID | ||
| + | 3.5.2 annotation AIR2000 Tour operator | ||
| + | Example: .D/ | ||
| - | Construction Example Data Field Name 3.32.1 element ID .V/ element ID\\ | + | 32ND EDITION, JUNE 2012 835 Passenger Services Conference Resolutions Manual |
| + | 3.6 .DBC/ DENIED BOARDING COMPENSATION ELEMENT This is used to indicate confirmed passengers receiving denied boarding compensation. Construction Example Data Field Name | ||
| + | 3.6.1 element ID .DBC/ element ID | ||
| + | 3.6.2 voluntary indicator (V) or involuntary indicator (I) V alpha/ | ||
| + | 3.6.3 oblique (if free text follows) / information separator | ||
| + | 3.6.4 type of compensation USD200 free flow text Example: .DBC/ | ||
| - | **3.33 .W/ PIECES/ | + | 3.7 .DG1/ FIRM DG PASSENGER |
| + | 3.7.1 element ID .DG1/ element ID 3.7.2 priority code PSN49 priority designator | ||
| + | 3.7.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.7.4 (optional) seniority date 11JUN86 date/full Example: .DG1/ | ||
| + | 3.8 .DG2/ SPACE AVAILABLE DG PASSENGER ELEMENT Construction | ||
| + | Example Data Field Name | ||
| - | 3.33 .W/ PIECES/WEIGHT DATA ELEMENT\\ | + | 3.8.1 element ID .DG2/ element ID |
| + | 3.8.2 priority code PSN68 priority indication | ||
| + | 3.8.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.8.4 (optional) seniority date 11JUN86 date/full | ||
| + | Example: .DG2/PSN68-12AUG82 | ||
| + | 3.9 .E/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.9.1 element ID .E/ element ID | ||
| - | Construction Example Data Field Name\\ | + | 3.10 .F FREQUENT TRAVELLER ELEMENT |
| + | 3.10.1 element ID .F/ element ID | ||
| + | 3.10.2 airline SK airline code | ||
| + | 3.10.3 space → information separator | ||
| + | 3.10.4 account number 123456789 account number | ||
| + | Example: | ||
| + | .F/KL 123456789 | ||
| + | .F/DL A97654321012345 836 | ||
| + | 32ND EDITION, JUNE 2012 Recommended Practice 1707b | ||
| + | 3.11 .G/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.11.1 element ID .G/ element ID | ||
| - | 3.33.1 element ID .W/ element ID\\ | + | 3.12 .H/ (NOT IN USE) Construction Example Data Field Name |
| + | 3.12.1 element ID .H/ element ID | ||
| + | 3.13 .I/ INBOUND CONNECTION ELEMENT Construction Example Data Field Name | ||
| + | 3.13.1 element ID .I/ element ID | ||
| + | 3.13.2 flight information: | ||
| + | 07 date/day boarding point MUC airport code arrival point (conditional: | ||
| + | flight in the message being created; optional when the same) JFK airport code arrival time (conditional: | ||
| + | is used; otherwise optional) /M1 date variation date variation (conditional: | ||
| + | from the departure date of the inbound connection. Not allowed when the date is the same. May have a value of minus 1, plus 1 or plus | ||
| + | 2.) /M1 date variation reservations status (optional) HK status | ||
| + | Example: | ||
| + | .I/ | ||
| + | .I/ | ||
| + | .I/ | ||
| - | 3.33.2 pieces/weight indicator K pieces/weight indicator\\ | + | 3.14 .ID1/ FIRM ID PASSENGER ELEMENT This is used for positive space ID passengers. Construction Example Data Field Name |
| + | 3.14.1 element ID .ID1/ element ID | ||
| + | 3.14.2 priority code ID00S1 priority designator | ||
| + | 3.14.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.14.4 (optional) seniority date 11JUN86 date/full | ||
| + | Example: .ID1/ID00S1-11JUN86 32ND EDITION, JUNE 2012 837 Passenger Services Conference Resolutions Manual | ||
| + | 3.15 .ID2/ SPACE AVAILABLE ID PASSENGER ELEMENT This is used for space available ID passengers. Construction Example Data Field Name | ||
| + | 3.15.1 element ID .ID2/ element ID | ||
| + | 3.15.2 priority code F2 priority designator | ||
| + | 3.15.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.15.4 (optional) seniority date 11JUN86 date/full Example: .ID2/ | ||
| + | 3.16 .J/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.16.1 element ID .J/ element ID | ||
| + | 3.17 .K/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.17.1 element ID .K/ element ID | ||
| + | 3.18 .L/ AUTOMATED PNR ADDRESS ELEMENT Members may include one or more automated PNR addresses (also known as file references or record locators); | ||
| + | each PNR address is to appear in its own separate .L/ element. When a single .L/ element appears, the company designator is optional. | ||
| + | When a single .L/ element appears with no company designator, it is assumed to be the record locator of the airline code of the airline in the Flight | ||
| + | Element of the DCS message. When more than one automated PNR address element appears for a PNR entry each must contain only one PNR address and each | ||
| + | must have a unique company designator, such as in the case of a code share flight or a CRS service provider. Construction Example Data Field Name | ||
| - | K = kilos | + | 3.18.1 element ID .L/ element ID |
| + | 3.18.2 automated PNR address S4627W automated PNR address | ||
| + | 3.18.3 oblique (if company designator follows) / information separator | ||
| + | 3.18.4 (conditional) company designator JD airline code (when absent, implies the record locator of the airline in the Flight Element of the DCS message.) | ||
| + | (when more than one .L/ element is present for the passenger entry, then the company designator is mandatory in each .L/ element.) (when only one .L/ element | ||
| + | is present for the passenger entry, then the company designator is optional.) | ||
| + | Examples: | ||
| + | .L/S2798Z | ||
| + | .L/ | ||
| + | .L/ | ||
| + | .L/ | ||
| + | .L/ Elements appear) | ||
| - | L = pounds | + | 838 32ND EDITION, JUNE 2012 Recommended Practice 1707b |
| + | 3.19 .M/ MARKETING FLIGHT INFORMATION ELEMENT Construction Example Data Field Name | ||
| + | 3.19.1 element ID .M/ element ID | ||
| + | 3.19.2 flight information: | ||
| + | departure time (optional) 1000 time reservations status (optional) HK status code | ||
| + | Example: | ||
| + | .M/ | ||
| + | 3.20 .N/ BAGGAGE TAG DETAILS ELEMENT This element is used to record consecutive bag tag numbers. When a Name Element has multiple bags with nonconsecutive | ||
| + | bag tag numbers, use multiple .N/ elements. As bilaterally agreed, the information will be provided using either the numeric or alphanumeric formats of the | ||
| + | baggage tag as described in IATA Resolution 740. | ||
| + | |||
| + | 3.20.1 Numeric version Construction Example Data Field Name | ||
| + | 3.20.1.1 element ID .N/ element ID | ||
| + | 3.20.1.2 baggage tag number 0074123456 baggage tag ID: licence plate number | ||
| + | 3.20.1.3 number of consecutive tags 005 number/ | ||
| + | 3.20.1.4 oblique (/) / information separator | ||
| + | 3.20.1.5 final destination to which bag(s) are checked SFO airport code | ||
| + | |||
| + | Example: | ||
| + | .N/ | ||
| + | 3.20.2 Alpha Numeric version Construction Example Data Field Name | ||
| + | 3.20.2.1 element ID .N/ element ID | ||
| + | 3.20.2.2 baggage tag ID number baggage tag ID: KL123456 Alpha/ | ||
| + | 3.20.2.3 oblique / information separator | ||
| + | 3.20.2.4 number of consecutive tags 5 number of bags | ||
| + | 3.20.2.5 oblique / information separator | ||
| + | 3.20.2.6 final destination to which bag(s) are checked SFO airport code | ||
| + | Example: | ||
| + | .N/ | ||
| + | 32ND EDITION, JUNE 2012 839 Passenger Services Conference Resolutions Manual | ||
| + | |||
| + | 3.21 .O/ ONWARD CONNECTION(S) ELEMENT It is mandatory that reservations systems list all onward connections from the PNR that are downline in the PNR. | ||
| + | The uses for having all onward connections in DCS include automated thru check-in and proper thrubaggage processing. | ||
| + | Construction | ||
| + | Example Data Field Name | ||
| + | 3.21.1 element ID .O/ element ID element ID with suffix .O2/ element ID | ||
| + | 3.21.2 flight information: | ||
| + | mandatory when different from the arrival point of the flight in the message being created or a previous .O/ element; optional when the same.) | ||
| + | HND airport code arrival point LHR airport code departure time (optional) 1400 time arrival time (conditional: | ||
| + | exists; otherwise optional) date variation (conditional: | ||
| + | when the date is the same. May have a value of minus 1, plus 1 or plus 2.) /M1 date variation reservations status (optional) KL status | ||
| + | Example: | ||
| + | .O/ | ||
| + | .O2/ | ||
| + | .O3/ | ||
| + | .O/ | ||
| + | .O2/ | ||
| + | .O/ | ||
| + | |||
| + | 3.22 .P/ (NOT IN USE) Construction | ||
| + | Example Data Field Name | ||
| + | 3.22.1 element ID .P/ element ID | ||
| + | 3.23 .Q/ (NOT IN USE) Construction Example Data Field Name | ||
| + | 3.23.1 element ID .Q/ element ID | ||
| + | |||
| + | 3.24 .R/ REMARKS ELEMENT As mentioned in Note 2 at the beginning of Section 3, unique continuation rules apply for this element. | ||
| + | A Remarks Element that is greater than the length of one message line is to be continued on the next line. Break the element at the 64th character. | ||
| + | Enter the Element ID code of .RN/ and continue the element data from where it was broken on the previous line. Multiple, successive .RN/ elements can be used | ||
| + | for the continuation of one .R/ Remarks Element. 840 32ND EDITION, JUNE 2012 Recommended Practice 1707b Construction Example Data Field Name | ||
| + | 3.24.1 element ID for Remarks Element .R/ element ID | ||
| + | 3.24.2 applicable SSR, OSI or AUX code SFML SSR/OSI/AUX code or bilateral (number, when present, may precede OSI code) 1VIP agreed code (Bilateral agreed code) ETLP | ||
| + | 3.24.3 space → information separator | ||
| + | 3.24.4 action/ | ||
| + | 3.24.5 space → information separator | ||
| + | 3.24.6 where required, fields as defined in RP1708 for certain types of Remarks Elements | ||
| + | 3.24.7 additional element information free flow format FIRST TIME FLYER free flow text | ||
| + | 3.24.8 Passenger ID: Add according to the rules in RP -1JONES/ | ||
| + | 3.24.9 element ID for Remarks continuation .RN/ element ID | ||
| + | 3.24.10 continuation of Remarks text MORE INFO free flow text | ||
| + | Example: | ||
| + | 2HARTSHORNE/ | ||
| + | .L/ | ||
| + | .R/STCR HK1 | ||
| + | PASSENGER HAS BROKEN HIP AND LEG AND IS WEARING | ||
| + | .RN/A FLEXIBLE BODY CAST WITH HIP IN PLASTER CAST. DO ALL | ||
| + | .RN/ | ||
| + | .RN/ON ARRIVAL-1HARTSHORNE/ | ||
| + | .R/VGML NN1-1HARTSHORNE/ | ||
| + | |||
| + | 3.25 .RG1/FIRM RG PASSENGER ELEMENT Construction Example Data Field Name | ||
| + | 3.25.1 element ID .RG1/ element ID 3.25.2 priority code PSN68 priority designator | ||
| + | 3.25.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.25.4 (optional) seniority date 12AUG82 date/ | ||
| + | Example: | ||
| + | .RG1/ | ||
| + | |||
| + | 3.26 .RG2/ SPACE AVAILABLE RG PASSENGER ELEMENT Construction Example Data Field Name | ||
| + | 3.26.1 element ID .RG2/ element ID | ||
| + | 3.26.2 priority code PSN68 priority designator | ||
| + | 3.26.3 hyphen (if seniority date follows) - information separator | ||
| + | 3.26.4 (optional) seniority date 12AUG82 date/ | ||
| + | Example: | ||
| + | .RG2/ | ||
| + | |||
| + | 3.27 .RN/ REMARKS CONTINUATION ELEMENT (See .R/ Remarks Element) | ||
| + | 32ND EDITION, JUNE 2012 841 Passenger Services Conference Resolutions Manual | ||
| + | 3.28 .S/ SECURITY INFORMATION ELEMENT This element lists a passenger' | ||
| + | As mentioned in Note 2 at the beginning of Section 3, unique continuation rules apply to this element. A Security Information Element | ||
| + | that is greater than the length of one message line is to be continued on the next line. Break the element at the 64th character. Enter the Element ID code of | ||
| + | .SN/ and continue the element data from where it was broken on the previous line. Multiple, successive .SN/ elements can be used for the continuation of one | ||
| + | .S/ Security Information Element. It is composed of the following information: | ||
| + | • Country (mandatory)—2 character ISO country code for which the security information applies. | ||
| + | • Security reference (conditional)—Per passenger, a unique security reference assigned to a passenger, as defined by individual governments' | ||
| + | • Security status code (conditional)—Status returned in the response from the specified governmental authority for a vetting request. | ||
| + | The vetting results will be passed as received from the government without any translation. The format is defined by individual governments. | ||
| + | • Infant indicator—to indicate an infant (not occupying a seat); passenger ID on this element is for the adult accompanying this infant. | ||
| + | • Free text (conditional). Once established, | ||
| + | The obliques between data components are mandatory, even when not populated. Construction Example Data Field Name | ||
| + | |||
| + | 3.28.1 element ID .S/ element ID | ||
| + | 3.28.2 ISO country code to which the security US aa information applies | ||
| + | 3.28.3 oblique / information separator | ||
| + | 3.28.4 security reference 8972657824 m[..25] 3.28.5 oblique / information separator | ||
| + | 3.28.6 security status code 2C m[..10] | ||
| + | 3.28.7 oblique / information separator | ||
| + | 3.28.8 infant indicator (not occupying seat) I I | ||
| + | 3.28.9 oblique / information separator | ||
| + | 3.28.10 free text FREE TEXT m[..999] | ||
| + | |||
| + | Note: Where the components of the .S/ Element are not provided, an oblique (/) is inserted to indicate an element is missing. | ||
| + | This is not allowed when no further components are provided. The Passenger Identification Element may follow the final element entered. | ||
| + | |||
| + | 3.28.11 passenger identification -1HOLTON/ | ||
| + | 3.28.12 element ID for Security Information .SN/ element ID continuation | ||
| + | 3.28.13 continuation of Security Information text MORE INFO free flow text | ||
| + | Examples: | ||
| + | .S/ | ||
| + | .S/ | ||
| + | .S/ | ||
| + | .S/ | ||
| + | .SN/ IFYING TRAVEL DOCUMENTS-1ZHANG/ | ||
| + | .SN/ SECURITY INFORMATION CONTINUATION ELEMENT (See .S/ Security Information Element) | ||
| + | |||
| + | 3.30 .T/ (RESERVED FOR ELECTRONIC TICKETING INFORMATION) Construction | ||
| + | Example Data Field Name | ||
| + | |||
| + | 3.30.1 element ID .T/ element ID 842 32ND EDITION, JUNE 2012 Recommended Practice 1707b | ||
| + | |||
| + | |||
| + | 3.31 .U/ | ||
| + | This element conveys a unique passenger system identifier for each flight segment. | ||
| + | The identifier is assigned by the sending system for purposes of data collection and statistical analysis. | ||
| + | It is composed of the following information: | ||
| + | |||
| + | • Unique passenger system identifier–a unique identifier is assigned to a passenger for each flight segment. | ||
| + | • Infant indicator–to indicate an infant (not occupying a seat); passenger ID on this element is for the adult accompanying this infant. | ||
| + | |||
| + | Once established, | ||
| + | 3.31.1 element ID .U/ element ID | ||
| + | 3.31.2 unique reference A98745632145678Z m[..25] | ||
| + | 3.31.3 oblique / information separator | ||
| + | 3.31.4 infant indicator I I | ||
| + | 3.31.5 passenger identification -1HOLTON/ | ||
| + | Examples: .U/ | ||
| + | |||
| + | 3.32 .V/ (NOT IN USE) | ||
| + | Construction Example Data Field Name 3.32.1 element ID .V/ element ID | ||
| + | |||
| + | 3.33 .W/ PIECES/ | ||
| + | Construction Example Data Field Name | ||
| + | |||
| + | 3.33.1 element ID .W/ element ID | ||
| + | 3.33.2 pieces/ | ||
| + | |||
| + | K = kilos | ||
| + | L = pounds | ||
| P = pieces only | P = pieces only | ||
pub/data_element_directory_for_dcs_passenger_messages.1587952456.txt.gz · Последнее изменение: 2020/04/27 01:54 — mmaxm