Zum Ende der Metadaten springen
Zum Anfang der Metadaten

Sie zeigen eine alte Version dieser Seite an. Zeigen Sie die aktuelle Version an.

Unterschiede anzeigen Seitenhistorie anzeigen

« Vorherige Version anzeigen Version 2 Aktuelle »



Software Documentation
WO_111: GTA Interface






Ordering party : Railtour Suisse sa







Created by: Kerstin Freiß













Filename:

D:\000_Bewotec\001_Railtour\GTA Interface\WO_111_Basisanbindung\WO_111_GTA_Interface_Software_Documentation_0.2.doc

Size:

1.335 KB

Created:

30.07.2013

Changed:

7/30/2013 17:07:00 A7/P7

Printed:

9/22/2011 10:09:00 A9/P9


Disclaimers
The information contained in this document is the proprietary and exclusive property of Bewotec GmbH except as otherwise indicated. No part of this document, in whole or in part, may be reproduced, stored, transmitted, or used for design purposes without the prior written permission of Bewotec GmbH.
The information contained in this document is subject to change without notice.
The information in this document is provided for informational purposes only. Bewotec specifically disclaims all warranties, express or limited, including, but not limited, to the implied warranties of merchantability and fitness for a particular purpose, except as provided for in a separate software license agreement.


Privacy Information
This document may contain information of a sensitive nature. This information should not be given to persons other than those who are involved in the "DaVinci" project or who will become involved during the lifecycle of this project.


General remark
The final dialog design/layout of the screens may vary, but the described functionality shall be integrated.




















Versions

Date

Version

Description

Name

29.07.2013

0.1

Document created

K.Freiß

30.07.2013

0.2

Document extended

K.Freiß

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 





Content

1 Requirement
1 Architecture
2 Hotel service
3 DaVinci Basic definitions
3.1 Price profile
3.2 Provider profile
3.3 CRS tab
3.4 Queue
4 GTA Products in DaVinci
5 General interface functionality
6 Automatic MarkUp
7 Samples
7.1 Booking request GTA product
7.2 Booking GTA product
7.3 Adding GTA product
7.4 Cancellation GTA product
7.5 Deletion cancelled GTA product
7.6 Optional Booking not possible
7.7 Request not possible
7.8 Booking GTA product with automatic MarkUp







Requirement



The background of the development project is that the touristic market is in a change as following:
The hotel suppliers do want to sell their rooms more and more on their own instead of giving their allotments to tour operators.
Therefore interfaces to hotel suppliers are getting more important.
The objective of this first phase of the project is the implementation of a booking interface to the hotel supplier GTS/GTA out of DaVinci.
Interfaces to other hotel reservation systems need to be handled in separate project phases.
The following functionalities are available in DaVinci release version 1059 or higher:

  1. Definition of external GTA hotel services within DaVinci
  2. Availability requests and reservations of GTA hotel services out of DaVinci (no requests and optional bookings)
  3. Rebooking handling of GTA hotel services in DaVinci (no re-booking of external services)
  4. Cancellation handling of GTA hotel services in DaVinci (no external cancellation)
  5. Error Handling within DaVinci


Sales prices should be calculated based on the by GTA supplied purchase price plus an automatic mark up.
Mark Ups can be defined for

  • certain hotels,
  • certain destinations and
  • on system level (as general default).








Architecture







This document describes the online functionality between GenVas and the GTA web service.

Hotel service


The Windows hotel service can be installed by using the installation routine 'setup.exe'.
The only setting which has to be defined outside Davinci is the DaVinci db connection within the configuration file 'Bewo.Config.Manager.dll.config':

Attributes element <Provider>
<db-server>: the name (or IP) of the DaVinci database server
<db-name> : the name of the DaVinci database
<user> / <password> :log in credentials of the DaVinci database
The service can be started after the configuration has been done.
The interface can also be started as 'HotelService.ServiceHost.exe' for test purpose.
The related configuration entries need to be done in 'HotelService.ServiceHost.exe.config'.

DaVinci Basic definitions


Price profile


To allow a correct import of purchase prices from GTA a price profile has to be defined with all necesarry entries and later on assigned to the provider profile.

Provider profile


The external provider profile needs to be defined within the DaVinci basic data under CRS – External Systems.

The 'Provider Name' (e.g. GTA) is a free name entry.
The 'Protocoll Transformer' name has to be 'Gta'.
'Adresse' is the URL of the GTA web service.
'Benutzer' and 'Passwort' are the login credentials of the GTA web service.
'Email' is the corresponding GTA email address.
For an correct import of purchase prices it is necessary to assign an EK price profile. Otherwise the system won't import any purchase prices from GTA.

Since the interface does only support fix / confirmed reservation optional bookings and requests have to be disabled on the third tab of the definition.

CRS tab


The following flag enables the CRS tab on booking code level:

Queue


In case of errors (e.g. time out during communication with the extern System, ..) DaVinci will create queue entries.
The queue definition within DaVinci is done under Queue / CRM:



GTA Products in DaVinci


Assumptions

  • One GTA product is defined as one DaVinci booking code
  • One GTA room type is defined as one DaVinci service type


Defintion of an GTA product within DaVinci:
On the first tab 'Buchungscode' 'Hotel-Interface' needs to be set as LT-Interface and the corresponding provider profile (e.g. GTA) needs to be assigned:

The tab 'CRS' contains the assignment of the external hotel code plus the external city code (both codes are supplied by GTA):

The external room code 'Unterbringung' plus the external room type code 'Belegung' (both supplied by GTA) need to be assigned on level hotel service type (room type):

The DaVinci code needs to be defined according to the valid occupany in GTA.

General interface functionality


The following functionalities are available for GTA products:

  • Availability requests against GTA (Genesis action BA and Cets action Book/Check)
  • Creation of external reservations in GTA (Genesis action B + BC and Cets action Book/Fix)
  • Adding of additional GTA products to an existing booking (Genesis action U + UC)


The user can request and book one GTA product and room within one DaVinci service line out of Genesis and Cets (Touronline).
The avaliability will be checked against DaVinci and GTA. The GTA system will only be checked in case the product is available within DaVinci. The GTA availability will be checkted against GTA in case no DaVinci allotment is assigned.
The price supplied by GTA will be stored as manual purchase price. Purchase prices from DaVinci won't be considered.
The sales price is taken from DaVinci or calculated based on the GTA purchase price plus a defined MarkUp (see chapter 6 / Automatic MarkUp).
Customer requests will be stored in DaVinci but won't be passed to GTA.
At the time the reservation is done in GTA GenVas will store the supplied external reservation number and prices within the DaVinci booking.

  • Cancelation of GTA products in DaVinci (action S + SN)

The external GTA reservation will be cancelled (partial DaVinci cancellation or full cancellation) in case of an internal DaVinci cancellation action.

  • Deletion of a canceled GTA product

GTA products can only be deleted if they are cancelled (Genesis actions U + UC).
Please note that this functionality can only be ensured if the booking contains the same GTA product once and if the booking is not a full cancellation.

Error Handling
The system will decline the DaVinci booking and will respond with an error message in case

  • the booking contains an GTA product with quantity > 1 within the same service line (actions BA, B and BC)
  • the booking contains at least one GTA product and is on request (actions BA and BQ)
  • the user requests or tries to create an optional booking which contains an GTA hotel service (action OA and O)
  • the user tries to change an GTA hotel service (actions U and UC)

Automatic MarkUp


Tables for automatic percental MarkUps can be defined within the system settings-> conditions:


It is possible to distinguish percentage values per travel date range.
Furthermore it is mentarory to enter a price profile to generate the affected sales price lines.
In case the GTA price is supplied in a foreign currency the system will consider the purchase exchange rate.

MarkUp tables can be linked on the following three levels.
The different MarkUps will be considered in the mentioned priority during the calculation process.

  1. Booking Code


The user can either link a classic sales price table on, after enabling the flag, or a MarkUp table.
The link on product, or booking code, level has the highest priority during the calculation process.

  1. Destination


The link on destination will be fired for products with MarkUp flag (no own MarkUp table) and the coresponding travel destination.

  1. General system default MarkUp


The default MarkUp table will be fired for products with MarkUp flag (no own MarkUp table) and no Markup on the coresponding travel destination.






Samples


Booking request GTA product


Booking request:

The external service is marked as GTA product (GTA icon).
The availability has been checked against DaVinci and GTA.
The sales prices has been calculated from the DaVinci definitions.

The purchase price has been imported as manual price.

Booking GTA product


Booking:

The external service is marked as GTA product (GTA icon).
The availability has been checked against DaVinci and GTA.
The sales price has been calculated from the DaVinci definitions.
The customer reqeusts have beed stored in DaVinci.

The external GTA reservation number has been stored within the service details (LT.-Res-Nr.)
The DaVinci allotment has been reduced if exist.
The purchase price has been imported as manual price.

Adding GTA product


Before re-booking:

Re-booking request for second GTA room:

Re-booking for second GTA room:

The external service is marked as GTA product (GTA icon).
The availability has been checked against DaVinci and GTA.
The sales price has been calculated from the DaVinci definitions.
The customer reqeusts have beed stored in DaVinci.

The external GTA reservation number has been stored within the service details (LT.-Res-Nr.)
The DaVinci allotment has been reduced if exist.
The purchase price has been imported as manual price.

Cancellation GTA product


Partial cancellation second GTA room:

The GTA room has internally and externally been cancelled.
Cancellation first GTA room with full cancellation:

The GTA room has internally and externally been cancelled.

Deletion cancelled GTA product


Before deletion, the second GTA hotel service is already cancelled:

After deletion of the cancelled external GTA hotel service and re-booking:

Optional Booking not possible




Request not possible


Booking GTA product with automatic MarkUp


Booking:

The external service is marked as GTA product (GTA icon).
The availability has been checked against DaVinci and GTA.
The sales price has been calculated based on the GTA purchase price plus 20 % MarkUp, which is defined on booking code level.
The customer reqeusts have beed stored in DaVinci.

  • Keine Stichwörter