Update Reservation Request Structure
The PNR data present in the response payload depends on the parameters used in the request. The parameters can be used to reduce the number of elements returned.
Following are descriptions of the request parameters (RQ) that can be combined to create a request message.
Views
The PNR data which will be present in the response payload depends on the View Name used in the request. The number of data elements returned in each View can be further narrowed by Subject Areas. If data elements corresponding to a specified Subject Area are not present in the PNR, then those will not be returned in the response payload. The most common View Names and Subject Areas are listed below. Custom made Views and Subject Areas may be developed if required.
| View | Description | Allow Custom Subject Areas3 | History |
|---|---|---|---|
| Simple | Always used, regardless of whether it is provided in the request. Includes: HEADER (Booking and Point of Sale details) | Yes | No |
| Default | It contains PNR data specified by all ACTIVE1 SUBJECT AREAS. Includes: SIMPLE VIEW; all PRIMARY SUBJECT AREAS | Yes | No |
| Full | It contains PNR data specified by all PRIMARY2 and HISTORY SUBJECT AREAS. Includes: SIMPLE VIEW; all PRIMARY SUBJECT AREAS, DSS4, AIR_CABIN4, OPENRESDATA | Yes4 | Yes |
1Active Subject Areas – a set of subject areas that are predefined as default view
2Primary Subject Areas – a set of subject areas that are predefined as default view (without additional information about the flight that are stored in DSS database)
3Allow Custom Subject Areas – for selected views it is possible to determine what types of data are presented in the web service response by defining SubjectAreas in the request.
4This functionality will be available starting from September release.
Subject Areas
Subject Areas define what parts of PNR data can be additionally presented in the web service response. Provisioning of Subject Areas in the web service request is optional. Unless Subject Areas are specified in the request, the default Subject Areas defined by the view that was chosen are applied. Simple view, can be extended by additional SubjectAreas. Information from SubjectAreas will be provided in response message if they were stored in PNR. The most common SubjectAreas are listed below.
| Subject Areas | Description |
|---|---|
| ACCOUNTING_LINE | Agency accounting lines stored in the PNR. |
| ACTIVE | This SA is an aggregator for a wide group of other Subject Areas: FQTV, ADDRESS, DKNUMBER, VCR, PASSENGERDETAILS, PRERESERVEDSEAT, AFAX, GFAX, REMARKS, MISC_TICKETING, BSGPROCESSING, FARETYPE, TICKETINGENTRIES, BAS_EXTENSION, CORPORATE_ID, ACCOUNTING_LINE, SUBSCRIPTION_CARD, GROUP_PLANNER, TRAVEL_POLICY, CUST_INSIGHT_PROFILE, TICKETING, TKT_ON_DEMAND, ITINERARY, DESCRIPTIVE_BILLING_INFO, EXT_FQTV, HEADER, NAME, RECORD_LOCATOR, RECEIVED, PHONE, ANCILLARY, ORE_COUNT, EQD_DATA, DSS, OPENRESDATA - Available only in stateless mode |
| ADDRESS | Agency address data stored in the PNR. |
| AIR_CABIN | Air Cabin supplements segment information with Air Cabin Class information and adds Product nodes (Itinerary Products stored in Open Res) |
| AFAX | AFAX allows to display hosted facts under GenericSpecialRequests and OpenReservationElemets nodes (any SSR or OSI; DOCS, DOCO, WCHR, VGML, PETC); All American Airlines facts (AFAX) excluding Pre-reserved seats |
| ANCILLARY | Ancillary Items (Air Extra) stored in the PNR. Ancillaries are displayed in the response only when NAME subject area is used in request. |
| BAS_EXTENSION | BAS_EXTENSION supplements itinerary data with some additional data, mainly connected to Hotels and Cars e.g. confirmation number in Hotel, credit card inf. |
| BSGPROCESSING | Block Space Group data stored in the PNR. |
| CARRIER_INFORMATION_CALCULATE | Using this Subject Area display of operating airline is changed in response: information from DSS are used to recalculate the information of operating airline. |
| CARRIER_INFORMATION_COMP ACT | Using this Subject Area display of operating airline is changed in response: if operating Airline is equal marketing airline only marketing airline is displayed. |
| CORPORATE_ID | Agency ID for Corporate Client stored in the PNR. |
| CUST_INSIGHT_PROFILE | Allows to display Profile information (Customer and Corporate) |
| DK_NUMBER | Customer number stored in the PNR⎯agencies use DK number primarily as an account reference identifier for billing purposes. |
| DSS | DSS supplements segment information with data stored in DSS (those are elapsed time, Air Miles Flown, Funnel Flight, Change of Gauge, Operating Airline Code, Stop Quantity) and updates Equipment Type with current data. |
| EXT_FQTV | External Frequent Traveler Number |
| FARETYPE | Fare data stored in the PNR. |
| FQTV | Frequent Flyer details stored in PNR. |
| GFAX | GFAX allows to display general facts; All airline facts |
| HEADER | PNR header data. |
| HISTORICAL | - Displays history of the PNR - Available only in stateless mode - Allows to display PNR history |
| ITINERARY | Itinerary data stored in the PNR including Air, Rail, Car, Hotel, etc. To display full Itinerary information request should also include additional Subject areas: DSS, AIR_CABIN, OPENRESDATA, BAS_EXTENSION |
| NAME | Passenger Name stored in the PNR. |
| PASSENGERDETAILS | Profile data, passenger type, email address, and other details stored in the PNR. |
| PHONE | Phone data stored in the PNR. |
| POPULATE_IS_PAST | To determine if a particular segment is active or in past |
| PRICE_QUOTE1 | PQ data received from PQ web service. The service is applicable for all price quote users (basic and enhanced PQ). |
| PRERESERVEDSEAT | Pre reserved seat data stored in the PNR. |
| PRICING_INFORMATION | Itinerary pricing information stored in PNR. This subject area is used to retrieve price quote information. This is a legacy way of retrieving those data and is no longer recommended. The recommended way to obtain this information is to use PRICE_QUOTE subject area. |
| RECEIVED | Received From Field stored in the PNR. |
| RECORD_LOCATOR | Allows to display TTY Record Locator |
| REMARKS | Allows to display remark information (supported types: REG, HD, HS, CLIADR, DELADR, INVOICE, ITINERARY, INTERFACE, CODED_A, PRTONTKT, CORPORATE, FOP, QQ, FILLER, ITINSEGASSOC) |
| REMARK_ACTION_CODE | GetRes will return ActionCode as a prefix in RemarkLine text for types: SBUDIDS (INVOICE), SBPRINTONTICKET (PRTONTKT), SBCORPORATE (CORPORATE), SBBILLING (INTERFACE) only when REMARK_ACTION_CODE subject area is provided |
| TICKETING | Ticketing information stored in the PNR. |
| VCR | Virtual Coupon Record |
*Active Subject Areas 1 For more information please go to: https://developer.sabre.com/docs/soap_apis/air/fulfill/manage_price_quote_details/resources, where you can read wide description of the PQ Web Service. The documentation mentioned above is the most up-to date description that is available on dev studio. User Guide of PriceQuote Web Service (linked above) provides information about types of operations that the service supports and points out the ones that are not valid Price Quote Service requests. It also contains an explanation of essential terms associated with the PriceQuote Web Service transactions.