Special Service Request (SSR)
- Valentina Maio (Unlicensed)
- Alvaro Chaparro
- Timothy Ling
Special Service Request (SSR) |
|---|
SSR’s is a legacy concept used to request special services for passengers on flights. Initially this service was created for, and is still used for, the requesting of free services, such as Wheelchairs, Special Dietary Meals, services for Passengers with Reduced Mobility, etc
Some SSR are inventory controlled due to operational reasons, and therefore can be rejected due to capacity restraints.
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.
The following are the SSRs that can be requested through our NDC channel.
Booking Special Services
The Special Services can be booked and held in unpaid (on hold) Orders to be paid with the flights in the servicing flow.
The bellow file contains a full end to end flow example.
SSR Code Table |
|---|
SSR Code | Purpose |
|---|---|
BLND | Blind Passenger |
DEAF | Deaf Passenger |
DPNA | Disabled Passenger, with intellectual or developmental disability needing assistance (specify details) |
WCHR | Wheelchair for passengers who can ascend/descend steps, and are able to make own way to/from cabin seat, but require wheelchair for distances. |
WCHS | Passenger cannot ascend/descend steps, but is able to make own way to/from cabin seat; requires wheelchair for distances and must be carried up/down steps. |
The code “DISA” can be included in the request, and this will return all the Special Services for disabilities that we offer in the response.
ServiceListRQ Message |
|---|
The applicable SSR Codes, that you can include as and when required, are taken from the table above.
To request an SSR it should be included in the ServiceListRQ message as a Qualifier:
<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.
It should be noted that if SSRs are requested in both the OfferPriceRQ and the ServiceListRQ, then an error will be returned (please, see an example of this scenario in our Special Services Error Messages page).
ServiceListRS Message |
|---|
ALaCarteOfferItem
The Special Services are returned in the ServiceListRS as ALaCarteOfferItems, for the passengers and flight segments for which they can be requested. This does not mean that the service is necessarily available, and is subject to confirmation at time of booking.
The Special Services can be booked and held in unpaid (on hold) Orders to be paid with the flights in the servicing flow.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ServiceListRS Version="5.000" PrimaryLangID="es" xmlns:ns2="http://www.iberia.com/IATA/NDC/SecurePayment/2017.2" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
<Document>
<ReferenceVersion>5.000</ReferenceVersion>
</Document>
<Success/>
<ShoppingResponseID>
<ResponseID>Qm9va2luZ0BHVy0xNjk1NjUyMTg3MjcwLTRSWERW</ResponseID>
</ShoppingResponseID>
<ALaCarteOffer OfferID="ALACARTE_IB48ed39bdf2204eb19f485e1357abe0a3" Owner="IB">
<OfferExpirationDateTime>2024-03-06T14:05:42.327Z</OfferExpirationDateTime>
<TimeLimits>
<Payment DateTime="2024-03-24T22:59:00.000Z"/>
</TimeLimits>
<ALaCarteOfferItem OfferItemID="ALACARTE_SSR_IB48ed39bdf2204eb19f485e1357abe0a3_BLND">
<Eligibility>
<PassengerRefs>ADULT_01 ADULT_02</PassengerRefs>
<SegmentRefs>IB042620240108 IB042520240128</SegmentRefs>
</Eligibility>
<UnitPriceDetail>
<TotalAmount>
<SimpleCurrencyPrice Code="EUR">0.00</SimpleCurrencyPrice>
</TotalAmount>
<BaseAmount Code="EUR">0.00</BaseAmount>
<Taxes>
<Total Code="EUR">0.00</Total>
</Taxes>
</UnitPriceDetail>
<Service ServiceID="SSR_BLND_d0730723-ab16-405a-8c44-6adbd32a0efc">
<ServiceDefinitionRef>SPECIAL_NEED-BLND</ServiceDefinitionRef>
</Service>
</ALaCarteOfferItem>
</ALaCarteOffer>ServiceDefinitionList
ContainsServiceDefinition with additional information describing each of the specific ALaCarteOfferItem, to which they are linked using the ServiceDefinitionRef in the ALaCarteOfferItem.
The BookingInstructions are used by certain system providers for legacy reasons.
MaximumQuantity is the amount services permitted for each passenger per flight.
<ServiceDefinitionList>
<ServiceDefinition ServiceDefinitionID="SPECIAL_NEED-BLND">
<Name>Blind Passenger</Name>
<Descriptions>
<Description>
<Text>Request Service Animal if travelling with one</Text>
</Description>
</Descriptions>
<BookingInstructions>
<SSRCode>BLND</SSRCode>
<Method>SSR</Method>
</BookingInstructions>
<Detail>
<ServiceItemQuantityRules>
<MaximumQuantity>1</MaximumQuantity>
</ServiceItemQuantityRules>
</Detail>
</ServiceDefinition>
</ServiceDefinitionList>
OrderCreateRQ Message |
|---|
The OfferID for each is ALaCarteOfferItem is included in an Offer in the OrderCreateRQ to book the service.
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:
Example with optional additional information:
Example without optional additional information:
DPNA example with mandatory Description / Text
DPNA example without mandatory Description / Text and error message:
OrderViewRS Message |
|---|
The service will then be returned in the OrderViewRS as an OrderItem with zero price for those services that are offered free of charge and without any EMD:
And the OrderItem is linked to the ServiceDefinition where the service is again described:
In the ServiceDefinitionList the additional information provided is reflected back to you, together with the BookingInstructions needed by legacy systems.
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>.
MediaList |
|---|
Here is where we put URLs that can be used to link to additional information such as rich media and other useful information for the customer:
Examples of messages with complete flows can be downloaded from here.
UPDATE as of December 17, only people with an Iberia or IAGGBS account will be able to access them. Write to jira.support.ib@iberia.es and we will help you with the change. ACTUALIZACIÓN a partir del 17 de diciembre, sólo podrán acceder a ellas personas con cuenta de Iberia o IAGGBS. Escribe a jira.support.ib@iberia.es y te ayudaremos con el cambio.