Overview

An example of end-to-end scenario based on on operation flow and user story


Operation flow

searchFlightsJourney → book (Flight) → reprice without PNR → reprice with PNR → demandTickets (ETK) → voidTicket (ETK)

User story

S7 Agent wants to buy one way flight from Moscow (DME) to Samara (KUF) for one adult traveler. He chooses direct S7 flight. Agent realised after ticketing that he messed up with a charged price and want to void ticket and issue it again.

Scenario

The general process for buying a trip such as this is:

  1. Initial search for flight solutions: S7 Agent executes a searchFlightsJourney operation with itinerary criteria and passenger types count;
  2. Book a reservation: S7 Agent executes a book operation with passenger details and itinerary info of chosen solution from search results;
  3. Request for informative reservation pricing: S7 Agent executes a reprice operation with itinerary info of chosen solution;
  4. Request for reservation pricing: S7 Agent executes a reprice operation with itinerary info of chosen solution;
  5. Issue tickets for all passenger: S7 Agent executes a demandTickets operation with reservation reference and pricing details.
  6. Void each ticket in reservation: S7 Agent executes a  voidTicket opertation with ETK number.

Table of contents:



Step 1: Initial search for flight solutions

S7 Agent executes a searchFlightsJourney operation with itinerary criteria and passenger types count

Received solutions divided by fare family and mostly includes 4 sub solutions (Basic Economy, Flex Economy, Basic Business, Flex Business) for each itinerary solution.

Step 2: Book a reservation

S7 Agent executes a book operation with passenger details and itinerary info of chosen solution from search results.

<DetailedFlightItem> block consists of journey information, where each slice is described by the <OriginDestination> element.

<OriginDestination>  block takes from appropriate AirShoppingRS

Envelope/Body/AirShoppingRS/DataLists/FlightSegmentList

and <ClassOfService> (RBD) from

Envelope/Body/AirShoppingRS/OffersGroup/AirlineOffers/AirlineOffer/PricedOffer/OfferPrice/RequestedDate/Associations/ApplicableFlight/FlightSegmentReference/ClassOfService/Code

Step 3: Request for informative reservation pricing

S7 Agent executes a reprice operation with itinerary info of chosen solution

All information must be taken from AirShoppingRS:

  • itinerary details (airport codes and dates for origin and departure, airline code and flight number);

(lightbulb) <FlightItem> block must fill in like in OrderCreateRQ. Each slice is described by the <OriginDestination> element.

  • passenger types (PTC);
  • fare details (RBD and fare code).

Step 4: Request for reservation pricing

S7 Agent executes a reprice operation with itinerary info of chosen solution

All information must be taken from AirShoppingRS:

  • itinerary details (airport codes and dates for origin and departure, airline code and flight number);

(lightbulb) <FlightItem> block must fill in like in OrderCreateRQ. Each slice is described by the <OriginDestination> element.

  • passenger types (PTC);
  • fare details (RBD and fare code).

Step 5: Issue tickets for all passenger

S7 Agent executes a demandTickets operation with reservation reference and pricing details

  • Add information about PNR from OrderViewRS
Envelope/Body/OrderViewRS/Response/Order/BookingReferences/BookingReference/ID
  • Fill in the form of payment as in example <*A*TEXT>


<Payments>
    <Payment>
        <Type>
            <Code>MS</Code>
        </Type>
        <Other>
            <Remarks>
                <Remark>*A*TEXT</Remark>
            </Remarks>
        </Other>
    </Payment>
</Payments>

Step 6: Void each ticket in reservation

S7 Agent executes a  voidTicket opertation with ETK number.

  • Add information about ETK number without stock number (421) from AirDocDisplayRS


Envelope/Body/AirDocDisplayRS/Response/TicketDocInfos/TicketDocInfo/TicketDocument/TicketDocNbr