Appendix - SSR

Owned by Natalia Pacheco (Deactivated)
May 08, 2019


1.  Introduction


The SSR (Special Service Requirements) are additional elements that can be associated to a passenger or a booking, they are used to request a special service on which the airline needs to take an action. SSRs can be included on the KIU_AirBookRQ method inside the attribute SpecialReqDetails:

Example
<?xml version="1.0" encoding="UTF-8"?>
<KIU_AirBookRQ EchoToken="1" TimeStamp="2013-01-25T18:40:47+00:00" Target="Testing" Version="3.0" SequenceNmbr="1" PrimaryLangID="en-us">
   <POS>
      <Source AgentSine="NET00XXWW" PseudoCityCode="NET" ISOCountry="AR" ISOCurrency="ARS" TerminalID="NET00XX000">
         <RequestorID Type="5" />
         <BookingChannel Type="1" />
      </Source>
   </POS>
   <AirItinerary>
      <OriginDestinationOptions>
         <OriginDestinationOption>
            <FlightSegment DepartureDateTime="2013-07-15 14:30:00" ArrivalDateTime="2013-07-15 14:45:00" FlightNumber="3130" ResBookDesigCode="Y" RPH="01">
               <DepartureAirport LocationCode="AEP" />
               <ArrivalAirport LocationCode="COR" />
               <MarketingAirline Code="XX" />
            </FlightSegment>
         </OriginDestinationOption>
      </OriginDestinationOptions>
   </AirItinerary>
   <TravelerInfo>
      <AirTraveler PassengerTypeCode="ADT">
         <PersonName>
            <GivenName>JUAN</GivenName>
            <Surname>PEREZ</Surname>
         </PersonName>
         <Telephone PhoneNumber="123456789" />
         <Email>JUAN@PEREZ.COM</Email>
         <Document DocID="123456789" DocType="NI" />
         <TravelerRefNumber RPH="01" />
      </AirTraveler>
      <SpecialReqDetails>
         <SpecialServiceRequests>
            <SpecialServiceRequest ServiceQuantity="1" SSRCode="AVIH" Status="NN" TravelerRefNumberRPHList="01">
               <Airline Code="XX" />
               <FlightLeg Date="2013-07-15" FlightNumber="3130" ResBookDesigCode="Y">
                  <DepartureAirport LocationCode="AEP" />
                  <ArrivalAirport LocationCode="COR" />
               </FlightLeg>
               <Text>TRAVELS WITH A PET</Text>
            </SpecialServiceRequest>
         </SpecialServiceRequests>
      </SpecialReqDetails>
   </TravelerInfo>
   <Ticketing TicketTimeLimit="4" />
</KIU_AirBookRQ>


SSR can be “confirmed”, “rejected”, or “required” when requested on a booking. They can also depend on the airline’s inventory, according to their settings. (For example, on Infant passengers: if the airline has setted a maximum amount of infant passengers per flight, when an SSR for an infant is requested on a flight it can be confirmed if the amount configured has not been reached, or if it has reached their capacity, It can be rejected.)


Also, SSR can be determined to response on each case:


  •  If only a pax is requested per service
  •  theres a specific amount of special services requested
  •  If it requires an action code (HK o NN)
  •  If it requires a carrier or company code.
  • If it will allow an SSR / Passenger/ Carrier / Itinerary duplicity.
  • If it will allow only one service per request
  • If it will always be confirmed
  • If it will allow to add the carrier YY (thus including all airlines on the itinerary)
  • If it will allow to show the amount of requested services after the SSR Status
  • If it will allow setting from the airline
  • Free text: Mandatory, not allowed, or opcional
  • Linked itinerary: required, not allowed, or optional


2.  Categories

 

Each SSR belongs to a precise category. Those categories are ARPT, BAGG, FFDA, MEAL, MEDC, OTHR y STND. Next we will show the diferents SSRs and their corresponding categories.


2.1       ARPT (Airport)

 

2.1.1    AVIH: animal in hold


References:


  • It can be associated to more the one passenger per service
  • Requires free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Does not requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Does not always confirm
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example
<?xml version="1.0" encoding="UTF-8"?>
<KIU_AirBookRQ EchoToken="1" TimeStamp="2013-01-25T18:40:47+00:00" Target="Testing" Version="3.0" SequenceNmbr="1" PrimaryLangID="en-us">
   <POS>
      <Source AgentSine="NET00XXWW" PseudoCityCode="NET" ISOCountry="AR" ISOCurrency="ARS" TerminalID="NET00XX000">
         <RequestorID Type="5" />
         <BookingChannel Type="1" />
      </Source>
   </POS>
   <AirItinerary>
      <OriginDestinationOptions>
         <OriginDestinationOption>
            <FlightSegment DepartureDateTime="2013-07-15 14:30:00" ArrivalDateTime="2013-07-15 14:45:00" FlightNumber="3130" ResBookDesigCode="Y" RPH="01">
               <DepartureAirport LocationCode="AEP" />
               <ArrivalAirport LocationCode="COR" />
               <MarketingAirline Code="XX" />
            </FlightSegment>
         </OriginDestinationOption>
      </OriginDestinationOptions>
   </AirItinerary>
   <TravelerInfo>
      <AirTraveler PassengerTypeCode="ADT">
         <PersonName>
            <GivenName>JUAN</GivenName>
            <Surname>PEREZ</Surname>
         </PersonName>
         <Telephone PhoneNumber="123456789" />
         <Email>JUAN@PEREZ.COM</Email>
         <Document DocID="123456789" DocType="NI" />
         <TravelerRefNumber RPH="01" />
      </AirTraveler>
      <SpecialReqDetails>
         <SpecialServiceRequests>
            <SpecialServiceRequest ServiceQuantity="1" SSRCode="AVIH" Status="NN" TravelerRefNumberRPHList="01">
               <Airline Code="XX" />
               <FlightLeg Date="2013-07-15" FlightNumber="3130" ResBookDesigCode="Y">
                  <DepartureAirport LocationCode="AEP" />
                  <ArrivalAirport LocationCode="COR" />
               </FlightLeg>
               <Text>TRAVELS WITH A PET</Text>
            </SpecialServiceRequest>
         </SpecialServiceRequests>
      </SpecialReqDetails>
   </TravelerInfo>
   <Ticketing TicketTimeLimit="4" />
</KIU_AirBookRQ>


 

2.1.2    DEPA: deportee – accompanied by an escort


References:


  • Should be associated only to one pax per service
  • Optional free text
  • Does not require the amount of requested services
  • Requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


Example
<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DEPA" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX DEPORTED TRAVELS ESCORTED </Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



2.1.3    DEPU: deportee – unaccompanied


References:


  • Should be associated only to one pax per service
  • Optional free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.



Example:


Example
<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DEPU" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX DEPORTED TRAVELS UNESCORTED </Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.1.4    EXST: extra seat

References:


  • Should be associated only to one pax per service
  • Requires free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires associated itinerary
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.



Example:


Example
<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="EXST" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX SOLICITA ASIENTO EXTRA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.1.5    MAAS: meet and assist


References:


  • It can be associated to more the one passenger per servicer
  • Requires free text
  • Does not require the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="MAAS" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX REQUIERE ASISTENCIA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.1.6    PETC: animal in cabin

References:

  • It can be associated to more the one passenger per service
  • Requires free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Does not always confirm
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="PETC" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX VIAJA CON MASCOTA EN CABINA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.1.7    UMNR: unaccompanied minor

References:


  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to input the carrier YY
  • Will allow to be configured by the airline


Note: the field <Text> requires a specific format: UM follow by the age numer of the unaccompanied minor.

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="UMNR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>UM8</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.2       BAGG (Baggage) 

2.2.1    BIKE: bicycle

References:

  • It can be associated to more the one passenger per service
  • Optional free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • requiere itinerario asociado
  • Does not requires an itinerary associated
  • Allows more than one service by request
  • Does not always confirm
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="BIKE" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX VIAJA CON BICICLETA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.2.2    CBBG: cabin baggage

References:


  • It can be associated to more the one passenger per service
  • Requires free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Does not requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

  

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="CBBG" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX VIAJA CON EQUIPAJE EN CABINA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.2.3    SPEQ: sports equipment

References:


  • It can be associated to more the one passenger per service
  • Requires free text
  • Requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.



Example: 



<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="SPEQ" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX VIAJA CON EQUIPO DEPORTIVO</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



2.3       MEAL (Meals) 

2.3.1    BBML: baby meal


References:


  • It can be associated to more the one passenger per service
  • Does not requires free text
  • Does not require the amount of requested services
  • Requires code of action
  • Does not requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note: The SSR BBML does not require free text, therefore the field  <Text> can go empty or not be included on the request call.


Example with the field <Text>:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="BBML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text></Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


Example without the field <Text>:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="BBML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.3.2    CHML: child meal

References:


  • It can be associated to more the one passenger per service
  • Optional free text
  • Does not require the amount of requested services
  • Requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="CHML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX REQUEST CHILDREN MEAL</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.3.3    SPML: special meal

References:


  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="SPML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-20" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX REQUEST UNSALTED MEAL</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.3.4    VGML: vegetarian vegan meal

References:


  • It can be associated to more the one passenger per service
  • Does not requires free text
  • Does not requires the amount of requested services
  • Requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always gets confirmed
  • Shows the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces. Plus this SSR does not requires free text, therefore the field <Text> can be empty or not be included on the method call.



Example with the field <Text>:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="VGML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX REQUESTED VEGETARIAN MEAL</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



Example without the field <Text>:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="VGML" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.4       FFDA (Frequent Flyer Data)

 

On the three cases for this category (FQTR, FQTU y FQTV) it should be left out the element <FlightLeg> since this SSR will not require any segment association.


The format to input the information on the field <Text> es:


<Text>XX/54224445550.PREMIUM</Text>


XX  Airline code who owns the frequent flyer program (where the passenger will collect the points, miles or kilometers obtained). The information  regarding the airline code that operates the flight on the field <Airline Code>

 / divisor

54224445550 Frequent flyers number (allows up to 22 alphanumberic characters, including the divisor, category or tier are optionals)

. divisor (optional)

PREMIUM category or tier (optional free text) 

2.4.1    FQTR: frequent traveller award redemption journey

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Will not show the amount of requested services after the SSR status
  • Will not  allow to add the carrier YY
  • Will not allow to be configured by the airline


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


Example including category (tier):

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550.PREMIUM</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.4.2    FQTU: frequent traveller req. redemption for upgrade

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Will not show the amount of requested services after the SSR status
  • Will not  allow to add the carrier YY
  • Will not allow to be configured by the airline

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTU" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


Example including category (tier):


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTU" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550.PREMIUM</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.4.3    FQTV: frequent traveller mileage program information

 

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Will not show the amount of requested services after the SSR status
  • Will not  allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTV" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


Example incluind category (tier):


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FQTV" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>XX/54224445550.PREMIUM</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5       STND (Standard)

 

2.5.1    ADTK: advise if ticketed

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Will show the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="ADTK" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-21" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>VENCIMIENTO 1800/30JUN</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.2    CHLD: child

References:

  • It can be associated to more the one passenger per service
  • Optional free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Does not requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

Note: On the field text <Text> you must add the birthdate on the following format DDMMMAA (example: 19JAN07) or DDMMMAAAA (example: 19JAN2007). On the other hand it should be left out the element <FlightLeg> since the SSR CHLD does not required segment association.

 

Example on DDMMMAA:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="CHLD" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>19JAN07</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


Example on DDMMMAAA:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="CHLD" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>19JAN2007</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>

 

2.5.3    CKIN: provides information for airport personnel

References:

  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not requires carrier
  • An itinerary associated is optional
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="CKIN" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-21" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX VIP</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.4    DOCA: API – passenger address information

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not require carrier
  • An itinerary associated is optional
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline


Note: the information included on the field <Text> must be the following:


<Type of address: D=destination, R=residence>/<address country >/<address>/<city>/<state, province o country>/<zip code>/<infant indicator>

 

For more information, please verify the SSR DOCx: http://kiusys.com/docs/host/SSR%20DOCx%20-%20Especificacion_v4.pdf


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DOCA" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-21" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>R/AR/AV RAMON DANTE 429/BUE/AR/1001</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.5    DOCO: API – passenger other supplementary information (información suplementaria del pasajero)

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not require carrier
  • An itinerary associated is optional
  • Allows SSR, pax, carrier, and/or itinerary duplicity
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note: The information included on the field <Text> should be the following:


<birth country>/<typo of document>/<document number>/<Issue country>/<Date of issue>/<Valid country>/<infant indicator>

 

For more information, please verify the SSR DOCx: http://kiusys.com/docs/host/SSR%20DOCx%20-%20Especificacion_v4.pdf


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DOCO" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-21" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>AR/V/123456789/AR/19JAN12/AR</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.6    DOCS: API – passenger travel document information


References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested service
  • Does not requires code of action
  • Requires carrier
  • An itinerary associated is optional
  • Allows SSR, pax, carrier, and/or itinerary duplicity
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note: The information included on the field <Text> should be the following:


<document type>/<state or country of the document>/<document number>/<nationality (country code)>/<date of birth (format: DDMMMYY)>/<gender>/<documents expiration date>/<last name>/<name>{/middle name}{/Passport holder}

 

For more information, please verify the SSR DOCx: http://kiusys.com/docs/host/SSR%20DOCx%20-%20Especificacion_v4.pdf


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DOCS" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-21" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>I/AR/12345678/AR/19JAN79/M/19JAN15/PEREZ/JOSE</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.7    FOID: form of identification

References:


  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Does not requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

Note: It must leave out the element <FlightLeg> since the SSR FOID does not require any segment association.


The information included on the field <Text> should be the following:


<Text><type of document><document number></Text>


Considerations:


  • The type of document can be PP (passport), NI (national identity card) or ID (Locally defined Identification)
  • The document number can contain up to 25 alphanumeric characters (without including the previous type of document)


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="FOID" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>NI123456789ABC</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.8    INFT: infant

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Does not always confirm
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note: in the field <Text> you must add the last name/name of the infant passenger and the date of birth on the following format DDMMMYY (example: 19JAN07)


Example:

 


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="INFT" Status="NN" TravelerRefNumberRPHList="03">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PEDRO/PEREZ20SEP12</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



2.5.9    LANG: specify language(s) spoken


References:

  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not require carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="LANG" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX SPEAKS SPANISH ONLY</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.10 OTHS: other service not listed with its own SSR code

References:

  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not require carrier
  • an itinerary associated its optional
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="OTHS" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX SOLICITA UBICACION SALIDA DE EMERGENCIA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.11 PCTC: passenger provided contact information

References:

  • It can be associated to more the one passenger per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Does not require carrier
  • Does not requires an itinerary associated
  • Allows SSR, pax, carrier, and/or itinerary duplicity.
  • Allows more than one service by request
  • Will confirm always
  • Will not show the amount of requested services after the SSR status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note: It must leave out the element <FlightLeg> since the SSR PCTC does not require any segment association.


The information included on the field <Text> should be the following:


<Text>MARIANA/AR 54222444.WIFE</Text>


MARIANA Contact name (Allows a maximum of 25 alphanumeric characters)

 / divisor

AR country code (up to a max. of  two alphanumeric characters)

54222444 contact phone number(up to a max. of twenty-three alphanumeric characters)

. divisor (optional)

WIFE free text (optional, allows up to twenty-five alphanumeric characters and spaces)

 

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="PCTC" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<Text>MARIANA/AR 54222444.WIFE</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.12 RLOC: record locator

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="RLOC" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>ABCDEF</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.5.13 TKNE: ticket number for electronic tickets

References:

  • Should be associated only to one pax per service
  • Requires free text
  • Does not require the amount of requested services
  • Does not requires code of action
  • Requires carrier      
  • Requires an itinerary associated
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.
  • Allows only one service per request
  • Will confirm always
  • Shows the amount of services requested after the SSR Status
  • Will allow to add the carrier YY
  • Will not allow to be configured by the airline

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="TKNE" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="123" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>666000123456</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>

 

2.6       MEDC (Medical Cases)

 

2.6.1    AOXY: airline supplied oxygen

References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows more than one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="AOXY" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>SUPPLY OXIGEN</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.6.2    BLND: blind passenger


References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Does not requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows more than one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="BLND" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-22" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>BLIND PASSENGER</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>

2.6.3    DEAF: deaf passenger

References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Does not requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows more than one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="DEAF" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX HIPOACUSICO</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>

2.6.4    MEDA: medical case

References:


  • It can be associated to more the one passenger per service
  • free text is required
  • Does not requires the amount of requested services  
  • Does not requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Allows SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows more than one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:


<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="MEDA" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX CON MARCAPASOS</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.6.5    POXY: passenger own oxygen

References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows only one service by request      
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:



<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="POXY" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PASAJERO POSEE OXIGENO PROPIO</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



2.6.6    STCR: stretcher passenger

References:

  • It can be associated to more the one passenger per service
  • free text is not required
  • Does not requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier           
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows only one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     


Nota: el SSR STCR  does not requires free text, therefore the field  <Text> can go empty or not be included on the method call.


Example with text  <Text>:



<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="STCR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text></Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



Example without the text  <Text>:



<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="STCR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-09-20" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>



 

2.6.7    WCHC: wheelchair for cabin seat


References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows only one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.

Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="WCHC" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX WILL BE IN WHEELCHAIR TO THE CABIN</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.6.8    WCHR: wheelchair for ramp

References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Does not requires the amount of requested services  
  • Requires code of action   
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows only one service by request     
  • Does not always confirm    
  • Shows the amount of services requested after the SSR Status       
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     

 

Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="WCHR" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX SOLICITA SILLA DE RUEDAS EN RAMPA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


2.6.9    WCHS: wheelchair for steps

References:

  • It can be associated to more the one passenger per service
  • free text is optional 
  • Does not requires the amount of requested services  
  • Requires code of action  
  • Does not requires carrier            
  • Requires an itinerary associated     
  • Does not allow SSR, pax, carrier, and/or itinerary duplicity.   
  • Allows only one service by request     
  • Does not always confirm    
  • muestra la cantidad de servicios solicitados luego del status del SSR
  • Will allow to add the carrier YY
  • Will allow to be configured by the airline     


Note : This SSR will allow a maximum amount of one hundred and twenty seven (127) special characters(“/”, “-” y “.”), alphanumeric and spaces.


Example:

<SpecialReqDetails>
<SpecialServiceRequests>
<SpecialServiceRequest ServiceQuantity="1" SSRCode="WCHS" Status="NN" TravelerRefNumberRPHList="01">
<Airline Code="XX" />
<FlightLeg Date="2013-08-23" FlightNumber="666" ResBookDesigCode="Y" >
<DepartureAirport LocationCode="AEP"/>
<ArrivalAirport LocationCode="COR"/>
</FlightLeg>
<Text>PAX SOLICITA SILLA DE RUEDAS EN ESCALERA</Text>
</SpecialServiceRequest>
</SpecialServiceRequests>
</SpecialReqDetails>


3.  Common mistakes

 

3.1    When adding an unexistant SSR code or a wrong one:


              <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="BIQE" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-10-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID SSR CODE" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)


 

3.2   Requesting an SSR with confirm status (HK) when is not allowed to:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="WCHS" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-10-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="ONLY STATUS NN IS PERMITTED" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)

 

3.3   When adding an SSR code not supported or allowed:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="VGML" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-10-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="SSR NOT SUPPORTED BY CARRIER" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)

 

3.4   When adding an SSR without the standar format:


              <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="UMNR" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID FORMAT - CHECK 4UMNR/HELP" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>

The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)

 

 

3.5   Adding a text when the SSR does not permit it:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="BBML" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="FREE TEXT NOT ALLOWED" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)


3.6   When adding the field <FlightLeg> when the SSR does not allow segment association:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="CHLD" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="SEGMENT ASSOCIATION IS NOT PERMITTED" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>

 

3.7   When adding an invalid carrier on the field <Text> (FQTR):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="FQTR" Status="UC" DepartureAirport="" ArrivalAirport="" FlightNumber="" RecordBookDesignator="" Date="" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="CHECK CARRIER" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>

 

3.8   When adding more characters than allowed on the field <Text>, wether on the mandatory fields as in the optional (FQTR):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="FQTR" Status="UC" DepartureAirport="" ArrivalAirport="" FlightNumber="" RecordBookDesignator="" Date="" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID FORMAT - CHECK 4FQTR/HELP OR SRFQTR/HELP" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


In both cases, the booking is created, but the SSR status on the PNR is UC (“unable to confirm”)

 

3.9   Adding an invalid date of birth (CHLD):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="CHLD" Status="UC" DepartureAirport="" ArrivalAirport="" FlightNumber="" RecordBookDesignator="" Date="" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID DATE OF BIRTH" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


The booking is created, but the SSR status on the PNR is UC (“unable to confirm”)

 

3.10         When adding invalid informationl (DOCA, DOCO, DOCS):

 

3.10.1              Country code:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="DOCO" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID COUNTRY CODE" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


3.10.1              Document Type:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="DOCO" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID TRAVEL DOCUMENT TYPE: V, K" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>



3.10.2              Document Number:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="DOCO" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID TRAVEL DOCUMENT NUMBER" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>



3.10.3              Issue date of the passport or visa:


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="DOCO" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID VISA DOCUMENT ISSUE DATE" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


On all cases, the booking is created, but the SSR status on the PNR is UC (“unable to confirm”)


3.11         Adding an invalid type of document (FOID):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="FOID" Status="UC" DepartureAirport="" ArrivalAirport="" FlightNumber="" RecordBookDesignator="" Date="" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="INVALID IDENTIFICATION NUMBER" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>



3.12         When adding a document number bigger than 25 characters, not including the type of previous document (FOID):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="FOID" Status="UC" DepartureAirport="" ArrivalAirport="" FlightNumber="" RecordBookDesignator="" Date="" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="TOO LONG" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>


On both cases, the booking is created, but the SSR status on the PNR is UC (“unable to confirm”)


3.13         When not adding the last name/name of the infant pax (INFT):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="INFT" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/JUAN" Text="CHECK NAMES" PassengerAssociationIds="P1"/>
             </SpecialServiceRequests>



3.14         When adding an invalid birth date (INFT):


             <SpecialServiceRequests>
                    <SpecialServiceRequest Airline="XX" Code="INFT" Status="UC" DepartureAirport="AEP" ArrivalAirport="COR" FlightNumber="666" RecordBookDesignator="Y" Date="2013-08-20" NumberOfServices="1" PassengerNames="-1PEREZ/PEDRO" Text="CHECK DATE" PassengerAssociationIds="P3"/>
             </SpecialServiceRequests>


On both cases, the booking is created, but the SSR status on the PNR is UC (“unable to confirm”)


3.15         When adding not permitted or more than permitted characters:


<Error><ErrorCode>11059</ErrorCode><ErrorMsg>Error at SSR parameter Text.</ErrorMsg></Error></KIU_AirBookRS>


In this case the booking is not created, forcing to correct the information on the field <Text> of the SSR.