Инструменты пользователя

Инструменты сайта


pub:data_element_directory_for_dcs_passenger_messages

Различия

Здесь показаны различия между двумя версиями данной страницы.

Ссылка на это сравнение

pub:data_element_directory_for_dcs_passenger_messages [2019/10/31 12:53]
kov создано
pub:data_element_directory_for_dcs_passenger_messages [2019/10/31 13:00] (текущий)
kov
Строка 512: Строка 512:
 ====Section 3—DCS Elements at the Passenger Level==== ====Section 3—DCS Elements at the Passenger Level====
  
-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.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/​groups. Construction Example Data Field Name 3.3.1 element ID .BG/ element ID 3.3.2 pooling reference number 001 number/​three Example: .BG/001 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/​CARNAVAL/​TOUR/​ONE 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/AIR2000 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/one 3.6.3 oblique (if free text follows) / information separator 3.6.4 type of compensation USD200 free flow text Example: .DBC/​V/​USD200 PAID IN CASH .DBC/I/MCO GIVEN FOR DOMESTIC RT TRAVEL 3.7 .DG1/ FIRM DG PASSENGER ELEMENT Construction Example Data Field Name 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/​PSN49-08AUG91 3.8 .DG2/ SPACE AVAILABLE DG PASSENGER ELEMENT Construction Example Data Field Name 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 3.10 .F FREQUENT TRAVELLER ELEMENT Construction Example Data Field Name 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.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:​ flight SR559 flight fare class F fare class local date of inbound boarding point 07 date/day boarding point MUC airport code arrival point (conditional:​ mandatory when different from the departure point of the flight in the message being created; optional when the same) JFK airport code arrival time (conditional:​ mandatory if date variation is used; otherwise optional) /M1 date variation date variation (conditional:​ mandatory if arrival date of Inbound connection is different 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/​SR559F07MUC .I/​BA226Y09LHR1100 .I/​NZ040X27AKL0651/​M1HK 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/​F2-11JUN86 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 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/​ABC123/​JD .L/​222BBD/​NW .L/​QRS123/​KL (showing mandatory company designators when multiple .L/ Elements appear) 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:​ flight UA3517 flight fare class F fare class departure date 16 date/day origin FRA airport code destination JFK airport code departure time (optional) 1000 time reservations status (optional) HK status code Example: .M/​UA3517F16FRAJFK1000HK 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/​three 3.20.1.4 oblique (/) / information separator 3.20.1.5 final destination to which bag(s) are checked SFO airport code Example: .N/​0074123456005/​SFO 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/​Numeric 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/​KL123456/​5/​SFO 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:​ flight LH001 flight fare class F fare class local date of onward boarding point 26 date/day boarding point (conditional:​ 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:​ mandatory if date 0630 time variation exists; otherwise optional) date variation (conditional:​ mandatory if arrival date is different from departure date of the onward 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) KL status Example: .O/​BA012C26LHR1500HK .O2/​NW001C27JFK1400HK .O3/​AA123Y27ATL .O/​CO0964Y15NRTGUM20500125/​1HK .O2/​CO0002Y16GUMHNL06301755/​M1HK .O/​NZ0038Y29LHRAKL21050900/​2HK 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/​status code and number KK1 status code HK3 number/​one-to-three 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/​SAMDR passenger identification 1707b, paragraph 3.37 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/​MARKMR/​MARYMRS .L/765Y78 .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/​POSSIBLE TO ASSIST. WILL BE MET BY PRIVATE AMBULANCE .RN/ON ARRIVAL-1HARTSHORNE/​MARKMR .R/VGML NN1-1HARTSHORNE/​MARYMRS 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/full Example: .RG1/​PSN68-12AUG82 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/full Example: .RG2/​PSN68-12AUG82 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'​s security information as related to a particular country. 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'​ requirements. • 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 security reference will be used in any communication with the specified government. 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/​TOMMR passenger ID 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/​US/​8972657824/​2C/​I/​INFANT WITH FATHER-1HOLTON/​TOMMR .S/​US/​123454321-1SMITH/​JOHNMR .S/​US/​9757326734 .S/​US/​1234567922/​11//​CALL GOVERNMENT AUTHORITY AFTER VER .SN/ IFYING TRAVEL DOCUMENTS-1ZHANG/​BIN 3.29 .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+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.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/​groups. Construction Example Data Field Name 3.3.1 element ID .BG/ element ID 3.3.2 pooling reference number 001 number/​three Example: .BG/001 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/​CARNAVAL/​TOUR/​ONE 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/AIR2000 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/one 3.6.3 oblique (if free text follows) / information separator 3.6.4 type of compensation USD200 free flow text Example: .DBC/​V/​USD200 PAID IN CASH .DBC/I/MCO GIVEN FOR DOMESTIC RT TRAVEL 3.7 .DG1/ FIRM DG PASSENGER ELEMENT Construction Example Data Field Name 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/​PSN49-08AUG91 3.8 .DG2/ SPACE AVAILABLE DG PASSENGER ELEMENT Construction Example Data Field Name 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 3.10 .F FREQUENT TRAVELLER ELEMENT Construction Example Data Field Name 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.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:​ flight SR559 flight fare class F fare class local date of inbound boarding point 07 date/day boarding point MUC airport code arrival point (conditional:​ mandatory when different from the departure point of the flight in the message being created; optional when the same) JFK airport code arrival time (conditional:​ mandatory if date variation is used; otherwise optional) /M1 date variation date variation (conditional:​ mandatory if arrival date of Inbound connection is different 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/​SR559F07MUC .I/​BA226Y09LHR1100 .I/​NZ040X27AKL0651/​M1HK 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/​F2-11JUN86 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 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/​ABC123/​JD .L/​222BBD/​NW .L/​QRS123/​KL (showing mandatory company designators when multiple .L/ Elements appear) 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:​ flight UA3517 flight fare class F fare class departure date 16 date/day origin FRA airport code destination JFK airport code departure time (optional) 1000 time reservations status (optional) HK status code Example: .M/​UA3517F16FRAJFK1000HK 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/​three 3.20.1.4 oblique (/) / information separator 3.20.1.5 final destination to which bag(s) are checked SFO airport code Example: .N/​0074123456005/​SFO 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/​Numeric 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/​KL123456/​5/​SFO 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:​ flight LH001 flight fare class F fare class local date of onward boarding point 26 date/day boarding point (conditional:​ 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:​ mandatory if date 0630 time variation exists; otherwise optional) date variation (conditional:​ mandatory if arrival date is different from departure date of the onward 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) KL status Example: .O/​BA012C26LHR1500HK .O2/​NW001C27JFK1400HK .O3/​AA123Y27ATL .O/​CO0964Y15NRTGUM20500125/​1HK .O2/​CO0002Y16GUMHNL06301755/​M1HK .O/​NZ0038Y29LHRAKL21050900/​2HK 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/​status code and number KK1 status code HK3 number/​one-to-three 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/​SAMDR passenger identification 1707b, paragraph 3.37 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/​MARKMR/​MARYMRS .L/765Y78 .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/​POSSIBLE TO ASSIST. WILL BE MET BY PRIVATE AMBULANCE .RN/ON ARRIVAL-1HARTSHORNE/​MARKMR .R/VGML NN1-1HARTSHORNE/​MARYMRS 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/full Example: .RG1/​PSN68-12AUG82 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/full Example: .RG2/​PSN68-12AUG82 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'​s security information as related to a particular country. 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'​ requirements. • 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 security reference will be used in any communication with the specified government. 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/​TOMMR passenger ID 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/​US/​8972657824/​2C/​I/​INFANT WITH FATHER-1HOLTON/​TOMMR .S/​US/​123454321-1SMITH/​JOHNMR .S/​US/​9757326734 .S/​US/​1234567922/​11//​CALL GOVERNMENT AUTHORITY AFTER VER .SN/ IFYING TRAVEL DOCUMENTS-1ZHANG/​BIN 3.29 .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/​PASSENGER SYSTEM IDENTIFIER PER SEGMENT (bilateral agreement)** 
  
-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,​ this unique reference will be the key to identify the passenger Construction Example Data Field Name 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/​TOMMR passenger ID Examples: .U/​A456789A56478 .U/​B12345698Z765889Q/​I-1MONCEL/​MARC+**3.31 .U/PASSENGER SYSTEM IDENTIFIER PER SEGMENT (bilateral agreement)**\\
  
-**3.32 .V/ (NOT IN USE)** 
  
-Construction Example Data Field Name 3.32.1 element ID .V/ element ID+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,​ this unique reference will be the key to identify the passenger ​Construction Example Data Field Name 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/​TOMMR passenger ID Examples: .U/​A456789A56478 .U/​B12345698Z765889Q/​I-1MONCEL/​MARC\\
  
-**3.33 .W/ PIECES/​WEIGHT DATA ELEMENT** 
  
-3.33 .WPIECES/​WEIGHT DATA ELEMENT+**3.32 .V(NOT IN USE)**\\
  
-Construction Example Data Field Name 
  
-3.33.1 element ID .W/ element ID+Construction Example Data Field Name 3.32.1 element ID .V/ element ID\\
  
-3.33.2 pieces/​weight indicator K pieces/​weight indicator 
  
-K = kilos+**3.33 .W/ PIECES/​WEIGHT DATA ELEMENT**\\
  
-L = pounds 
  
-P = pieces only+3.33 .W/ PIECES/​WEIGHT DATA ELEMENT\\
  
-3.33.3 oblique / information separator 
  
-3.33.4 number of checked baggage 3 number/​one-to-three+Construction Example Data Field Name\\
  
-(this field is mandatory) 
  
-3.33.5 oblique (if weight follows) ​information separator+3.33.1 element ID .Welement ID\\
  
-3.33.6 checked baggage weight 33 weight 
  
-(not to be used with P)+3.33.2 pieces/​weight indicator K pieces/​weight indicator\\
  
-3.33.7 oblique (if weight follows) / information separator 
  
-3.33.8 unchecked (hand carried) weight 5 number/​one-to-three+K = kilos\\
  
-(optional for K and L; not to be used with P) 
  
-Examples:+L = pounds\\
  
-.W/L/2/45 
  
-.W/P/3+= pieces only\\
  
-.W/K/1/17/5 
  
-.W/K/0/0/7+3.33.3 oblique ​information separator\\
  
-**3.34 .WL/ REVENUE PASSENGER ON WAITLIST ELEMENT** 
  
-Construction Example Data Field Name 3.34.1 element ID .WL/ element ID 3.34.2 priority code AB84 priority designator Example: .WL/AB84+3.33.4 number of checked baggage ​number/one-to-three\\
  
-**3.35 .X/ (NOT IN USE)** 
  
-Construction Example Data Field Name 3.35.1 element ID .X/ element ID+(this field is mandatory)\\
  
-**3.36 .Y/ (NOT IN USE)** 
  
-Construction Example Data Field Name 3.36.1 element ID .Yelement ID+3.33.5 oblique (if weight follows) ​information separator\\
  
-**3.37 .Z/ (NOT IN USE)** 
  
-Construction Example Data Field Name 3.37.1 element ID .Z/ element ID+3.33.6 checked baggage weight 33 weight\\ 
 + 
 + 
 +(not to be used with P)\\ 
 + 
 + 
 +3.33.7 oblique (if weight follows) / information separator\\ 
 + 
 + 
 +3.33.8 unchecked (hand carried) weight 5 number/​one-to-three\\ 
 + 
 + 
 +(optional for K and L; not to be used with P)\\ 
 + 
 + 
 +Examples:​\\ 
 + 
 + 
 +.W/​L/​2/​45\\ 
 + 
 + 
 +.W/P/3\\ 
 + 
 + 
 +.W/​K/​1/​17/​5\\ 
 + 
 + 
 +.W/​K/​0/​0/​7\\ 
 + 
 + 
 +**3.34 .WL/ REVENUE PASSENGER ON WAITLIST ELEMENT**\\ 
 + 
 + 
 +Construction Example Data Field Name 3.34.1 element ID .WL/ element ID 3.34.2 priority code AB84 priority designator Example: .WL/​AB84\\ 
 + 
 + 
 +**3.35 .X/ (NOT IN USE)**\\ 
 + 
 + 
 +Construction Example Data Field Name 3.35.1 element ID .X/ element ID\\ 
 + 
 + 
 +**3.36 .Y/ (NOT IN USE)**\\ 
 + 
 + 
 +Construction Example Data Field Name 3.36.1 element ID .Y/ element ID\\ 
 + 
 + 
 +**3.37 .Z/ (NOT IN USE)**\\ 
 + 
 + 
 +Construction Example Data Field Name 3.37.1 element ID .Z/ element ID\\ 
 + 
 + 
 +**3.38 PASSENGER IDENTIFICATION (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/​A/​B/​C or 1JONES/D), the passenger ID element is optional. • 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/​AMR/​BMRS). • A passenger identification element can appear only once per element, as shown in the examples below. Construction Example Data Field Name 3.38.1 applicable passenger name(s) -1COTE/​DIANEMS passenger identification (ID) Examples: The PNR holds The DCS message entry is One passenger: Passenger ID is optional: 1FOX/ABEMR 1FOX/ABEMR .R/FQTV AI 43211 (with an SSR FQTV for Mr. A. Fox) or 1FOX/ABEMR .R/FQTV AI 43211-1FOX/​ABEMR The PNR holds The DCS message entry is Multiple passengers with multiple surnames: Elements with and without passenger ID: 3BAKER/​HUGHMR/​JANEMRS/​BOBMR 3BAKER/​HUGHMR/​JANEMRS/​BOBMR-D4 (with an SSR FQTV for only Mrs. Baker) .L/​87Y344/​AI .R/FQTV JD 98765432-1BAKER/​JANEMRS 1UPTON/​TINAMRS 1UPTON/​TINAMRS-D4 .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/​WILMMR/​HELENMRS/​JANEMS 3DAHL/​WILMR/​HELENMRS/​JANEMS (with an SSR VGML for all three of the DAHLs, plus .L/​223H45/​AY .R/VGML HK3 an SSR BIKE for Mrs. DAHL and for Ms. DAHL) .R/BIKE HK2-2DAHL/​HELENMRS/​JANEMS 844 32ND EDITION, JUNE 2012 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,​ and address information. These are the RES elements of SSR DOCS, SSR DOCO, and SSR DOCA. In reservations message construction rules, all data fields in the body of these SSR elements are ‘optional’—meaning that they should appear in messages if they are present in the PNR. 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/​status code and the number 1 HK1 status code 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/​state US country code 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/​THOMAS passenger ID Example showing a DOCS for an adult male, with a continuation element: .R/DOCS HK1/​I/​US/​D23145890/​US/​12JUL64/​M/​12JUL04/​STEVENSON/​THOM .RN/​AS/​RICHARD-1STEVENSON/​THOMASMR 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/​P/​CA/​939822373/​HK/​08MAR82/​F/​31JUL12/​LIU/​JANE/​LIN/​H-1LIU/​JANEMS .R/DOCS HK1/​P/​CA/​939822373/​HK/​21FEB08/​FI/​31JUL12/​LIU/​MILLY/​KAI-1LIU/​JANEMS 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/​status code and the number 1 HK1 status code 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/full 3.40.2.15 oblique / information separator 3.40.2.16 country/​state for which visa is applicable US country code 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/​MARYMRS passenger ID Examples: .R/DOCO HK1/AMBER HILL GBR-1BROSNAN/​JAMES .R/DOCO HK1/BREMEN DEU////​12JUL06-1KAISER/​HARALD 846 32ND EDITION, JUNE 2012 Recommended Practice 1707b 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/​status code HK status code 3.40.3.5 number of passengers to whom the element applies 2 number/​one-to-three 3.40.3.6 oblique / information separator 3.40.3.7 type of address: D-Destination,​ R-Residence R a 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/​province/​county TX a(..35) 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/​LEAHMRS passenger ID Example: .R/DOCA HK1/​R/​US/​1600 SMITH STREET/​HOUSTON/​TX/​77001-1BREKKE/​LEAHMRS .R/DOCA HK1/​D/​US/​HOLIDAY INN/​HOUSTON-1DRYER/​DAVIDMR .R/DOCA HK3/R/CH/33 ROUTE DE LAEROPORT/​GENEVA/​SWITZERLAND/​15 Passenger Identification is optional on a passenger element entry. • If the element applies to all passengers in a family name (such as 3SMITH/​A/​B/​C or 1JONES/D), the passenger ID element is optional. • 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/​AMR/​BMRS). • A passenger identification element can appear only once per element, as shown in the examples below. Construction Example Data Field Name 3.38.1 applicable passenger name(s) -1COTE/​DIANEMS passenger identification (ID) Examples: The PNR holds The DCS message entry is One passenger: Passenger ID is optional: 1FOX/ABEMR 1FOX/ABEMR .R/FQTV AI 43211 (with an SSR FQTV for Mr. A. Fox) or 1FOX/ABEMR .R/FQTV AI 43211-1FOX/​ABEMR The PNR holds The DCS message entry is Multiple passengers with multiple surnames: Elements with and without passenger ID: 3BAKER/​HUGHMR/​JANEMRS/​BOBMR 3BAKER/​HUGHMR/​JANEMRS/​BOBMR-D4 (with an SSR FQTV for only Mrs. Baker) .L/​87Y344/​AI .R/FQTV JD 98765432-1BAKER/​JANEMRS 1UPTON/​TINAMRS 1UPTON/​TINAMRS-D4 .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/​WILMMR/​HELENMRS/​JANEMS 3DAHL/​WILMR/​HELENMRS/​JANEMS (with an SSR VGML for all three of the DAHLs, plus .L/​223H45/​AY .R/VGML HK3 an SSR BIKE for Mrs. DAHL and for Ms. DAHL) .R/BIKE HK2-2DAHL/​HELENMRS/​JANEMS 844 32ND EDITION, JUNE 2012 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,​ and address information. These are the RES elements of SSR DOCS, SSR DOCO, and SSR DOCA. In reservations message construction rules, all data fields in the body of these SSR elements are ‘optional’—meaning that they should appear in messages if they are present in the PNR. 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/​status code and the number 1 HK1 status code 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/​state US country code 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/​THOMAS passenger ID Example showing a DOCS for an adult male, with a continuation element: .R/DOCS HK1/​I/​US/​D23145890/​US/​12JUL64/​M/​12JUL04/​STEVENSON/​THOM .RN/​AS/​RICHARD-1STEVENSON/​THOMASMR 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/​P/​CA/​939822373/​HK/​08MAR82/​F/​31JUL12/​LIU/​JANE/​LIN/​H-1LIU/​JANEMS .R/DOCS HK1/​P/​CA/​939822373/​HK/​21FEB08/​FI/​31JUL12/​LIU/​MILLY/​KAI-1LIU/​JANEMS 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/​status code and the number 1 HK1 status code 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/full 3.40.2.15 oblique / information separator 3.40.2.16 country/​state for which visa is applicable US country code 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/​MARYMRS passenger ID Examples: .R/DOCO HK1/AMBER HILL GBR-1BROSNAN/​JAMES .R/DOCO HK1/BREMEN DEU////​12JUL06-1KAISER/​HARALD 846 32ND EDITION, JUNE 2012 Recommended Practice 1707b 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/​status code HK status code 3.40.3.5 number of passengers to whom the element applies 2 number/​one-to-three 3.40.3.6 oblique / information separator 3.40.3.7 type of address: D-Destination,​ R-Residence R a 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/​province/​county TX a(..35) 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/​LEAHMRS passenger ID Example: .R/DOCA HK1/​R/​US/​1600 SMITH STREET/​HOUSTON/​TX/​77001-1BREKKE/​LEAHMRS .R/DOCA HK1/​D/​US/​HOLIDAY INN/​HOUSTON-1DRYER/​DAVIDMR .R/DOCA HK3/R/CH/33 ROUTE DE LAEROPORT/​GENEVA/​SWITZERLAND/​15
pub/data_element_directory_for_dcs_passenger_messages.txt · Последние изменения: 2019/10/31 13:00 — kov