Manual SSR5.0
Name |
Manual SSR |
Code |
ManualSSR |
Source |
Entity ManualSSR |
XML Element |
BookingData/SSRInformation/NonProgrammaticSSR |
Description
A Special Service Request (SSR) is a message sent directly to suppliers to communicate traveler preferences, special services needed by a traveler, or of a procedural requirement necessary of the carrier. SSRs are used for air segments only.
SSRs include information such as meal preference or special assistance required the traveler. In addition, the SSR can send an alert message back to the agency or travel provider. SSRs can originate with the travel provider asking for service from the carrier or from the carrier asking for information (like a ticket number) from the travel provider.
Because action must be taken by the carrier, there is usually a reply from them in the form of the status code on the SSR (HK, UN, etc.)
A Special Service Request (SSR) can be made in a PNR on behalf of one traveler, several travelers, or all travelers for specific segments or an entire itinerary. A single traveler and/or single segment may have multiple SSRs assigned to it, but the same SSR cannot be assigned to the same traveler/segment more than once.
SSRs require the carrier to take action, while OSIs are informational only and do not typically require an action or response from the carrier. OSIs and SSRs are NOT interchangeable. An SSR should be used if possible; an OSI should be used only if there is no standardized SSR available for the service needed.
SSRs can either be Programmatic (automated) or Manual (non-automated). Programmatic SSRs use a codes recognized by the provider/supplier, while Manual SSRs do not have an associated programmatic code, and some items must be entered as a manual SSR. Programmatic SSRs are associated to both an Air segment and a PNR (ProviderReservationInfoRef); Manual SSRs are associated only to a PNR.
Fields
Travel Order Event Identifier
Field Label |
TravelOrderIdentifier |
XML Element |
No equivalent XML. |
Attributes |
4 N |
Status |
Mandatory |
Description |
A programmatically generated number that uniquely identifies the travel order event. Passed to this table from the TableOrderEvent table. |
Event Type |
Ticketing |
Allowable Values |
Not applicable. |
SSR Sequence Number
Field Label |
SSRSequenceNbr |
XML Element |
No equivalent XML. |
Attributes |
2 N |
Status |
Mandatory |
Description |
A programmatically generated number that identifies the position of this SSR (Special Service Request) in the PNR/BF. |
Event Type |
Booking |
Allowable Values |
Not applicable. |
SSR Code
Field Label |
SSRCode |
XML Element |
SSRCode |
Attributes |
4 A |
Status |
Optional |
Description |
The SSR Code applicable to the Manual (Non-Programmatic) SSR item. For example: FOID, PSPT, DOCS, DOCA, and DOCO. |
Event Type |
Booking |
Allowable Values |
Not applicable. |
SSR Vendor Code
Field Label |
SSRVendorCode |
XML Element |
VendorCode |
Attributes |
3 A/N |
Status |
Optional |
Description |
The vendor providing the service requested. |
Event Type |
Booking |
Allowable Values |
Not applicable. |
Status Code
Field Label |
StatusCode |
XML Element |
StatusCode |
Attributes |
2 A |
Status |
Optional |
Description |
The current status of this service request. |
Event Type |
Booking |
Allowable Values |
Not applicable. |
Number Required
Field Label |
NbrRequired |
XML Element |
NbrRequired |
Attributes |
2 N |
Status |
Optional |
Description |
The number of services requested for the SSR item. |
Event Type |
Booking |
Allowable Values |
Not applicable. |
SSR Data
Field Label |
SSRData |
XML Element |
SSRFreeText |
Attributes |
255 A/N (variable) |
Status |
Optional |
Description |
Free text for the SSR item. |
Event Type |
Booking |
Allowable Values |
Not applicable. |