Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
userdocs:travelwise:getting_started:glossary [2013/06/19 08:41]
127.0.0.1 external edit
userdocs:travelwise:getting_started:glossary [2014/02/03 19:42] (current)
dokuwiki_sync
Line 69: Line 69:
   * [[#Pline]]   * [[#Pline]]
   * [[#​Product]]   * [[#​Product]]
 +  * [[#​Profile]] ​
   * [[#​Promotion]] ​   * [[#​Promotion]] ​
   * [[#PNR]]   * [[#PNR]]
Line 89: Line 90:
   * [[#TOP]]   * [[#TOP]]
   * [[#Tour Code]]   * [[#Tour Code]]
 +  * [[#Train]]
   * [[#​Transfer]]   * [[#​Transfer]]
   * [[#Transfer to Finance]]   * [[#Transfer to Finance]]
Line 96: Line 98:
   * [[#​Voucher]] ​   * [[#​Voucher]] ​
   * [[#WEF, WET]]   * [[#WEF, WET]]
 +
 ====== Administrator ====== ====== Administrator ======
 Maximum rights user account in TW.net. Maximum rights user account in TW.net.
 Set in Tools -> User Management -> column '​A'​. Set in Tools -> User Management -> column '​A'​.
 All the rest columns are not needed to be checked when '​A'​ is enabled. All the rest columns are not needed to be checked when '​A'​ is enabled.
 +
 +
 +====== Application ======
 +Travelwise.net program, called also TW.net; Travelwise (mostly old VB6 version), TW.
  
  
Line 358: Line 365:
 The record locators of the copied PNRs are communicated back to the CRS that owns the Master PNR, so all records remain tied together. This allows exchanging updates of the PNR when the status of trip changes in any of the CRSes. The record locators of the copied PNRs are communicated back to the CRS that owns the Master PNR, so all records remain tied together. This allows exchanging updates of the PNR when the status of trip changes in any of the CRSes.
 Although PNRs were originally introduced for air travel, they are now also being used for bookings of hotels, car rental, railways, etc. Although PNRs were originally introduced for air travel, they are now also being used for bookings of hotels, car rental, railways, etc.
 +
 +
 +====== Profile ======
 +Instance created under //Master Entry// as //Customer, Supplier, Hotel, Transfer or Sightseeing.//​
  
  
Line 366: Line 377:
 ====== Product ====== ====== Product ======
 Type of goods to be sold via Travelwise. Whatever becomes invoiced (segment, service) is related to exact product name and its settings. Type of goods to be sold via Travelwise. Whatever becomes invoiced (segment, service) is related to exact product name and its settings.
 +
 +====== Report Labels ======
 +Report element headline text. Can be edited and translated in: //Tools → Company Settings → Report Labels//.
  
  
 ====== Segment ====== ====== Segment ======
-Format, in which the service is treated in Travelwise Order. Provides automated booking procedure (separate booking form; confirmation workflow support, such as status change, '​Supplier'​ and '​Customer'​ confirmations;​ representation in Itinerary and Voucher). The segments are: Hotel, Transfer, Sightseeing,​ Misc (Miscellaneous service, provided by hotel), Car.+Format, in which the service is treated in Travelwise Order. Provides automated booking procedure (separate booking form; confirmation workflow support, such as status change, '​Supplier'​ and '​Customer'​ confirmations;​ representation in Itinerary and Voucher). The segments are: Hotel, Transfer, Train, Sightseeing,​ Misc (Miscellaneous service, provided by hotel), Car.
  
 Segments are classified by the type of rates: Segments are classified by the type of rates:
Line 375: Line 389:
   * manual segment (booked based on the rates inserted manually in a certain segment while booking).   * manual segment (booked based on the rates inserted manually in a certain segment while booking).
  
 +
 +====== Segment Status ======
 +Each booked service (//​segment//​) in Application'​ Order has got a special //status// assigned depending on the step of its processing. ​
 +  * IQ (information query) - segment is created, but nothing has been sent to supplier yet. 
 +  * PQ (price quotation) – reservation is made in online booking system (farewise.dk),​ but not confirmed by Billetkontoret as a tour operator.
 +  * RQ! (change request pending) – Change request has not yet been sent to supplier. Is automatically changed to RQ when it is sent.
 +  * RQ (request) – request sent to Supplier. IQ automatically changes to RQ, when booking is sent.
 +  * OK (confirmed) – reservation is confirmed by supplier. ​
 +  * UC (unable to confirm) – reservation is NOT confirmed by supplier. RQ can result in an OK or an UC. Logically it can also result in a WL (waitlisted).
 +  * RX! (cancellation request pending) – request for cancellation has not yet been sent. Is automatically changed to RX when sent.
 +  * RX (cancellation request pending) – pending a cancellation from Supplier, as the Customer cancelled the reservation.
 +  * XX (cancel) – reservation is cancelled. Confirmation of cancellation has been received from supplier. Caption should be XX (Cancelled).
 +  * OZ (obsolete) – reservation is not relevant anymore and can be deleted from the Order. Segments with this status become hidden within the Order, but can be reactivated back in case of need.
  
 ====== Service ====== ====== Service ======
Line 387: Line 414:
 ====== Tour Code ====== ====== Tour Code ======
 The definition applied in GDS, meaning the tour code. If a sale has been cancelled, this field remains blank. The definition applied in GDS, meaning the tour code. If a sale has been cancelled, this field remains blank.
 +
 +
 +====== Train ======
 +Service, which can be reserved in Amadeus or in any other external booking system and get loaded in Travelwise.net as a ‘Train Segment’ automatically or manually.