Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema PNRChangeRQ.xsd
Namespace No namespace
Properties
attribute form default: unqualified
element form default: unqualified
[ top ]
Included schema CommonTypes.xsd
Namespace No namespace
Properties
attribute form default: qualified
element form default: qualified
[ top ]
Element PNRChangeRQ
Namespace No namespace
Annotations
PNR change request root element
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_version PNRChangeRQ.tmp#RecordLocator PNRChangeRQ.tmp#SaleInfo PNRChangeRQ.tmp#TicketingInfo PNRChangeRQ.tmp#ChangeTraveler PNRChangeRQ.tmp#PNRChangeRQ_ChangeAir PNRChangeRQ.tmp#PNRChangeRQ_ChangeFareGroup PNRChangeRQ.tmp#PNRChangeRQ_ChangeStoredPrice PNRChangeRQ.tmp#ChangeCar PNRChangeRQ.tmp#ChangeHotel PNRChangeRQ.tmp#ChangeTicketing PNRChangeRQ.tmp#ChangeTelephone PNRChangeRQ.tmp#PNRChangeRQ_ChangeRemark PNRChangeRQ.tmp#PricingInfo PNRChangeRQ.tmp#PNRChangeRQ_ChangeFormOfPayment PNRChangeRQ.tmp#PNRChangeRQ_ChangeSeat PNRChangeRQ.tmp#PNRChangeRQ_ChangeSeatOptimization PNRChangeRQ.tmp#PNRChangeRQ_ChangeAPIS PNRChangeRQ.tmp#Display PNRChangeRQ.tmp#EndTransaction
Properties
content: complex
Model RecordLocator{0,1} , SaleInfo{0,1} , TicketingInfo{0,1} , ChangeTraveler* , ChangeAir* , ChangeFareGroup* , ChangeStoredPrice* , ChangeCar* , ChangeHotel* , ChangeTicketing{0,1} , ChangeTelephone* , ChangeRemark* , PricingInfo* , ChangeFormOfPayment* , ChangeSeat* , ChangeSeatOptimization* , ChangeAPIS* , Display{0,1} , EndTransaction{0,1}
Children ChangeAPIS, ChangeAir, ChangeCar, ChangeFareGroup, ChangeFormOfPayment, ChangeHotel, ChangeRemark, ChangeSeat, ChangeSeatOptimization, ChangeStoredPrice, ChangeTelephone, ChangeTicketing, ChangeTraveler, Display, EndTransaction, PricingInfo, RecordLocator, SaleInfo, TicketingInfo
Instance
<PNRChangeRQ version="">
  <RecordLocator>{0,1}</RecordLocator>
  <SaleInfo>{0,1}</SaleInfo>
  <TicketingInfo>{0,1}</TicketingInfo>
  <ChangeTraveler>{0,unbounded}</ChangeTraveler>
  <ChangeAir AutoExchange="">{0,unbounded}</ChangeAir>
  <ChangeFareGroup FareNumber="">{0,unbounded}</ChangeFareGroup>
  <ChangeStoredPrice FareNumber="" TravelerType="">{0,unbounded}</ChangeStoredPrice>
  <ChangeCar>{0,unbounded}</ChangeCar>
  <ChangeHotel>{0,unbounded}</ChangeHotel>
  <ChangeTicketing>{0,1}</ChangeTicketing>
  <ChangeTelephone>{0,unbounded}</ChangeTelephone>
  <ChangeRemark>{0,unbounded}</ChangeRemark>
  <PricingInfo FareType="" Price="" StorePrice="N">{0,unbounded}</PricingInfo>
  <ChangeFormOfPayment>{0,unbounded}</ChangeFormOfPayment>
  <ChangeSeat>{0,unbounded}</ChangeSeat>
  <ChangeSeatOptimization Deactivate="">{0,unbounded}</ChangeSeatOptimization>
  <ChangeAPIS>{0,unbounded}</ChangeAPIS>
  <Display>{0,1}</Display>
  <EndTransaction TransactionType="">{0,1}</EndTransaction>
</PNRChangeRQ>
Attributes
QName Type Fixed Default Use Annotation
version xsd:string optional
Version number.  Example: 1.0
Source
<xsd:element name="PNRChangeRQ">
  <xsd:annotation>
    <xsd:documentation>PNR change request root element</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="RecordLocator" minOccurs="0"/>
      <xsd:element ref="SaleInfo" minOccurs="0"/>
      <xsd:element ref="TicketingInfo" minOccurs="0"/>
      <xsd:element ref="ChangeTraveler" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="ChangeAir" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="SegmentIDRef" maxOccurs="unbounded">
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute ref="Source"/>
                    <xsd:attribute ref="SourceRef"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:choice>
              <xsd:element name="NewStatusCode">
                <xsd:annotation>
                  <xsd:documentation>New status code of the segment as referenced in SegmentIDRef. The status codes are typical GDS status code. However, mostly status changes involve changing staus to HK or RR Example: RR, HK</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:minLength value="1"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:element>
              <xsd:element name="NewClassOfService">
                <xsd:annotation>
                  <xsd:documentation>New calss of service of the segment as referenced in SegmentIDRef. Note that for married segment the change should be done for all segments in a marriage. Example: C</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:maxLength value="2"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:element>
              <xsd:element name="DepartureDate" type="xsd:date" minOccurs="0" maxOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>NOT IMPLEMENTED YET</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:choice>
          </xsd:sequence>
          <xsd:attribute name="AutoExchange">
            <xsd:annotation>
              <xsd:documentation>Allowed value = "Y" Identifies this request as a request to be handled by an auto-exchange process (e.g. ReShop by ITA).</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ChangeFareGroup" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Change applies to entire fare group as referenced by attribute @FareNumber Note: for any changes to the TravelerGroup use the "ChangeStoredPrice" node</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="TravelStats" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="PurposeCode" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="DestinationCode" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="FareNumber" type="xsd:string" use="required">
            <xsd:annotation>
              <xsd:documentation>FareNumber of FareGroup to be modified. Example: 2</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ChangeStoredPrice" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Used to modify a stored fare in PNR at the TravelerGroup level (identified by the PTC). Use one ChangeStoredPrice per fare you want to modify. See attribute FareNumber. The value of this attribute is to be taken from PNRViewRS/FareGroup/FareNumber. In general all values entered in this section will replace values in stored fare (if any).</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="RelatedSegment" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>These are the values of the RelatedSegment element(s) of the respective Faregroup/ TravelerGroup to be changed.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element ref="SegmentIDRef"/>
                  <xsd:element ref="TicketDesignator" minOccurs="0"/>
                  <xsd:element ref="BaggageAllowance" minOccurs="0"/>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="NewCommission" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>Overwrites a commission stored w/ a fare and sets it to the value of this element. Commission percentage or amount. Commission will be in the samecurrency as the fare this commission applies to. Number of digits after decimal point is governed by the CurrencyCode element in the FareGroup this commission is associated with. See PNRViewRS/FareGroup/Commission/@NumberOfDecimals Amadeus - the new commission will replace the old commission. No repricing will take place since commissions are maintained outside of TST's. Apollo/Galileo - TBD Sabre - Note that on Sabre if PQ is used to stored automated fares entering commission will result in a repricing of the fare which potentially could lead to a different fare as previously stored. Worldspan - TBD Example: 2000</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="CommissionType">
                    <xsd:attribute name="RuleCode" type="xsd:string">
                      <xsd:annotation>
                        <xsd:documentation>System defined commission processing code. Can be retrieved in RevenueStructureRS Example: XYZ. Note: integration function w/ backoffice system. Not currently supported by XX1.</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="TourCode" type="xsd:string" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>FUTURE USE. Tour code identifier. Example: ITGF12</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="TicketType" type="xsd:string" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>FUTURE USE. identifies First, Bulk or Tour ticket and maps to @Tour attribute in PNRViewRS Example: U (Bulk)</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="Endorsement" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>FUTURE USE. Creates endorsements associated with the fare. See Type attribute for details of endorsement types. In general, on tickets issued manual endorsements will override those automatically generated by the GDS/CRS, which are then no longer visible in the PNR. However, if a GDS (e.g. Apollo, Sabre) returns both generated and manual endorsements stored w/ a fare, both will be present in PNRViewRS distinguished by their Type. Amadeus allows only either-or mode - either manual or automatically generated enorsements will be present in the PNR. Which endorsements will be printed on the ticket depends on GDS-specific logic. As a rule of thumb: manual will override generated.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:complexContent>
                  <xsd:extension base="BasicEndorsement">
                    <xsd:attribute name="Type" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Identifies the creation mode of this line. Values are: M - manual override entered by agent P - manual agent entered to be appended to the automatically generated line.</xsd:documentation>
                      </xsd:annotation>
                      <xsd:simpleType>
                        <xsd:restriction base="xsd:string">
                          <xsd:length value="1"/>
                          <xsd:enumeration value="M"/>
                          <xsd:enumeration value="P"/>
                        </xsd:restriction>
                      </xsd:simpleType>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:complexContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="NetRemit" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Net remit group.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="APBC" type="xsd:positiveInteger" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>This IATA term stands for 'Amount Paid By Customer' and is needed for Net Remit methods 2A, 2E. Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 57500</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="AEBA" type="xsd:positiveInteger" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>This IATA term stands for 'Amount Entered By Agent' and is needed for Net Remit methods 2A, 2E Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 50500</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
                <xsd:attribute name="NRIndicator" type="xsd:string" use="required"/>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="TravelStats" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="PurposeCode" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                  <xsd:element name="DestinationCode" minOccurs="0">
                    <xsd:annotation>
                      <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="FareNumber" type="xsd:string" use="required">
            <xsd:annotation>
              <xsd:documentation>FareNumber of FareGroup to be deleted from PNR. Example: 2</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="TravelerType" type="xsd:string" use="required">
            <xsd:annotation>
              <xsd:documentation>PAX Type requested. This value is used as a key to identify the TravelerGroup within the FareGroup to be modified.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="ChangeCar" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="ChangeHotel" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="ChangeTicketing" minOccurs="0"/>
      <xsd:element ref="ChangeTelephone" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="ChangeRemark" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Change Remark group includes change of NameRemark as well as different types of PNR remark elements.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:choice>
              <xsd:element ref="ElementNumber"/>
              <xsd:element ref="TattooNumber"/>
            </xsd:choice>
            <xsd:choice>
              <xsd:element ref="NewNameRemark">
                <xsd:annotation>
                  <xsd:documentation>The ElementNumber above or TattooNumber must point to a PNR traveler name element when changing name remarks. Otherwise an error will be returned.</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element ref="NewRemark">
                <xsd:annotation>
                  <xsd:documentation>The ElementNumber or TattooNumber above must identify a PNR remark of the specified type when changing PNR remarks. Otherwise an error will be returned.</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:choice>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="PricingInfo" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="ChangeFormOfPayment" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>ChangeFormOfPayment will result in deletion of form of payment element identified by ElementNumber and creation of a new form of payment element. Note that the newly created form of payment element will be also assigned a new element number.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="ElementNumber"/>
            <xsd:element name="FormOfPayment">
              <xsd:annotation>
                <xsd:documentation>New for of payment data to be created.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element ref="TravelerIDRef" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:element ref="SegmentIDRef" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:element ref="ServiceIDRef" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:element ref="CreditCard" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:element ref="Other" minOccurs="0" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation>Other payment information. Example: CHECK, CASH</xsd:documentation>
                    </xsd:annotation>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ChangeSeat" minOccurs="0" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="ElementNumber">
              <xsd:annotation>
                <xsd:documentation>Element number of the element to be changed. Example: 16</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="NewServiceElement" minOccurs="0">
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="Service">
                    <xsd:annotation>
                      <xsd:documentation>Servive details</xsd:documentation>
                    </xsd:annotation>
                    <xsd:complexType>
                      <xsd:sequence>
                        <xsd:element ref="SegmentIDRef" minOccurs="0">
                          <xsd:annotation>
                            <xsd:documentation>For booked flights this references to an existing SegmentElementNumber, e.g. "4". For a new booking it references to the flight element within this message, e.g. "F1"</xsd:documentation>
                          </xsd:annotation>
                        </xsd:element>
                        <xsd:element ref="TravelerIDRef">
                          <xsd:annotation>
                            <xsd:documentation>For booked travelers this references to an existing TravelerElementNumber, e.g. "1". For new booking reference is to the traveler element within this message, e.g. "T1"</xsd:documentation>
                          </xsd:annotation>
                        </xsd:element>
                        <xsd:element name="Description" minOccurs="0">
                          <xsd:annotation>
                            <xsd:documentation>Title description (Commercial Name) of this service - normally a one liner, e.g. "3rd Bag Fee"</xsd:documentation>
                          </xsd:annotation>
                        </xsd:element>
                        <xsd:element name="DescriptionVariable" minOccurs="0">
                          <xsd:annotation>
                            <xsd:documentation>This value is used to provide a variable value for an selected service. Sample: for a Premium Seat this will be a seat number; for a annual pass of onboard WiFi this will be the credentials, etc. Examples: "9D" "UID: GO8978 PW: 1234"</xsd:documentation>
                          </xsd:annotation>
                        </xsd:element>
                        <xsd:element name="ReferenceKey" minOccurs="0">
                          <xsd:annotation>
                            <xsd:documentation>Unique reference key. If present in pricing response messages, must be included.</xsd:documentation>
                          </xsd:annotation>
                          <xsd:simpleType>
                            <xsd:restriction base="xsd:string">
                              <xsd:minLength value="1"/>
                            </xsd:restriction>
                          </xsd:simpleType>
                        </xsd:element>
                        <xsd:element ref="ServicePrice" minOccurs="0"/>
                        <xsd:element ref="BookingInstructions" minOccurs="0"/>
                      </xsd:sequence>
                      <xsd:attribute ref="Source" use="required"/>
                      <xsd:attribute name="ReasonCode" use="required">
                        <xsd:annotation>
                          <xsd:documentation>IATA RFIC (ReasonFor IssuanceCode, a 1-character main code) Example of RFIC: A Note: Only services of same RFIC code can be combined on an EMD-A document. For example, if there are services of RFIC code "A" and "B", two separate EMD documents are needed, issuing all services of "A" and "B" on seperate docs.</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="Method">
                        <xsd:annotation>
                          <xsd:documentation>Values are: F = FareIntegrated EA = EMD Associated ES = EMD Standalone MA = Flight Associated but settled via MCO MS = Standalone but settle via MCO D = DirectSettlement</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                          <xsd:restriction base="xsd:string">
                            <xsd:enumeration value="F"/>
                            <xsd:enumeration value="EA"/>
                            <xsd:enumeration value="MA"/>
                            <xsd:enumeration value="ES"/>
                            <xsd:enumeration value="MS"/>
                            <xsd:enumeration value="D"/>
                          </xsd:restriction>
                        </xsd:simpleType>
                      </xsd:attribute>
                      <xsd:attribute name="SubCode" use="required">
                        <xsd:annotation>
                          <xsd:documentation>ATPCO RFIS (ReasonForIssuance Subcode). Example of RFIS: 0CC</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="ServiceCode">
                        <xsd:annotation>
                          <xsd:documentation>Additional unique ATPCO code. Example: OC</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="Type">
                        <xsd:annotation>
                          <xsd:documentation>Indicator if this option is a discount or a surcharge; Values are: "Discount" 1) "Surcharge" "Included" 2) "Not applicable" 3) 1) only applicable when using methof F, applying option directly to a fare (not used in an EMD solution) 2) This item is free of charge due to FQTV status or chosen Price Class 3) This item is not available/applicable due to FQTV status or chosen Price Class. Sample: Earning extra miles may only be allowed for a Top tier FQTV status and is not applicable for any other traveler.</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                          <xsd:restriction base="xsd:string">
                            <xsd:enumeration value="Discount"/>
                            <xsd:enumeration value="Surcharge"/>
                            <xsd:enumeration value="Included"/>
                            <xsd:enumeration value="Not applicable"/>
                          </xsd:restriction>
                        </xsd:simpleType>
                      </xsd:attribute>
                      <xsd:attribute name="FareBrand">
                        <xsd:annotation>
                          <xsd:documentation>Service is part of a bundle associated to this fare brand</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="ServiceType">
                        <xsd:annotation>
                          <xsd:documentation>The ATPCO defined code for the type of service (also referred to as 'Flight/Ticket/Merchandise Byte 21)': F = Flight (TypeValue=2) R = Rule Buster (Type Value = 5) T = Ticket (TypeValue=3 if EMD-S is issued, 4 if other) M = Merchandise (TypeValue=1 if EMD-S is issued, 4 if other)</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="FQTVStatus">
                        <xsd:annotation>
                          <xsd:documentation>The status (tier level) of the traveler's FQTV account. This is available as a query results against the airline's FQTV database. Samples: AA(American AAdvantage): -- Gold -- Platinum -- Executive Platinum LH (Miles and More): -- Frequent Traveller -- Senator -- HON Circle EK (Emirates Skywards): -- Silver -- Gold</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                      <xsd:attribute name="FQTVNumber">
                        <xsd:annotation>
                          <xsd:documentation>This is the actual FrequentFlyer number associated to the FQTVStatus. This will allow the POS GUI to associate the actual traveler with the respective option/price</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="NewSeat">
              <xsd:complexType>
                <xsd:choice>
                  <xsd:element ref="SeatLocation"/>
                  <xsd:element ref="Characteristic"/>
                </xsd:choice>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ChangeSeatOptimization" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Changing preferences for Seat Optimization</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="ElementNumber">
              <xsd:annotation>
                <xsd:documentation>Element number of the element to be changed. Example: 8</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="NewPreferences" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Replaces existing preferences</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="SeatPreferences">
                    <xsd:complexType>
                      <xsd:sequence>
                        <xsd:element name="Preference" maxOccurs="unbounded">
                          <xsd:annotation>
                            <xsd:documentation>Preference Codes: A = Aisle W = Window E = Exit Row H = Bulkhead F = Front of Cabin B = Back of Cabin O = Over Wing L = Left R = Right C = Center P = Powerport</xsd:documentation>
                          </xsd:annotation>
                          <xsd:complexType>
                            <xsd:simpleContent>
                              <xsd:extension base="xsd:string">
                                <xsd:attribute name="Rank">
                                  <xsd:annotation>
                                    <xsd:documentation>future use - can be used to rank the preferences for improved optimization</xsd:documentation>
                                  </xsd:annotation>
                                </xsd:attribute>
                              </xsd:extension>
                            </xsd:simpleContent>
                          </xsd:complexType>
                        </xsd:element>
                      </xsd:sequence>
                      <xsd:attribute name="AcceptPremium">
                        <xsd:annotation>
                          <xsd:documentation>Indicates the acceptance of applicable premiums Values: Y = user accepts N = no premiums accepted</xsd:documentation>
                        </xsd:annotation>
                      </xsd:attribute>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="Deactivate">
            <xsd:annotation>
              <xsd:documentation>If requested it will stop the robotoic process and remove the PNR from processing queue Possible Values: N = No (default) Y = Yes, stop optimization</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ChangeAPIS" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Changing APIS (including Secure Flight) elements</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="ElementNumber">
              <xsd:annotation>
                <xsd:documentation>Element number of the element to be changed. Example: 12</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="NewAPIS">
              <xsd:annotation>
                <xsd:documentation>APIS data group (Advanced Passenger Information System)</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element ref="TravelerIDRef"/>
                  <xsd:element ref="SegmentIDRef" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:choice>
                    <xsd:element name="PictureID">
                      <xsd:annotation>
                        <xsd:documentation>Passport or other accepted government issued picture ID. SSR DOCS.</xsd:documentation>
                      </xsd:annotation>
                      <xsd:complexType>
                        <xsd:sequence>
                          <xsd:element name="DocType" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>A - Alien resident card C - Permanent resident card P - Passport T - Refugee travel document and re-entry permit, US Travel document F - Facilitation document M - Military N - Naturalization certificate V - Border crossing card DB - Secure Flight data</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="2"/>
                                <xsd:enumeration value="A"/>
                                <xsd:enumeration value="C"/>
                                <xsd:enumeration value="P"/>
                                <xsd:enumeration value="F"/>
                                <xsd:enumeration value="M"/>
                                <xsd:enumeration value="N"/>
                                <xsd:enumeration value="V"/>
                                <xsd:enumeration value="DB"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="IssueCountry" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Country where document (for instance passport) was issued. Use valid 2 or 3 char country codes. ISO3166-Alpha2 or ISO3166-Alpha3</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="2"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="DocNumber" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Document (for instance passport) number.</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:minLength value="1"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="NationalityCountry" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Use valid 2 or 3 char country codes. ISO3166-Alpha2 or ISO3166-Alpha3</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="2"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element ref="DateOfBirth"/>
                          <xsd:element ref="Gender"/>
                          <xsd:element name="DocExpirationDate" type="xsd:date" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>This element is MANDATORY, if the DocType is one of the following: C - Permanent resident card P - Passport T - Refugee travel document and re-entry permit, US Travel document M - Military Example: 2012-05-25</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element ref="Surname"/>
                          <xsd:element ref="GivenName"/>
                          <xsd:element ref="Initial" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Traveler middle initial or spelled out middle name. Example: G</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="PassportHolder" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>In case of a multi-passenger passport this element can be used to indentify the the person entered in this SSR is the primary passport holder. The only value allowed: H. Example: H</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="1"/>
                                <xsd:enumeration value="H"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                        </xsd:sequence>
                      </xsd:complexType>
                    </xsd:element>
                    <xsd:element name="VISA">
                      <xsd:annotation>
                        <xsd:documentation>Visa information. SSR DOCO A single VISA element must be created for each passenger when submitting a redress number as it is always associated to a specific passenger.</xsd:documentation>
                      </xsd:annotation>
                      <xsd:complexType>
                        <xsd:sequence>
                          <xsd:element name="DocType" default="V" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Identifies the type of the SSR DOCO entered. Three types exist: Visa (default), Known Traveler Number and Redress Number. V - Visa K - Known Traveler R - Redress Number Example: V</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="1"/>
                                <xsd:enumeration value="V"/>
                                <xsd:enumeration value="K"/>
                                <xsd:enumeration value="R"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="PlaceOfBirth" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Mandatory for VISA</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:minLength value="1"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="DocNumber">
                            <xsd:annotation>
                              <xsd:documentation>Mandatory for all types. This is the VISA document number, the RedressNumber or the KnownTraveler number</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:minLength value="1"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="PlaceOfIssue" type="xsd:string" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Mandatory for VISA Example: Frankfurt</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="IssueDate" type="xsd:date" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Mandatory for VISA</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="IssuedForCountry" minOccurs="0">
                            <xsd:annotation>
                              <xsd:documentation>Mandatory for VISA Use valid 2 or 3 char country codes. ISO3166-Alpha2 or ISO3166-Alpha3 Example: DE</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:minLength value="2"/>
                                <xsd:maxLength value="3"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="InfantOnLap" minOccurs="0">
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="1"/>
                                <xsd:enumeration value="Y"/>
                                <xsd:enumeration value="N"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                        </xsd:sequence>
                      </xsd:complexType>
                    </xsd:element>
                    <xsd:element name="StayingAt">
                      <xsd:annotation>
                        <xsd:documentation>Address while in country. SSR DOCA</xsd:documentation>
                      </xsd:annotation>
                      <xsd:complexType>
                        <xsd:sequence>
                          <xsd:element name="Address" type="xsd:string">
                            <xsd:annotation>
                              <xsd:documentation>Street or PO Box address. Example: 1234 Main Street</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="City" type="xsd:string">
                            <xsd:annotation>
                              <xsd:documentation>City name. Example: NY</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="StateCode" type="xsd:string">
                            <xsd:annotation>
                              <xsd:documentation>State code. Example: NY</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="CountryCode" type="xsd:string">
                            <xsd:annotation>
                              <xsd:documentation>Country code. Example: US</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="PostalCode" type="xsd:string">
                            <xsd:annotation>
                              <xsd:documentation>Postal code or zip code. Example: 12345</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                          <xsd:element name="InfantOnLap" minOccurs="0">
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="1"/>
                                <xsd:enumeration value="Y"/>
                                <xsd:enumeration value="N"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                        </xsd:sequence>
                        <xsd:attribute name="AddressType">
                          <xsd:annotation>
                            <xsd:documentation>Valid address types are: R - Residence Address D - Destination Address</xsd:documentation>
                          </xsd:annotation>
                          <xsd:simpleType>
                            <xsd:restriction base="xsd:string">
                              <xsd:length value="1"/>
                              <xsd:enumeration value="R"/>
                              <xsd:enumeration value="D"/>
                            </xsd:restriction>
                          </xsd:simpleType>
                        </xsd:attribute>
                      </xsd:complexType>
                    </xsd:element>
                  </xsd:choice>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="Display" minOccurs="0"/>
      <xsd:element ref="EndTransaction" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="version" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation>Version number. Example: 1.0</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element RecordLocator
Namespace No namespace
Annotations
PNR record locator to be changed.  Example: VP1256
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 6
maxLength 6
Used by
Element PNRChangeRQ
Source
<xsd:element name="RecordLocator">
  <xsd:annotation>
    <xsd:documentation>PNR record locator to be changed. Example: VP1256</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="6"/>
      <xsd:maxLength value="6"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element SaleInfo
Namespace No namespace
Annotations
Sale information group
Diagram
Diagram PNRChangeRQ.tmp#CityCode PNRChangeRQ.tmp#CountryCode PNRChangeRQ.tmp#CurrencyCode
Properties
content: complex
Used by
Element PNRChangeRQ
Model CityCode{0,1} , CountryCode{0,1} , CurrencyCode{0,1}
Children CityCode, CountryCode, CurrencyCode
Instance
<SaleInfo>
  <CityCode>{0,1}</CityCode>
  <CountryCode>{0,1}</CountryCode>
  <CurrencyCode NumberOfDecimals="">{0,1}</CurrencyCode>
</SaleInfo>
Source
<xsd:element name="SaleInfo">
  <xsd:annotation>
    <xsd:documentation>Sale information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="CityCode" minOccurs="0"/>
      <xsd:element ref="CountryCode" minOccurs="0"/>
      <xsd:element ref="CurrencyCode" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CityCode
Namespace No namespace
Annotations
City code.  Example: MIA
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="CityCode" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>City code. Example: MIA</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CountryCode
Namespace No namespace
Annotations
Country code.  Example: US
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
maxLength 2
Used by
Source
<xsd:element name="CountryCode">
  <xsd:annotation>
    <xsd:documentation>Country code. Example: US</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2"/>
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CurrencyCode
Namespace No namespace
Annotations
Currency code.  Example: USD
Diagram
Diagram PNRChangeRQ.tmp#CurrencyCodeType_NumberOfDecimals PNRChangeRQ.tmp#CurrencyCodeType PNRChangeRQ.tmp#CurrencyCode_NumberOfDecimals
Type restriction of CurrencyCodeType
Type hierarchy
Properties
content: complex
Used by
Attributes
QName Type Fixed Default Use Annotation
NumberOfDecimals xsd:integer required
Decimal position in fare amount.  Example: 2
Source
<xsd:element name="CurrencyCode">
  <xsd:annotation>
    <xsd:documentation>Currency code. Example: USD</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:restriction base="CurrencyCodeType">
        <xsd:pattern value="[A-Z0-9]{3}"/>
        <xsd:attribute name="NumberOfDecimals" type="xsd:integer" use="required">
          <xsd:annotation>
            <xsd:documentation>Decimal position in fare amount. Example: 2</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TicketingInfo
Namespace No namespace
Annotations
Ticketing information group
Diagram
Diagram PNRChangeRQ.tmp#CityCode PNRChangeRQ.tmp#CountryCode
Properties
content: complex
Used by
Element PNRChangeRQ
Model CityCode{0,1} , CountryCode{0,1}
Children CityCode, CountryCode
Instance
<TicketingInfo>
  <CityCode>{0,1}</CityCode>
  <CountryCode>{0,1}</CountryCode>
</TicketingInfo>
Source
<xsd:element name="TicketingInfo">
  <xsd:annotation>
    <xsd:documentation>Ticketing information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="CityCode" minOccurs="0"/>
      <xsd:element ref="CountryCode" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ChangeTraveler
Namespace No namespace
Annotations
Change traveler group
Diagram
Diagram PNRChangeRQ.tmp#NewTraveler
Properties
content: complex
Used by
Element PNRChangeRQ
Model NewTraveler
Children NewTraveler
Instance
<ChangeTraveler>
  <NewTraveler Type="">{1,1}</NewTraveler>
</ChangeTraveler>
Source
<xsd:element name="ChangeTraveler">
  <xsd:annotation>
    <xsd:documentation>Change traveler group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="NewTraveler"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element NewTraveler
Namespace No namespace
Annotations
New traveler information group
Diagram
Diagram PNRChangeRQ.tmp#NewTraveler_Type PNRChangeRQ.tmp#ElementNumber PNRChangeRQ.tmp#TattooNumber PNRChangeRQ.tmp#TravelerName PNRChangeRQ.tmp#Infant PNRChangeRQ.tmp#FrequentTravelerGroup
Properties
content: complex
Used by
Element ChangeTraveler
Model (ElementNumber | TattooNumber) , TravelerName , Infant{0,1} , FrequentTravelerGroup*
Children ElementNumber, FrequentTravelerGroup, Infant, TattooNumber, TravelerName
Instance
<NewTraveler Type="">
  <ElementNumber>{1,1}</ElementNumber>
  <TattooNumber>{1,1}</TattooNumber>
  <TravelerName>{1,1}</TravelerName>
  <Infant InfantIndicator="" Type="">{0,1}</Infant>
  <FrequentTravelerGroup>{0,unbounded}</FrequentTravelerGroup>
</NewTraveler>
Attributes
QName Type Fixed Default Use Annotation
Type xsd:string required
Passenger type.  Values are:
ADT = Adult
CHD = Child
YTH = Youth
MIL = Military
GOV = Government
SRC = Senior Citizen
STD = Student
Example: ADT
Source
<xsd:element name="NewTraveler">
  <xsd:annotation>
    <xsd:documentation>New traveler information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:choice>
        <xsd:element ref="ElementNumber"/>
        <xsd:element ref="TattooNumber"/>
      </xsd:choice>
      <xsd:element ref="TravelerName"/>
      <xsd:element ref="Infant" minOccurs="0"/>
      <xsd:element ref="FrequentTravelerGroup" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    <xsd:attribute name="Type" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>Passenger type. Values are: ADT = Adult CHD = Child YTH = Youth MIL = Military GOV = Government SRC = Senior Citizen STD = Student Example: ADT</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ElementNumber
Namespace No namespace
Annotations
Element number of the element to be changed. Example: 1.1
Diagram
Diagram
Type extension of xsd:string
Properties
content: complex
Used by
Source
<xsd:element name="ElementNumber">
  <xsd:annotation>
    <xsd:documentation>Element number of the element to be changed. Example: 1.1</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string"/>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TattooNumber
Namespace No namespace
Annotations
Tattoo number to change in PNR.  Example: 2
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="TattooNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Tattoo number to change in PNR. Example: 2</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TravelerName
Namespace No namespace
Annotations
Name group
Diagram
Diagram PNRChangeRQ.tmp#Surname PNRChangeRQ.tmp#GivenName PNRChangeRQ.tmp#Initial PNRChangeRQ.tmp#Title PNRChangeRQ.tmp#Age PNRChangeRQ.tmp#DateOfBirth PNRChangeRQ.tmp#Gender
Properties
content: complex
Used by
Element NewTraveler
Model Surname , GivenName , Initial{0,1} , Title{0,1} , (Age{0,1} | DateOfBirth{0,1}) , Gender{0,1}
Children Age, DateOfBirth, Gender, GivenName, Initial, Surname, Title
Instance
<TravelerName>
  <Surname>{1,1}</Surname>
  <GivenName>{1,1}</GivenName>
  <Initial>{0,1}</Initial>
  <Title>{0,1}</Title>
  <Age>{0,1}</Age>
  <DateOfBirth>{0,1}</DateOfBirth>
  <Gender>{0,1}</Gender>
</TravelerName>
Source
<xsd:element name="TravelerName">
  <xsd:annotation>
    <xsd:documentation>Name group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Surname"/>
      <xsd:element ref="GivenName"/>
      <xsd:element ref="Initial" minOccurs="0"/>
      <xsd:element ref="Title" minOccurs="0"/>
      <xsd:choice>
        <xsd:element ref="Age" minOccurs="0"/>
        <xsd:element ref="DateOfBirth" minOccurs="0"/>
      </xsd:choice>
      <xsd:element ref="Gender" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Surname
Namespace No namespace
Annotations
Traveler family (last) name.  Example: SMITH
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="Surname" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler family (last) name. Example: SMITH</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element GivenName
Namespace No namespace
Annotations
Traveler given (first) name.  Example: JANE
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="GivenName" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler given (first) name. Example: JANE</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Initial
Namespace No namespace
Annotations
Traveler middle initial.  Example: G
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="Initial" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler middle initial. Example: G</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Title
Namespace No namespace
Annotations
Traveler title.  Example: MISS
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element TravelerName
Source
<xsd:element name="Title" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler title. Example: MISS</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Age
Namespace No namespace
Annotations
Traveler age.  Age is not supported by Galileo.  Example: 01
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element TravelerName
Source
<xsd:element name="Age" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Traveler age. Age is not supported by Galileo. Example: 01</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element DateOfBirth
Namespace No namespace
Annotations
Traveler birth date in ISO 8601 format (yyyy-mm-dd).  Date of birth is not supported in Galileo.  Example: 1978-06-09
Diagram
Diagram
Type xsd:date
Properties
content: simple
Used by
Source
<xsd:element name="DateOfBirth" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Traveler birth date in ISO 8601 format (yyyy-mm-dd). Date of birth is not supported in Galileo. Example: 1978-06-09</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Gender
Namespace No namespace
Annotations
Traveler gender.  
Values are: 
F = Female 
M = Male.  
Example: M
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
enumeration F
enumeration M
Used by
Source
<xsd:element name="Gender">
  <xsd:annotation>
    <xsd:documentation>Traveler gender. Values are: F = Female M = Male. Example: M</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="F"/>
      <xsd:enumeration value="M"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Infant
Namespace No namespace
Annotations
Information for the infant traveling with the passenger and not requiring a seat.
Diagram
Diagram PNRChangeRQ.tmp#Infant_Type PNRChangeRQ.tmp#Infant_InfantIndicator PNRChangeRQ.tmp#ElementNumber PNRChangeRQ.tmp#TattooNumber PNRChangeRQ.tmp#Surname PNRChangeRQ.tmp#GivenName PNRChangeRQ.tmp#AgeInMonths PNRChangeRQ.tmp#DateOfBirth PNRChangeRQ.tmp#Gender
Properties
content: complex
Used by
Element NewTraveler
Model (ElementNumber | TattooNumber) , Surname , GivenName , (AgeInMonths | DateOfBirth) , Gender{0,1}
Children AgeInMonths, DateOfBirth, ElementNumber, Gender, GivenName, Surname, TattooNumber
Instance
<Infant InfantIndicator="" Type="">
  <ElementNumber>{1,1}</ElementNumber>
  <TattooNumber>{1,1}</TattooNumber>
  <Surname>{1,1}</Surname>
  <GivenName>{1,1}</GivenName>
  <AgeInMonths>{1,1}</AgeInMonths>
  <DateOfBirth>{1,1}</DateOfBirth>
  <Gender>{0,1}</Gender>
</Infant>
Attributes
QName Type Fixed Default Use Annotation
InfantIndicator optional
Possible Values:

A = Adding an INF association

C = Changing elements in the Infant node
Type xsd:string optional
Infant PAX type. Although regular INF type will be automatically set, this optional attribute would show if present a different PTC for infants. Particularly useful for bulk contracts - JNF pax type. 
Example: JNF
Source
<xsd:element name="Infant">
  <xsd:annotation>
    <xsd:documentation>Information for the infant traveling with the passenger and not requiring a seat.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:choice minOccurs="0">
        <xsd:element ref="ElementNumber"/>
        <xsd:element ref="TattooNumber"/>
      </xsd:choice>
      <xsd:element ref="Surname"/>
      <xsd:element ref="GivenName"/>
      <xsd:choice minOccurs="0">
        <xsd:element ref="AgeInMonths"/>
        <xsd:element ref="DateOfBirth"/>
      </xsd:choice>
      <xsd:element ref="Gender" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="Type" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation>Infant PAX type. Although regular INF type will be automatically set, this optional attribute would show if present a different PTC for infants. Particularly useful for bulk contracts - JNF pax type. Example: JNF</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="InfantIndicator">
      <xsd:annotation>
        <xsd:documentation>Possible Values: A = Adding an INF association C = Changing elements in the Infant node</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element AgeInMonths
Namespace No namespace
Annotations
Infant age specified in months. Example: 5
Diagram
Diagram
Type restriction of xsd:integer
Properties
content: simple
Facets
maxInclusive 23
minInclusive 0
pattern ([\-+]?[0-9]+) & ([0-2]?[0-9])
Used by
Element Infant
Source
<xsd:element name="AgeInMonths">
  <xsd:annotation>
    <xsd:documentation>Infant age specified in months. Example: 5</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:integer">
      <xsd:minInclusive value="0"/>
      <xsd:maxInclusive value="23"/>
      <xsd:pattern value="[0-2]?[0-9]"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FrequentTravelerGroup
Namespace No namespace
Annotations
Frequent traveler group
Diagram
Diagram PNRChangeRQ.tmp#ProgramInformation
Properties
content: complex
Used by
Element NewTraveler
Model ProgramInformation+
Children ProgramInformation
Instance
<FrequentTravelerGroup>
  <ProgramInformation FrequentFlyerID="">{1,unbounded}</ProgramInformation>
</FrequentTravelerGroup>
Source
<xsd:element name="FrequentTravelerGroup">
  <xsd:annotation>
    <xsd:documentation>Frequent traveler group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="ProgramInformation" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProgramInformation
Namespace No namespace
Annotations
Program information group
Diagram
Diagram PNRChangeRQ.tmp#ProgramInformation_FrequentFlyerID PNRChangeRQ.tmp#FFCompanyCode PNRChangeRQ.tmp#FFProgramName PNRChangeRQ.tmp#FFNumber PNRChangeRQ.tmp#FFSharedProgramName PNRChangeRQ.tmp#FFLoyaltyLevel
Properties
content: complex
Used by
Model FFCompanyCode , FFProgramName , FFNumber , FFSharedProgramName{0,1} , FFLoyaltyLevel{0,1}
Children FFCompanyCode, FFLoyaltyLevel, FFNumber, FFProgramName, FFSharedProgramName
Instance
<ProgramInformation FrequentFlyerID="">
  <FFCompanyCode>{1,1}</FFCompanyCode>
  <FFProgramName>{1,1}</FFProgramName>
  <FFNumber>{1,1}</FFNumber>
  <FFSharedProgramName>{0,1}</FFSharedProgramName>
  <FFLoyaltyLevel>{0,1}</FFLoyaltyLevel>
</ProgramInformation>
Attributes
QName Type Fixed Default Use Annotation
FrequentFlyerID xsd:string optional
Unique frequent flyer identification.  Example: FF1
Source
<xsd:element name="ProgramInformation">
  <xsd:annotation>
    <xsd:documentation>Program information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="FFCompanyCode"/>
      <xsd:element ref="FFProgramName"/>
      <xsd:element ref="FFNumber"/>
      <xsd:element ref="FFSharedProgramName" minOccurs="0"/>
      <xsd:element ref="FFLoyaltyLevel" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="FrequentFlyerID" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation>Unique frequent flyer identification. Example: FF1</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FFCompanyCode
Namespace No namespace
Annotations
Frequent flyer company code.  Example: AF
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFCompanyCode" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer company code. Example: AF</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FFProgramName
Namespace No namespace
Annotations
Frequent flyer program name.  Example: Frequence Plus
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFProgramName" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer program name. Example: Frequence Plus</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FFNumber
Namespace No namespace
Annotations
Frequent flyer number.  Example: 0956301007
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer number. Example: 0956301007</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FFSharedProgramName
Namespace No namespace
Annotations
Frequent flyer shared program name.  Example: Delta Miles
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFSharedProgramName" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer shared program name. Example: Delta Miles</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FFLoyaltyLevel
Namespace No namespace
Annotations
Frequent flyer loyalty level.  Example: Blue
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="FFLoyaltyLevel" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Frequent flyer loyalty level. Example: Blue</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeAir
Namespace No namespace
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeAir_AutoExchange PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeAir_SegmentIDRef PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeAir_NewStatusCode PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeAir_NewClassOfService PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeAir_DepartureDate
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model SegmentIDRef+ , (NewStatusCode | NewClassOfService | DepartureDate{0,0})
Children DepartureDate, NewClassOfService, NewStatusCode, SegmentIDRef
Instance
<ChangeAir AutoExchange="">
  <SegmentIDRef Source="" SourceRef="">{1,unbounded}</SegmentIDRef>
  <NewStatusCode>{1,1}</NewStatusCode>
  <NewClassOfService>{1,1}</NewClassOfService>
  <DepartureDate>{0,0}</DepartureDate>
</ChangeAir>
Attributes
QName Type Fixed Default Use Annotation
AutoExchange optional
Allowed value = "Y"

Identifies this request as a request to be handled by an auto-exchange process (e.g. ReShop by ITA).
Source
<xsd:element name="ChangeAir" minOccurs="0" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="SegmentIDRef" maxOccurs="unbounded">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute ref="Source"/>
              <xsd:attribute ref="SourceRef"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:choice>
        <xsd:element name="NewStatusCode">
          <xsd:annotation>
            <xsd:documentation>New status code of the segment as referenced in SegmentIDRef. The status codes are typical GDS status code. However, mostly status changes involve changing staus to HK or RR Example: RR, HK</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:minLength value="1"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NewClassOfService">
          <xsd:annotation>
            <xsd:documentation>New calss of service of the segment as referenced in SegmentIDRef. Note that for married segment the change should be done for all segments in a marriage. Example: C</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:maxLength value="2"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:element>
        <xsd:element name="DepartureDate" type="xsd:date" minOccurs="0" maxOccurs="0">
          <xsd:annotation>
            <xsd:documentation>NOT IMPLEMENTED YET</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
      </xsd:choice>
    </xsd:sequence>
    <xsd:attribute name="AutoExchange">
      <xsd:annotation>
        <xsd:documentation>Allowed value = "Y" Identifies this request as a request to be handled by an auto-exchange process (e.g. ReShop by ITA).</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeAir / SegmentIDRef
Namespace No namespace
Diagram
Diagram PNRChangeRQ.tmp#Source PNRChangeRQ.tmp#SourceRef
Type extension of xsd:string
Properties
content: complex
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
Source restriction of xsd:string optional
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
SourceRef restriction of xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="SegmentIDRef" maxOccurs="unbounded">
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute ref="Source"/>
        <xsd:attribute ref="SourceRef"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeAir / NewStatusCode
Namespace No namespace
Annotations
New status code of the segment as referenced in SegmentIDRef. The status codes are typical GDS status code. However, mostly status changes involve changing staus to HK or RR
Example: RR, HK
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="NewStatusCode">
  <xsd:annotation>
    <xsd:documentation>New status code of the segment as referenced in SegmentIDRef. The status codes are typical GDS status code. However, mostly status changes involve changing staus to HK or RR Example: RR, HK</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeAir / NewClassOfService
Namespace No namespace
Annotations
New calss of service of the segment as referenced in SegmentIDRef. Note that for married segment the change should be done for all segments in a marriage.
Example: C
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
maxLength 2
Source
<xsd:element name="NewClassOfService">
  <xsd:annotation>
    <xsd:documentation>New calss of service of the segment as referenced in SegmentIDRef. Note that for married segment the change should be done for all segments in a marriage. Example: C</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeAir / DepartureDate
Namespace No namespace
Annotations
NOT IMPLEMENTED YET
Diagram
Diagram
Type xsd:date
Properties
content: simple
minOccurs: 0
maxOccurs: 0
Source
<xsd:element name="DepartureDate" type="xsd:date" minOccurs="0" maxOccurs="0">
  <xsd:annotation>
    <xsd:documentation>NOT IMPLEMENTED YET</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeFareGroup
Namespace No namespace
Annotations
Change applies to entire fare group as referenced by attribute @FareNumber

Note: for any changes to the TravelerGroup use the "ChangeStoredPrice" node
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_FareNumber PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_TravelStats
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model TravelStats{0,1}
Children TravelStats
Instance
<ChangeFareGroup FareNumber="">
  <TravelStats>{0,1}</TravelStats>
</ChangeFareGroup>
Attributes
QName Type Fixed Default Use Annotation
FareNumber xsd:string required
FareNumber of FareGroup to be modified.  

Example: 2
Source
<xsd:element name="ChangeFareGroup" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Change applies to entire fare group as referenced by attribute @FareNumber Note: for any changes to the TravelerGroup use the "ChangeStoredPrice" node</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="TravelStats" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="PurposeCode" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="DestinationCode" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="FareNumber" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>FareNumber of FareGroup to be modified. Example: 2</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeFareGroup / TravelStats
Namespace No namespace
Annotations
Statistical data as needed for BSP and/or ARC reporting
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_TravelStats_PurposeCode PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_PNRChangeRQ_PNRChangeRQ_ChangeFareGroup_TravelStats_DestinationCode
Properties
content: complex
minOccurs: 0
Model PurposeCode{0,1} , DestinationCode{0,1}
Children DestinationCode, PurposeCode
Instance
<TravelStats>
  <PurposeCode>{0,1}</PurposeCode>
  <DestinationCode>{0,1}</DestinationCode>
</TravelStats>
Source
<xsd:element name="TravelStats" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="PurposeCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="DestinationCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeFareGroup / TravelStats / PurposeCode
Namespace No namespace
Annotations
Purpose Code.
Valid values:
1 = Business
2 = Pleasure
3 = Charter

Canadian requirement
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="PurposeCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeFareGroup / TravelStats / DestinationCode
Namespace No namespace
Annotations
1 = Mexico, Costa Rica, Central America, Canal zone
2 = Islands and countries of the Caribbean, Bermuda, including PR, VI
3 = South America
4 = Europe incl Morocco, Tunisia, Algeria, Greenland
5 = Africa
6 = Middle East (western Asia) 
7 = Asia including India
8 = Australia, New Zealand. Pacific islands incl Hawaii,
excluding Guam
0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) 

Canadian requirement
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="DestinationCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice
Namespace No namespace
Annotations
Used to modify a stored fare in PNR at the TravelerGroup level (identified by the PTC). 

Use one ChangeStoredPrice per fare you want to modify. See attribute FareNumber. The value of this attribute is to be taken from PNRViewRS/FareGroup/FareNumber.

In general all values entered in this section will replace values in stored fare (if any).
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_FareNumber PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TravelerType PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_RelatedSegment PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NewCommission PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TourCode PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TicketType PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_Endorsement PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NetRemit PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TravelStats
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model RelatedSegment* , NewCommission* , TourCode{0,1} , TicketType{0,1} , Endorsement* , NetRemit{0,1} , TravelStats{0,1}
Children Endorsement, NetRemit, NewCommission, RelatedSegment, TicketType, TourCode, TravelStats
Instance
<ChangeStoredPrice FareNumber="" TravelerType="">
  <RelatedSegment>{0,unbounded}</RelatedSegment>
  <NewCommission RuleCode="" Type="">{0,unbounded}</NewCommission>
  <TourCode>{0,1}</TourCode>
  <TicketType>{0,1}</TicketType>
  <Endorsement Type="">{0,unbounded}</Endorsement>
  <NetRemit NRIndicator="">{0,1}</NetRemit>
  <TravelStats>{0,1}</TravelStats>
</ChangeStoredPrice>
Attributes
QName Type Fixed Default Use Annotation
FareNumber xsd:string required
FareNumber of FareGroup to be deleted from PNR.  Example: 2
TravelerType xsd:string required
PAX Type requested. This value is used as a key to identify the TravelerGroup within the FareGroup to be modified.
Source
<xsd:element name="ChangeStoredPrice" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Used to modify a stored fare in PNR at the TravelerGroup level (identified by the PTC). Use one ChangeStoredPrice per fare you want to modify. See attribute FareNumber. The value of this attribute is to be taken from PNRViewRS/FareGroup/FareNumber. In general all values entered in this section will replace values in stored fare (if any).</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="RelatedSegment" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>These are the values of the RelatedSegment element(s) of the respective Faregroup/ TravelerGroup to be changed.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="SegmentIDRef"/>
            <xsd:element ref="TicketDesignator" minOccurs="0"/>
            <xsd:element ref="BaggageAllowance" minOccurs="0"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="NewCommission" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Overwrites a commission stored w/ a fare and sets it to the value of this element. Commission percentage or amount. Commission will be in the samecurrency as the fare this commission applies to. Number of digits after decimal point is governed by the CurrencyCode element in the FareGroup this commission is associated with. See PNRViewRS/FareGroup/Commission/@NumberOfDecimals Amadeus - the new commission will replace the old commission. No repricing will take place since commissions are maintained outside of TST's. Apollo/Galileo - TBD Sabre - Note that on Sabre if PQ is used to stored automated fares entering commission will result in a repricing of the fare which potentially could lead to a different fare as previously stored. Worldspan - TBD Example: 2000</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="CommissionType">
              <xsd:attribute name="RuleCode" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation>System defined commission processing code. Can be retrieved in RevenueStructureRS Example: XYZ. Note: integration function w/ backoffice system. Not currently supported by XX1.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="TourCode" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>FUTURE USE. Tour code identifier. Example: ITGF12</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="TicketType" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>FUTURE USE. identifies First, Bulk or Tour ticket and maps to @Tour attribute in PNRViewRS Example: U (Bulk)</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Endorsement" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>FUTURE USE. Creates endorsements associated with the fare. See Type attribute for details of endorsement types. In general, on tickets issued manual endorsements will override those automatically generated by the GDS/CRS, which are then no longer visible in the PNR. However, if a GDS (e.g. Apollo, Sabre) returns both generated and manual endorsements stored w/ a fare, both will be present in PNRViewRS distinguished by their Type. Amadeus allows only either-or mode - either manual or automatically generated enorsements will be present in the PNR. Which endorsements will be printed on the ticket depends on GDS-specific logic. As a rule of thumb: manual will override generated.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="BasicEndorsement">
              <xsd:attribute name="Type" use="required">
                <xsd:annotation>
                  <xsd:documentation>Identifies the creation mode of this line. Values are: M - manual override entered by agent P - manual agent entered to be appended to the automatically generated line.</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:length value="1"/>
                    <xsd:enumeration value="M"/>
                    <xsd:enumeration value="P"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:attribute>
            </xsd:extension>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="NetRemit" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Net remit group.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="APBC" type="xsd:positiveInteger" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>This IATA term stands for 'Amount Paid By Customer' and is needed for Net Remit methods 2A, 2E. Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 57500</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="AEBA" type="xsd:positiveInteger" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>This IATA term stands for 'Amount Entered By Agent' and is needed for Net Remit methods 2A, 2E Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 50500</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="NRIndicator" type="xsd:string" use="required"/>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="TravelStats" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="PurposeCode" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="DestinationCode" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="FareNumber" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>FareNumber of FareGroup to be deleted from PNR. Example: 2</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="TravelerType" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>PAX Type requested. This value is used as a key to identify the TravelerGroup within the FareGroup to be modified.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / RelatedSegment
Namespace No namespace
Annotations
These are the values of the RelatedSegment element(s) of the respective Faregroup/ TravelerGroup to be changed.
Diagram
Diagram PNRChangeRQ.tmp#SegmentIDRef PNRChangeRQ.tmp#TicketDesignator PNRChangeRQ.tmp#BaggageAllowance
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model SegmentIDRef , TicketDesignator{0,1} , BaggageAllowance{0,1}
Children BaggageAllowance, SegmentIDRef, TicketDesignator
Instance
<RelatedSegment>
  <SegmentIDRef>{1,1}</SegmentIDRef>
  <TicketDesignator>{0,1}</TicketDesignator>
  <BaggageAllowance>{0,1}</BaggageAllowance>
</RelatedSegment>
Source
<xsd:element name="RelatedSegment" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>These are the values of the RelatedSegment element(s) of the respective Faregroup/ TravelerGroup to be changed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="SegmentIDRef"/>
      <xsd:element ref="TicketDesignator" minOccurs="0"/>
      <xsd:element ref="BaggageAllowance" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element SegmentIDRef
Namespace No namespace
Annotations
ID reference used to asscociate this item to a segment.  No comma separeted lists and no ranges supported.    Example: F1
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="SegmentIDRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>ID reference used to asscociate this item to a segment. No comma separeted lists and no ranges supported. Example: F1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element TicketDesignator
Namespace No namespace
Annotations
Ticket designator to price.  Example: AM10AC
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="TicketDesignator" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Ticket designator to price. Example: AM10AC</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BaggageAllowance
Namespace No namespace
Annotations
Baggage allowance.  
PC = per piece
1PC = 1 piece
2PC = 2 pieces
nn = per weight
(nn is the weight limit).
Example: 2PC
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="BaggageAllowance" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Baggage allowance. PC = per piece 1PC = 1 piece 2PC = 2 pieces nn = per weight (nn is the weight limit). Example: 2PC</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / NewCommission
Namespace No namespace
Annotations
Overwrites a commission stored w/ a fare and sets it to the value of this element.
Commission percentage or amount. Commission will be in the samecurrency as the fare this commission applies to. Number of digits after decimal point is governed by the CurrencyCode element in the FareGroup this commission is associated with. See PNRViewRS/FareGroup/Commission/@NumberOfDecimals 


Amadeus - the new commission will replace the old commission. No repricing will take place since commissions are maintained outside of TST's.

Apollo/Galileo - TBD

Sabre - Note that on Sabre if PQ is used to stored automated fares entering commission will result in a repricing of the fare which potentially could lead to a different fare as previously stored.

Worldspan - TBD

Example: 2000
Diagram
Diagram PNRChangeRQ.tmp#positiveDecimal PNRChangeRQ.tmp#CommissionType_Type PNRChangeRQ.tmp#CommissionType PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NewCommission_RuleCode
Type extension of CommissionType
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
RuleCode xsd:string optional
System defined commission processing code. Can be retrieved in RevenueStructureRS
Example: XYZ.

Note: integration function w/ backoffice system. Not currently supported by XX1.
Type restriction of xsd:string required
Commission type.  Values are: P = Percent, A = Amount  Example: A
Source
<xsd:element name="NewCommission" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Overwrites a commission stored w/ a fare and sets it to the value of this element. Commission percentage or amount. Commission will be in the samecurrency as the fare this commission applies to. Number of digits after decimal point is governed by the CurrencyCode element in the FareGroup this commission is associated with. See PNRViewRS/FareGroup/Commission/@NumberOfDecimals Amadeus - the new commission will replace the old commission. No repricing will take place since commissions are maintained outside of TST's. Apollo/Galileo - TBD Sabre - Note that on Sabre if PQ is used to stored automated fares entering commission will result in a repricing of the fare which potentially could lead to a different fare as previously stored. Worldspan - TBD Example: 2000</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="CommissionType">
        <xsd:attribute name="RuleCode" type="xsd:string">
          <xsd:annotation>
            <xsd:documentation>System defined commission processing code. Can be retrieved in RevenueStructureRS Example: XYZ. Note: integration function w/ backoffice system. Not currently supported by XX1.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / TourCode
Namespace No namespace
Annotations
FUTURE USE.

Tour code identifier. Example: ITGF12
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="TourCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>FUTURE USE. Tour code identifier. Example: ITGF12</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / TicketType
Namespace No namespace
Annotations
FUTURE USE.

identifies First, Bulk or Tour ticket and maps to @Tour attribute in PNRViewRS
Example: U (Bulk)
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="TicketType" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>FUTURE USE. identifies First, Bulk or Tour ticket and maps to @Tour attribute in PNRViewRS Example: U (Bulk)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / Endorsement
Namespace No namespace
Annotations
FUTURE USE.

Creates endorsements associated with the fare. See Type attribute  for details of endorsement types.

In general, on tickets issued manual endorsements will override those automatically generated by the GDS/CRS, which are then no longer visible in the PNR. 

However, if a GDS (e.g. Apollo, Sabre) returns both generated and manual endorsements stored w/ a fare, both will be present in PNRViewRS distinguished by their Type.

Amadeus allows only either-or mode - either manual or automatically generated enorsements will be present in the PNR.

Which endorsements will be printed on the ticket depends on GDS-specific logic. As a rule of thumb: manual will override generated.
Diagram
Diagram PNRChangeRQ.tmp#BasicEndorsement_Text PNRChangeRQ.tmp#BasicEndorsement PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_Endorsement_Type
Type extension of BasicEndorsement
Type hierarchy
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model Text
Children Text
Instance
<Endorsement Type="">
  <Text>{1,1}</Text>
</Endorsement>
Attributes
QName Type Fixed Default Use Annotation
Type restriction of xsd:string required
Identifies the creation mode of this line. Values are:

M - manual override entered by agent
P - manual agent entered to be appended to the automatically generated line.
Source
<xsd:element name="Endorsement" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>FUTURE USE. Creates endorsements associated with the fare. See Type attribute for details of endorsement types. In general, on tickets issued manual endorsements will override those automatically generated by the GDS/CRS, which are then no longer visible in the PNR. However, if a GDS (e.g. Apollo, Sabre) returns both generated and manual endorsements stored w/ a fare, both will be present in PNRViewRS distinguished by their Type. Amadeus allows only either-or mode - either manual or automatically generated enorsements will be present in the PNR. Which endorsements will be printed on the ticket depends on GDS-specific logic. As a rule of thumb: manual will override generated.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="BasicEndorsement">
        <xsd:attribute name="Type" use="required">
          <xsd:annotation>
            <xsd:documentation>Identifies the creation mode of this line. Values are: M - manual override entered by agent P - manual agent entered to be appended to the automatically generated line.</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:length value="1"/>
              <xsd:enumeration value="M"/>
              <xsd:enumeration value="P"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element BasicEndorsement / Text
Namespace No namespace
Annotations
Endorsement text.
Diagram
Diagram PNRChangeRQ.tmp#FreeFormTextField
Type FreeFormTextField
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Text" type="FreeFormTextField">
  <xsd:annotation>
    <xsd:documentation>Endorsement text.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / NetRemit
Namespace No namespace
Annotations
Net remit group.
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NetRemit_NRIndicator PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NetRemit_APBC PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_NetRemit_AEBA
Properties
content: complex
minOccurs: 0
Model APBC{0,1} , AEBA{0,1}
Children AEBA, APBC
Instance
<NetRemit NRIndicator="">
  <APBC>{0,1}</APBC>
  <AEBA>{0,1}</AEBA>
</NetRemit>
Attributes
QName Type Fixed Default Use Annotation
NRIndicator xsd:string required
Source
<xsd:element name="NetRemit" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Net remit group.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="APBC" type="xsd:positiveInteger" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>This IATA term stands for 'Amount Paid By Customer' and is needed for Net Remit methods 2A, 2E. Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 57500</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="AEBA" type="xsd:positiveInteger" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>This IATA term stands for 'Amount Entered By Agent' and is needed for Net Remit methods 2A, 2E Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 50500</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="NRIndicator" type="xsd:string" use="required"/>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / NetRemit / APBC
Namespace No namespace
Annotations
This IATA term stands for 'Amount Paid By Customer' and is needed for Net Remit methods 2A, 2E. Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element.
Example: 57500
Diagram
Diagram
Type xsd:positiveInteger
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="APBC" type="xsd:positiveInteger" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>This IATA term stands for 'Amount Paid By Customer' and is needed for Net Remit methods 2A, 2E. Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 57500</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / NetRemit / AEBA
Namespace No namespace
Annotations
This IATA term stands for 'Amount Entered By Agent' and is needed for Net Remit methods 2A, 2E
Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element.
Example: 50500
Diagram
Diagram
Type xsd:positiveInteger
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="AEBA" type="xsd:positiveInteger" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>This IATA term stands for 'Amount Entered By Agent' and is needed for Net Remit methods 2A, 2E Note that currency and decimal point are governed by the Currency alement definition of the FareGroup/Currency element. Example: 50500</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / TravelStats
Namespace No namespace
Annotations
Statistical data as needed for BSP and/or ARC reporting
Diagram
Diagram PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TravelStats_PurposeCode PNRChangeRQ.tmp#PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_PNRChangeRQ_PNRChangeRQ_ChangeStoredPrice_TravelStats_DestinationCode
Properties
content: complex
minOccurs: 0
Model PurposeCode{0,1} , DestinationCode{0,1}
Children DestinationCode, PurposeCode
Instance
<TravelStats>
  <PurposeCode>{0,1}</PurposeCode>
  <DestinationCode>{0,1}</DestinationCode>
</TravelStats>
Source
<xsd:element name="TravelStats" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Statistical data as needed for BSP and/or ARC reporting</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="PurposeCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="DestinationCode" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / TravelStats / PurposeCode
Namespace No namespace
Annotations
Purpose Code.
Valid values:
1 = Business
2 = Pleasure
3 = Charter

Canadian requirement
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="PurposeCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Purpose Code. Valid values: 1 = Business 2 = Pleasure 3 = Charter Canadian requirement</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PNRChangeRQ / ChangeStoredPrice / TravelStats / DestinationCode
Namespace No namespace
Annotations
1 = Mexico, Costa Rica, Central America, Canal zone
2 = Islands and countries of the Caribbean, Bermuda, including PR, VI
3 = South America
4 = Europe incl Morocco, Tunisia, Algeria, Greenland
5 = Africa
6 = Middle East (western Asia) 
7 = Asia including India
8 = Australia, New Zealand. Pacific islands incl Hawaii,
excluding Guam
0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) 

Canadian requirement
Diagram
Diagram
Properties
minOccurs: 0
Source
<xsd:element name="DestinationCode" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>1 = Mexico, Costa Rica, Central America, Canal zone 2 = Islands and countries of the Caribbean, Bermuda, including PR, VI 3 = South America 4 = Europe incl Morocco, Tunisia, Algeria, Greenland 5 = Africa 6 = Middle East (western Asia) 7 = Asia including India 8 = Australia, New Zealand. Pacific islands incl Hawaii, excluding Guam 0 = United States (wholly within the USA) or trans- border Canada – USA (or vice-versa) Canadian requirement</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ChangeCar
Namespace No namespace
Annotations
Change car group
Diagram
Diagram PNRChangeRQ.tmp#ElementNumber PNRChangeRQ.tmp#TattooNumber PNRChangeRQ.tmp#ChangeCarDates PNRChangeRQ.tmp#ChangeCarType PNRChangeRQ.tmp#ChangeCarOptions
Properties
content: complex
Used by
Element PNRChangeRQ
Model (ElementNumber | TattooNumber) , ChangeCarDates{0,1} , ChangeCarType{0,1} , ChangeCarOptions{0,1}
Children ChangeCarDates, ChangeCarOptions, ChangeCarType, ElementNumber, TattooNumber
Instance
<ChangeCar>
  <ElementNumber>{1,1}</ElementNumber>
  <TattooNumber>{1,1}</TattooNumber>
  <ChangeCarDates>{0,1}</ChangeCarDates>
  <ChangeCarType>{0,1}</ChangeCarType>
  <ChangeCarOptions>{0,1}</ChangeCarOptions>
</ChangeCar>
Source
<xsd:element name="ChangeCar">
  <xsd:annotation>
    <xsd:documentation>Change car group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:choice>
        <xsd:element ref="ElementNumber"/>
        <xsd:element ref="TattooNumber"/>
      </xsd:choice>
      <xsd:element ref="ChangeCarDates" minOccurs="0"/>
      <xsd:element ref="ChangeCarType" minOccurs="0"/>
      <xsd:element ref="ChangeCarOptions" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ChangeCarDates
Namespace No namespace
Annotations
Change car dates group
Diagram
Diagram PNRChangeRQ.tmp#PickUp PNRChangeRQ.tmp#DropOff PNRChangeRQ.tmp#RateCode
Properties
content: complex
Used by
Element ChangeCar
Model PickUp{0,1} , DropOff{0,1} , RateCode{0,1}
Children DropOff, PickUp, RateCode
Instance
<ChangeCarDates>
  <PickUp>{0,1}</PickUp>
  <DropOff>{0,1}</DropOff>
  <RateCode>{0,1}</RateCode>
</ChangeCarDates>
Source
<xsd:element name="ChangeCarDates">
  <xsd:annotation>
    <xsd:documentation>Change car dates group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="PickUp" minOccurs="0"/>
      <xsd:element ref="DropOff" minOccurs="0"/>
      <xsd:element ref="RateCode" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element PickUp
Namespace No namespace
Annotations
Pick up information group
Diagram
Diagram PNRChangeRQ.tmp#Date PNRChangeRQ.tmp#Time PNRChangeRQ.tmp#FlightArrival
Properties
content: complex
Used by
Element ChangeCarDates
Model Date{0,1} , Time{0,1} , FlightArrival{0,1}
Children Date, FlightArrival, Time
Instance
<PickUp>
  <Date>{0,1}</Date>
  <Time>{0,1}</Time>
  <FlightArrival>{0,1}</FlightArrival>
</PickUp>
Source
<xsd:element name="PickUp">
  <xsd:annotation>
    <xsd:documentation>Pick up information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Date" minOccurs="0"/>
      <xsd:element ref="Time" minOccurs="0"/>
      <xsd:element ref="FlightArrival" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Date
Namespace No namespace
Annotations
Date in ISO 8601 format (yyyy-mm-dd).  Example: 2002-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
Used by
Source
<xsd:element name="Date" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Date in ISO 8601 format (yyyy-mm-dd). Example: 2002-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Time
Namespace No namespace
Annotations
Time in ISO 8601 format (hh:mm).  Example: 14:30
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
pattern ([0-1][0-9]|2[0-4]):[0-5][0-9]
Used by
Elements DropOff, PickUp, TimeLimit
Source
<xsd:element name="Time">
  <xsd:annotation>
    <xsd:documentation>Time in ISO 8601 format (hh:mm). Example: 14:30</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="([0-1][0-9]|2[0-4]):[0-5][0-9]">
        <xsd:annotation>
          <xsd:documentation>
          </xsd:documentation>
        </xsd:annotation>
      </xsd:pattern>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FlightArrival
Namespace No namespace
Annotations
Flight arrival group
Diagram
Diagram PNRChangeRQ.tmp#AirlineCode PNRChangeRQ.tmp#FlightNumber
Properties
content: complex
Used by
Element PickUp
Model AirlineCode , FlightNumber
Children AirlineCode, FlightNumber
Instance
<FlightArrival>
  <AirlineCode>{1,1}</AirlineCode>
  <FlightNumber Suffix="">{1,1}</FlightNumber>
</FlightArrival>
Source
<xsd:element name="FlightArrival">
  <xsd:annotation>
    <xsd:documentation>Flight arrival group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="AirlineCode"/>
      <xsd:element ref="FlightNumber"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element AirlineCode
Namespace No namespace
Annotations
Airline code.  Example: DL
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
maxLength 2
Used by
Source
<xsd:element name="AirlineCode">
  <xsd:annotation>
    <xsd:documentation>Airline code. Example: DL</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="2"/>
      <xsd:maxLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element FlightNumber
Namespace No namespace
Annotations
Flight number - an integer value within the range of [0,9999].

Example: 1234
Diagram
Diagram PNRChangeRQ.tmp#FlightNumberType PNRChangeRQ.tmp#FlightNumberWithSuffixType_Suffix PNRChangeRQ.tmp#FlightNumberWithSuffixType
Type FlightNumberWithSuffixType
Type hierarchy
Properties
content: complex
Used by
Attributes
QName Type Fixed Default Use Annotation
Suffix restriction of xsd:string optional
Flight number alpha qualifier.  
Values are:
A
B
C
D

Example: A
Source
<xsd:element name="FlightNumber" type="FlightNumberWithSuffixType">
  <xsd:annotation>
    <xsd:documentation>Flight number - an integer value within the range of [0,9999]. Example: 1234</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element DropOff
Namespace No namespace
Annotations
Drop off information group
Diagram
Diagram PNRChangeRQ.tmp#Date PNRChangeRQ.tmp#Time PNRChangeRQ.tmp#FlightDeparture
Properties
content: complex
Used by
Element ChangeCarDates
Model Date{0,1} , Time{0,1} , FlightDeparture{0,1}
Children Date, FlightDeparture, Time
Instance
<DropOff>
  <Date>{0,1}</Date>
  <Time>{0,1}</Time>
  <FlightDeparture>{0,1}</FlightDeparture>
</DropOff>
Source
<xsd:element name="DropOff">
  <xsd:annotation>
    <xsd:documentation>Drop off information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Date" minOccurs="0"/>
      <xsd:element ref="Time" minOccurs="0"/>
      <xsd:element ref="FlightDeparture" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FlightDeparture
Namespace No namespace
Annotations
Flight departure group
Diagram
Diagram PNRChangeRQ.tmp#AirlineCode PNRChangeRQ.tmp#FlightNumber
Properties
content: complex
Used by
Element DropOff
Model AirlineCode , FlightNumber
Children AirlineCode, FlightNumber
Instance
<FlightDeparture>
  <AirlineCode>{1,1}</AirlineCode>
  <FlightNumber Suffix="">{1,1}</FlightNumber>
</FlightDeparture>
Source
<xsd:element name="FlightDeparture">
  <xsd:annotation>
    <xsd:documentation>Flight departure group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="AirlineCode"/>
      <xsd:element ref="FlightNumber"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element RateCode
Namespace No namespace
Annotations
Rate code.  Example: STD
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element ChangeCarDates
Source
<xsd:element name="RateCode" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Rate code. Example: STD</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ChangeCarType
Namespace No namespace
Annotations
Change car type group
Diagram
Diagram PNRChangeRQ.tmp#CarType
Properties
content: complex
Used by
Element ChangeCar
Model CarType
Children CarType
Instance
<ChangeCarType>
  <CarType>{1,1}</CarType>
</ChangeCarType>
Source
<xsd:element name="ChangeCarType">
  <xsd:annotation>
    <xsd:documentation>Change car type group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="CarType"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarType
Namespace No namespace
Annotations
Car type code for car type specific search. 
GDS use car types defined by standard interline practices and procedures (SIPP) manual. Each car-type code consists of four letters, one letter from each of the following categories :
- CLASS
- TYPE
- SHIFT
- AIR CONDITIONING.
i.e. ECMR = Economy Class + 2/4 Door Car + Manual Transmisson + Air-Conditioning.

You can use asterisks in any position to indicate all. So to search for any car so long as it is automatic, enter: **A* . You can use up to 3 asterisks ( **** not allowed).

CLASS: 
C = Compact
E = Economy
F = Full Size (4-door)
I = Intermediate
L = Luxury
M = Mini
P = Premium
S = Standard
X = Special

TYPE:
B = 2-Door
C = 2/4 Door
D = 4-Door
F = 4-Wheel Drive
J = All Terrain
K = Truck
L = Limousine
P = Pick Up
R = Recreational
S = Sports Car
T = Convertible
V = Van
W = Station Wagon
X = Special

SHIFT:
A = Automatic
M = Manual

AIR CONDITIONING:
N = No
R = Yes
Example: ECAR
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 4
maxLength 4
Used by
Element ChangeCarType
Source
<xsd:element name="CarType">
  <xsd:annotation>
    <xsd:documentation>Car type code for car type specific search. GDS use car types defined by standard interline practices and procedures (SIPP) manual. Each car-type code consists of four letters, one letter from each of the following categories : - CLASS - TYPE - SHIFT - AIR CONDITIONING. i.e. ECMR = Economy Class + 2/4 Door Car + Manual Transmisson + Air-Conditioning. You can use asterisks in any position to indicate all. So to search for any car so long as it is automatic, enter: **A* . You can use up to 3 asterisks ( **** not allowed). CLASS: C = Compact E = Economy F = Full Size (4-door) I = Intermediate L = Luxury M = Mini P = Premium S = Standard X = Special TYPE: B = 2-Door C = 2/4 Door D = 4-Door F = 4-Wheel Drive J = All Terrain K = Truck L = Limousine P = Pick Up R = Recreational S = Sports Car T = Convertible V = Van W = Station Wagon X = Special SHIFT: A = Automatic M = Manual AIR CONDITIONING: N = No R = Yes Example: ECAR</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:maxLength value="4"/>
      <xsd:minLength value="4"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ChangeCarOptions
Namespace No namespace
Annotations
Change car options group
Diagram
Diagram PNRChangeRQ.tmp#SupplementalInformation
Properties
content: complex
Used by
Element ChangeCar
Model SupplementalInformation
Children SupplementalInformation
Instance
<ChangeCarOptions>
  <SupplementalInformation>{1,1}</SupplementalInformation>
</ChangeCarOptions>
Source
<xsd:element name="ChangeCarOptions">
  <xsd:annotation>
    <xsd:documentation>Change car options group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="SupplementalInformation"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element SupplementalInformation
Namespace No namespace
Annotations
Supplemental information group
Diagram
Diagram PNRChangeRQ.tmp#BookingSource PNRChangeRQ.tmp#CorporateRateOverride PNRChangeRQ.tmp#CorporateDiscountNumber PNRChangeRQ.tmp#Deposit PNRChangeRQ.tmp#PaymentGuarantee PNRChangeRQ.tmp#Voucher PNRChangeRQ.tmp#Coupon PNRChangeRQ.tmp#AdditionalInformation
Properties
content: complex
Used by
Model BookingSource{0,1} , CorporateRateOverride{0,1} , CorporateDiscountNumber{0,1} , Deposit{0,1} , PaymentGuarantee* , Voucher{0,1} , Coupon{0,1} , AdditionalInformation{0,1}
Children AdditionalInformation, BookingSource, CorporateDiscountNumber, CorporateRateOverride, Coupon, Deposit, PaymentGuarantee, Voucher
Instance
<SupplementalInformation>
  <BookingSource>{0,1}</BookingSource>
  <CorporateRateOverride>{0,1}</CorporateRateOverride>
  <CorporateDiscountNumber>{0,1}</CorporateDiscountNumber>
  <Deposit>{0,1}</Deposit>
  <PaymentGuarantee>{0,unbounded}</PaymentGuarantee>
  <Voucher>{0,1}</Voucher>
  <Coupon>{0,1}</Coupon>
  <AdditionalInformation>{0,1}</AdditionalInformation>
</SupplementalInformation>
Source
<xsd:element name="SupplementalInformation">
  <xsd:annotation>
    <xsd:documentation>Supplemental information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="BookingSource" minOccurs="0"/>
      <xsd:element ref="CorporateRateOverride" minOccurs="0"/>
      <xsd:element ref="CorporateDiscountNumber" minOccurs="0"/>
      <xsd:element ref="Deposit" minOccurs="0"/>
      <xsd:element ref="PaymentGuarantee" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element ref="Voucher" minOccurs="0"/>
      <xsd:element ref="Coupon" minOccurs="0"/>
      <xsd:element ref="AdditionalInformation" minOccurs="0"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element BookingSource
Namespace No namespace
Annotations
Agency booking source number.  Example: 99199
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="BookingSource" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Agency booking source number. Example: 99199</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CorporateRateOverride
Namespace No namespace
Annotations
Corporate rate override.  Example: 25900
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="CorporateRateOverride" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Corporate rate override. Example: 25900</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CorporateDiscountNumber
Namespace No namespace
Annotations
Corporate discount number.  Example: 5643356
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="CorporateDiscountNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Corporate discount number. Example: 5643356</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Deposit
Namespace No namespace
Annotations
Deposit.  Example: 15000
Diagram
Diagram
Type xsd:integer
Properties
content: simple
Used by
Source
<xsd:element name="Deposit" type="xsd:integer">
  <xsd:annotation>
    <xsd:documentation>Deposit. Example: 15000</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element PaymentGuarantee
Namespace No namespace
Annotations
Payment guarantee group
Diagram
Diagram PNRChangeRQ.tmp#CreditCard PNRChangeRQ.tmp#Other
Properties
content: complex
Used by
Model CreditCard{0,1} , Other*
Children CreditCard, Other
Instance
<PaymentGuarantee>
  <CreditCard PartialAmount="">{0,1}</CreditCard>
  <Other PartialAmount="">{0,unbounded}</Other>
</PaymentGuarantee>
Source
<xsd:element name="PaymentGuarantee">
  <xsd:annotation>
    <xsd:documentation>Payment guarantee group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="CreditCard" minOccurs="0"/>
      <xsd:element ref="Other" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CreditCard
Namespace No namespace
Annotations
Credit card group
Diagram
Diagram PNRChangeRQ.tmp#CreditCard_PartialAmount PNRChangeRQ.tmp#CCCode PNRChangeRQ.tmp#CCNumber PNRChangeRQ.tmp#CCExpiration PNRChangeRQ.tmp#CreditCard_SecurityID PNRChangeRQ.tmp#CreditCard_ReportingData PNRChangeRQ.tmp#CardholderFirstName PNRChangeRQ.tmp#CardholderLastName PNRChangeRQ.tmp#ApprovalCode PNRChangeRQ.tmp#Authorization PNRChangeRQ.tmp#ExtendedPayment PNRChangeRQ.tmp#CreditCard_CCAddressGroup
Properties
content: complex
Used by
Model CCCode , CCNumber , CCExpiration , SecurityID{0,1} , ReportingData{0,1} , CardholderFirstName{0,1} , CardholderLastName , ApprovalCode{0,1} , Authorization{0,1} , ExtendedPayment{0,1} , CCAddressGroup{0,1}
Children ApprovalCode, Authorization, CCAddressGroup, CCCode, CCExpiration, CCNumber, CardholderFirstName, CardholderLastName, ExtendedPayment, ReportingData, SecurityID
Instance
<CreditCard PartialAmount="">
  <CCCode>{1,1}</CCCode>
  <CCNumber>{1,1}</CCNumber>
  <CCExpiration>{1,1}</CCExpiration>
  <SecurityID>{0,1}</SecurityID>
  <ReportingData>{0,1}</ReportingData>
  <CardholderFirstName>{0,1}</CardholderFirstName>
  <CardholderLastName>{1,1}</CardholderLastName>
  <ApprovalCode>{0,1}</ApprovalCode>
  <Authorization Type="">{0,1}</Authorization>
  <ExtendedPayment>{0,1}</ExtendedPayment>
  <CCAddressGroup>{0,1}</CCAddressGroup>
</CreditCard>
Attributes
QName Type Fixed Default Use Annotation
PartialAmount xsd:positiveInteger optional
(Partial) amount allocated to this form of payment. Used for so called split payment. This is the amount to be paid with this FOP. 
Not to be confused w/ amount entered for authorization in Authorization/Amount element.
Source
<xsd:element name="CreditCard">
  <xsd:annotation>
    <xsd:documentation>Credit card group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="CCCode"/>
      <xsd:element ref="CCNumber"/>
      <xsd:element ref="CCExpiration"/>
      <xsd:element name="SecurityID" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="ReportingData" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Data Elements required by certain card issuers for report purposes</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="AccountNumber" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Corporation's account number</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="Min">
                      <xsd:annotation>
                        <xsd:documentation>minimum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Max">
                      <xsd:annotation>
                        <xsd:documentation>maximum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Format">
                      <xsd:annotation>
                        <xsd:documentation>A - alphanumeric (default) N - numeric D - ISO date format</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Mandatory">
                      <xsd:annotation>
                        <xsd:documentation>O - optional (default) M - mandatory</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementID" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor code assigned to this reporting element Example: BK</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementName" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor element name assigned to this reporting element Example: Corperate ID</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="CostCenter" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Cost center number/code</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="Min">
                      <xsd:annotation>
                        <xsd:documentation>minimum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Max">
                      <xsd:annotation>
                        <xsd:documentation>maximum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Format">
                      <xsd:annotation>
                        <xsd:documentation>A - alphanumeric (default) N - numeric D - ISO date format</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Mandatory">
                      <xsd:annotation>
                        <xsd:documentation>O - optional (default) M - mandatory</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementID" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor code assigned to this reporting element Example: BK</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementName" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor element name assigned to this reporting element Example: Corperate ID</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="Department" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Department description for this Traveler in this association. Example: Marketing</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="Min">
                      <xsd:annotation>
                        <xsd:documentation>minimum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Max">
                      <xsd:annotation>
                        <xsd:documentation>maximum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Format">
                      <xsd:annotation>
                        <xsd:documentation>A - alphanumeric (default) N - numeric D - ISO date format</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Mandatory">
                      <xsd:annotation>
                        <xsd:documentation>O - optional (default) M - mandatory</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementID" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor code assigned to this reporting element Example: BK</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementName" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor element name assigned to this reporting element Example: Corperate ID</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="EmployeeID" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>EmployeeID of traveler for this association. Example 476254</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="Min">
                      <xsd:annotation>
                        <xsd:documentation>minimum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Max">
                      <xsd:annotation>
                        <xsd:documentation>maximum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Format">
                      <xsd:annotation>
                        <xsd:documentation>A - alphanumeric (default) N - numeric D - ISO date format</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Mandatory">
                      <xsd:annotation>
                        <xsd:documentation>O - optional (default) M - mandatory</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementID" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor code assigned to this reporting element Example: BK</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementName" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor element name assigned to this reporting element Example: Corperate ID</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="GenericElement" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>These are elements provided by CC vendor and could include elements such as - ProjectNumber - AccountingUnit - ActionNumber - DepartingDate - FinalDestination Above sample reflects data elements from UATP/Airplus requirements</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="Min">
                      <xsd:annotation>
                        <xsd:documentation>minimum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Max">
                      <xsd:annotation>
                        <xsd:documentation>maximum length</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Format">
                      <xsd:annotation>
                        <xsd:documentation>A - alphanumeric (default) N - numeric D - ISO date format</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="Mandatory">
                      <xsd:annotation>
                        <xsd:documentation>O - optional (default) M - mandatory</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementID" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor code assigned to this reporting element Example: PN</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="DataElementName" use="required">
                      <xsd:annotation>
                        <xsd:documentation>Vendor element name assigned to this reporting element Example: Project Number</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="SystemProcess">
                      <xsd:annotation>
                        <xsd:documentation>Allowed value: Y If set this identifies that this data content for this element is system generated (not provide by user input or profiles)</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:sequence minOccurs="0">
        <xsd:element ref="CardholderFirstName" minOccurs="0"/>
        <xsd:element ref=</