Introduction

To support Sabre technology modernization efforts, we are changing the Sabre agency reservation logic and workflows for American Airlines (AA), which will result in AA and Sabre travel agencies no longer sharing a single reservation (PNR). This change in the booking process will affect API customers.

Currently, for Special Service Requests (SSRs) and Other Services (OSI), agencies follow separate workflows for AA and other carriers. After this change, we will begin a transitional period where both workflows will coexist; however, once the period ends, your workflows may have to be adjusted. To better understand and prepare for these potential changes in API behavior, refer to the guidelines below for the affected services.

Questions? For additional information on SSRs and other products impacted, please refer to SAN16279. If you aren't already subscribed to Sabre Advance Notifications, contact your account manager to subscribe and receive important updates.

Note: All API examples below are XML SOAP, unless stated otherwise.

Affected LLSRQ APIs

Send Sabre Command (SabreCommandLLSRQ)

Before and after PCC activation:

For agency PNRs created prior to activation with at least one AA flight (active/flown):

After PCC activation:

For agency PNRs created after activation with at least one AA flight, or agency PNRs created prior to activation that never had an AA flight (active/flown), but the AA flight was added after activation, use Action Codes 3 or 4:

Add Special Service (SpecialServiceLLSRQ)

Before and after PCC activation:

For agency PNRs created prior to activation with at least one AA flight (active/flown):

To add OSI/SSRs associated with AA flights, use the <VendorPrefs> node to trigger the correct command, starting with "4".

Note: These items are stored under the AA Facts field.

After PCC activation:

For agency PNRs created after activation with at least one AA flight, or agency PNRs created prior to activation that never had an AA flight (active/flown), but the AA flight was added after activation:

When adding OSI/SSRs associated with AA flights, <VendorPrefs> becomes optional. If used, it will still trigger commands starting with "4", but the Sabre system will orchestrate a "3" command anyway.

Note: These items are stored under the General Facts field. If not used, the PNR entry will default to a "3" command.

Recommendations

Delete Special Service (DeleteSpecialServiceLLSRQ)

Before PCC activation:

For agency PNRs created prior to activation with at least one AA flight (active/flown):

To delete OSI/SSRs associated with AA flights, the <VendorPrefs> node must be used to trigger the right command (staring with "4"). These items are stored under the AFAX field.

After PCC activation:

For agency PNRs created prior to activation with at least one AA flight (active/flown):

To delete OSI/SSRs associated with AA flights, the <VendorPrefs> node must be used to trigger the right command (staring with "4"). These items are stored under the AFAX field.

For agency PNRs created after activation with at least one AA flight, or agency PNRs created prior to activation that never had an AA flight (active/flown), but the AA flight was added after activation:

To delete OSI/SSR associated to AA flights, the node should NOT be used, since these items will be stored under GFAX field. Full example below:

Book Air Segment (OTA_AirBookLLSRQ)

Selling an AA flight before PCC activation:

Errors may occur when trying to sell an AA flight. You may see a "UC" status returned with a direct error response:

Selling an AA flight after PCC activation:

Errors may occur when trying to sell an AA flight. The response will be the same as other errors when selling flights for other airlines: