Sporting Equipment

 

Sporting Equipment

Sporting Equipment

For information on Iberia’s Special Baggage Policy, please see Baggage in the hold - Iberia Spain

Through NDC, in addition to the 23kg, 15kg and 32kg baggage weights and the Priority Boarding service, Sporting Equipment options will be offered by Ancillaries as follows:

  • Bicycle Equipment (BICYCLE)

  • Fishing Equipment (FISHING_EQUIPMENT)

  • Golf Equipment (GOLF_EQUIPMENT)

  • Scuba Diving Equipment (SCUBA_DIVING)

  • Ski Equipment (SKI_SNOW)

  • Surf Equipment (SURFBOARD)

To purchase Sporting Equipment baggage, the ServiceFilter/GroupCode needs to be sent in the ServiceListRQ message as per the SubGroup and Group codes displayed in this table:

Sporting Equipment can ONLY be included in an OrderCreate (with payment), or added to an already paid Order.

The information regarding the price and details is included in the message response, later displayed in these examples.

 

ServiceListRQ Message

ServiceListRQ Message

When new services are released, we will publish the new applicable ServiceFilters, and you can include them as and when required, as per the following examples:

<Parameters> <ServiceFilters> <ServiceFilter> <GroupCode>BG</GroupCode> </ServiceFilter> <ServiceFilter> <GroupCode>TS</GroupCode> <SubGroupCode>PR</SubGroupCode> </ServiceFilter> <ServiceFilter> <GroupCode>BG</GroupCode> <SubGroupCode>SP</SubGroupCode> </ServiceFilter> </ServiceFilters> </Parameters>

The Parameters section shows that all of the available Ancillaries have been requested.

Please, note that both GroupCode and SubGroupCode information are being taken from this table, and that the above-mentioned example combines three ancillaries (Priority Boarding and Sporting Equipment). At the moment, these are all of the Ancillaries offered through our NDC Channel.

An example of a ServiceListRQ in the prime shopping flow, following the OfferPrice could look something like the following:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> <ServiceListRQ Version="5.000" PrimaryLangID="es" xmlns="http://www.iata.org/IATA/EDIST/2017.2"> <PointOfSale> <Location> <CountryCode>ES</CountryCode> </Location> </PointOfSale> <Document> <ReferenceVersion>1.0</ReferenceVersion> </Document> <Party> <Sender> <TravelAgencySender> <IATA_Number>########</IATA_Number> <AgencyID>firstAgency</AgencyID> </TravelAgencySender> </Sender> <Participants> <Participant> <AggregatorParticipant SequenceNumber="1"> <AggregatorID>########</AggregatorID> </AggregatorParticipant> </Participant> </Participants> </Party> <Parameters> <ServiceFilters> <ServiceFilter> <GroupCode>BG</GroupCode> </ServiceFilter> <ServiceFilter> <GroupCode>TS</GroupCode> <SubGroupCode>PR</SubGroupCode> </ServiceFilter> <ServiceFilter> <GroupCode>BG</GroupCode> <SubGroupCode>SP</SubGroupCode> </ServiceFilter> </ServiceFilters> </Parameters> <ShoppingResponseID> <ResponseID>Qm9va2luZ0AxNjg5NTgxODI4OTI5LWFzcHd6</ResponseID> </ShoppingResponseID> <Query> <Offers> <Offer> <OfferID Owner="IB">IBda189b81160243a9932b7aeb1ef0d6a6OC</OfferID> <OfferItemIDs> <OfferItemID Owner="IB">IBda189b81160243a9932b7aeb1ef0d6a6OC_01 </OfferItemID> </OfferItemIDs> </Offer> </Offers> </Query> </ServiceListRQ> </soapenv:Body> </soapenv:Envelope>

The above example is in the presale flow. For a postsale flow, simply replace the OfferID within the Query section with the OrderID:

<Query> <OrderID Owner="IB">IB24847487859643f69318ea7fa100e3beOC</OrderID> </Query>

 

ServiceListRS Message

ServiceListRS Message

All services offered are included within the ServiceList message response. This will evolve as more services are offered through the NDC channel.

Maintaining backward compatibility with our initial implementation, and with the new services being added, it is necessary to include the ServiceFilter if you want to sell them (as applied to Priority Boarding and Bags, and within the Parameters section). There is no need, however, to request them all since each ServiceFilter will retrieve the associated one.

AlaCarteOfferItem - in ServiceListRS

The OfferItem shows the unit price of the Service for the applicable passengers and flight segments.

The ServiceDefinitionList contains a list of the different Services each defined as necessary.

When there are more than one service then the number of <ServiceDefinitionRef> elements gives you the number of those services. We do not recommend you use the numbers in the Name or the Description Text to discern the number of services.

Using the RFIC together with the Subcode together with the ATPCo Optional Services Industry Sub Codes., the Grouping and SubGrouping of the services can be achieved.

The same principle as in our Bags ServiceDefinitionList is applied here. The purchase of multiple baggage is solved using the ServiceBundle, made up of various individual bag services, the NotPermitted combinations are shown to prevent the purchase of a number of bags that would exceed the maximum quantity allowed (which, for Sporting Equipment, is three).

Please, note that the ServiceDefinition BookingInstructions section for Golf, Ski, Fishing, Scuba Diving and Surfboard (you can only buy one surfboard item) baggage type the SSRCode looks like the following:

And for the Bike baggage type is:

 

OrderCreateRQ Message

OrderCreateRQ Message

Service Bundle

From the OrderCreate Request (and as an example of the various combinations) the following code shows that Sporting Equipment baggage is being assigned to different passengers, following the same process as in Bags with different weights.

As shown in the previous section, the Sporting Equipment requested is three bicycles.

Since these samples are being extracted from the same Flow, we can see that the OfferID is the same reported in the ServiceListRQ (<OfferID Owner="IB">IBda189b81160243a9932b7aeb1ef0d6a6OC</OfferID>), and so is the OfferItemID (<OfferItemID Owner="IB">IBda189b81160243a9932b7aeb1ef0d6a6OC_01 </OfferItemID>).

 

If you are adding the ancillary to an already existing, and paid for, Order then the OrderChangeRQ is used as per the following:

OderChangeRQ Message

OderChangeRQ Message

When adding ancillaries to an existing Order, you reference the existing OrderID and the OfferItem’s that you wish to purchase from the previous ServiceListRQ.

Remember:

  1. Ancillaries cannot be added to an unpaid Order.

  2. Payment for the ancillaries must be included, as you cannot add an unpaid ancillary to a paid Order.

 

OrderViewRS Message

OrderViewRS Message

In the OrderViewRS the Sporting Equipment Ancillary is shown in the following way.

First, the OrderItem:

And the ServiceDefinition, where we can observe all Ancillaries that are included in this specific example, according to their ServiceDefinitionID (Bags, Priority Boarding, and Sporting Equipment services).

 

MediaList

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.