Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel7

...

Some services are not accepted by our code-share partners, and therefore may be rejected.

Note: The inclusion of SSRs can only be done in the initial creation of the Order and not added later in a Servicing flow.

...

Code Block
<Qualifier>
	<SpecialNeedQualifiers>
		<Code>BLND</Code>
	</SpecialNeedQualifiers>
</Qualifier>

Note: Formerly, the only way to request SSRs was through OfferPriceRQ message, which is still possible to maintain backward compatibility. However, we recommend that from now on the ServiceList is used.

...

Code Block
<Order>
	<Offer OfferID="IB01db6efac4044bd7b6d65113a60b5281OC" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW">
		<OfferItem OfferItemID="IB01db6efac4044bd7b6d65113a60b5281OC_01">
			<PassengerRefs>ADULT_01 ADULT_02</PassengerRefs>
		</OfferItem>
		<OfferItem OfferItemID="IB01db6efac4044bd7b6d65113a60b5281OC_02">
			<PassengerRefs>INFANT_01</PassengerRefs>
		</OfferItem>
	</Offer>
	<Offer OfferID="ALACARTE_IB48ed39bdf2204eb19f485e1357abe0a3" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW">
		<OfferItem OfferItemID="ALACARTE_SSR_IB48ed39bdf2204eb19f485e1357abe0a3_BLND">
			<PassengerRefs>ADULT_01 ADULT_02</PassengerRefs>
			<ServiceSelection ServiceID="SSR_BLND_d0730723-ab16-405a-8c44-6adbd32a0efc">
				<ServiceDefinitionID>SPECIAL_NEED-BLND</ServiceDefinitionID>
			</ServiceSelection>
		</OfferItem>
	</Offer>
</Order>

The ServiceSelection is mandatory for Special Service Request in the OrderCreateRQ.

Also the ServiceDefinition is mandatory for Special Service Request in the OrderCreateRQ. Additional information in the Description / Text is optional, except for DPNA, which is mandatory.

The correct SSRCode must be included, otherwise the NDC_DIST_2164 error will be returned.

Example without mandatory ServiceSelection and error message:

Code Block
languagexml
<Offer OfferID="ALACARTE_SSR_IBe77ae231cf2040c184b96b814561bf26" Owner="IB"
            ResponseID="Qm9va2luZ0BHVy0xNzI4NDc0NjEzMTM5LWU2Qzls">
  <OfferItem OfferItemID="IB4f4689ba25af417a96cfb5053dfa2e12OC_BLND">
      <PassengerRefs>ADULT_01</PassengerRefs>
  </OfferItem>
</Offer>
-------------------------------------------------------------------------
<ServiceDefinitionList>
  <ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-BLND">
      <Name>Blind Passenger</Name>
      <Descriptions>
        <Description refs="ADULT_01">
            <Text>Request Service Animal if travelling with one</Text>
        </Description>
      </Descriptions>
      <BookingInstructions>
        <SSRCode>BLND</SSRCode>
      </BookingInstructions>
  </ServiceDefinition>
</ServiceDefinitionList>
Code Block
languagexml
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>UNEXPECTED_TECHNICAL_EXCEPTION</faultstring>
         <detail>
            <code>FRAM_B0006</code>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

Example with optional additional information:

...

Any Special Services not available through NDC should be requested through ServIberia at least 48 hours before the flight. 

IMPORTANT NOTE

Under no circumstances should the contents of any refs or ID’s be used to identify the type of service being offered/given. In the case of Ancillaries the RFIC and SubCode(RFISC) decoded against the ATPCo Optional Services Industry Sub Codes should be used, and in the case of Special Service Requests, the SSRCode should be used, decoded against the IATA Airimp or the above table, or you can simply use the <Name>.

...