Software Documentation
Functional Description



„BAS interface"
Booking data

BAS Interface /WO006

Created by:
K. Freiß
Bewotec GmbH

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 "KuDoS 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.
Revision History

Idea
Idea is to enable travel agency chains, which use agency system BAS, to request actual booking information from TO system KuDos.
Furthermore booking information should automatically be send to BAS in case booking has been created or changed within TO system and invoice information should automatically be send to BAS in case of invoicing.

Content
1. Setup
1.1. BAS agency
1.2. GenVas
1.3. Queues
1.3.1. General Queue settings
1.3.2. Queue events
1.4. BAS Pox Web service
1.4.1. BasPox as windows service
1.4.2. Settings BasPox windows service
1.4.3. BasPox as application
2. Workflows
2.1. Recap Pull
2.2. Recap Push
2.3. Invoice Push
3. Booking in BAS
3.1. General booking information
3.2. Flight transports
3.3. Accommodations
3.4. Prices
3.5. Additional products
4. Appendix
4.1. Overview Approval Conditions
4.1.1. Work package 1.1 System preparation
4.1.2. Work package 1.2 Basic functional implementations
4.1.3. Work package 1.3 Pull/Push booking information 'Recap-String'
4.1.4. Work package 1.4 Push invoice information 'Invoice-String'

Setup

This chapter describes basic data and web service setup .

BAS agency

To enable internal agency for BAS connectivity external CRS (ANVR) agency number has to be defined within address data on tab CRS-Datas.
Agency-no is ANVR number and as CRS booking source BAS has to be selected.

One DaVinci agency can only be connected to one external CRS (Cets, Touronline or BAS).

GenVas

For internal GenVas communication (between BAS-service and GenVas) additional BAS port (menu entry Genesis) and booking source BAS has to be defined


In case GenVas is running as windows service one dedicated GenVas service has to be taken into account only for BAS. In this case BasProx connection configuration is:
.... -IP:<IP BasProxService> -Port:<Port BasProxService> -bookingsrc:BAS ....
127.0.0.1 is not valid as IP BasProxService.

Queues

For push mechanism (Recap and Invoice) it is necessary to configure extra BAS system queues within system settings.
In case of relevant booking action for BAS agency affected booking will be send to BAS queue with status 'hold'. User can now, after e.g. all booking amendments are done, send actual status to CRS (BAS).

General Queue settings

In case flag 'Send automatically' to Cets' is disabled messages are not automatically pushed to BAS but set on hold first. Release of queue event (Send to CRS) is necessary to send data to external system. This setting is recommended because of multiple bookings changes.
In case every single booking change should be automatically transferred to BAS setting has to be enabled.


Queue type for system queue has to be defined.

Queue events

Following CRS events are available for CRS communication (events have to be enabled):

All events except 'invoiced for CRS agent' are relevant for recap-push mechanism.
'Invoiced for CRS agent' will be considered for invoice-push.
Within queue event assignment CRS type BAS has to be selected.

BAS Pox Web service

Communication to BAS agency system is steered by web service BAS Pox. This service has to be up and running for all pull- and push mechanism.
All affected components are available via installation and setup 'BasPoxWindowsServiceSetup.msi'.
Warning :
To ensure full BAS service functionality Microsoft .NET Framework 3.5 Service Pack 1 has to be installed additionally to general DaVinci system requirements !!!

BasPox as windows service

Via double click on 'BasPoxWindowsServiceSetup.msi' installation and setup of BasPox will start.


In second step installation folder can be selected. Per default BasPox will be installed within windows folder 'Programme'.


Installation is finished and BaPox is started as windows service.

Settings BasPox windows service

Configuration file for BasPox windows service 'BasPoxWindowsService.exe.config' contains :

• logging settings
• database connection
• communication settings

Element <log4net> contains logging parameters.

During testing period level 'INFO' is recommend. Later on level 'WARN' is sufficient.
Logfile name can be determined in element <appender> 'LogFileAppender' parameter 'File'.
For different logging settings please contact Bewotec.
Element <hibernate-configuration> contains database settings.

'connection.connection_string' refers to native db server, db name and user (not ODBC connection).
Other attributes within in this section are only for internal usage and should be left on default.
Element <appSettings> contains all connection parameters.

'ServiceUri'
Attribute contains URL of internal (local) BAS Pox Web Server, where BAS sends G7 requests to BASProx (DaVinci) system and which has also to be configured in remote BAS system (Fadiro) for pull mechanism.
'BasUri'
Attribute contains URL of external (remote) BAS Web Server, where BasProx sends G7 messages to.
It is possible to use https connection in case system requirements are fulfilled.
'GenvasUsername'
Attribute contains user for GenVas login. User has to correspond to general DaVinci user settings.
'GenvasPassword'
Attribute contains password for GenVas login.Password has to correspond to general DaVinci user settings.
'GenvasIP'
Attribute contains IP for GenVas communication. IP has to correspond to GenVas configuration (1.2.).
'GenvasBasPort'
Attribute contains port for GenVas communication. Port has to correspond to GenVas configuration (1.2.).
'GenvasSenderID'
Attribute contains general sender ID within BAS messages (DaVinci -> BAS) which represents tour operator KTN.
'PollingIntervalS'
Attribute contains queue polling interval (push mechanism described in chapter 2) in seconds. That means DaVinci BAS Web service will poll within defined interval for push relevant bookings.
'QueuePollIntervalS'
Attribute contains time interval of next retry in case connection to external BAS service can't be established within defined max retries define in "QueuePollMaxRetry".
'QueuePollMaxRetry'
Attribute contains amount of retries in case connection to external BAS service can't be established.

BasPox as application

It is also possible to start BasProx as windows application via 'BasPoxService.ServiceHost.exe'.
Configuration file for windows application is 'BasPoxService.ServiceHost.exe.config' with same settings as service config file.
To start the application BasPox as windows service has to be shut down

Workflows

This chapter describes two general mechanisms Recap-Pull and Recap-Push, which are available to send booking information from DaVinci system into external BAS agency application.
Furthermore invoice mechanism Invoice Push is already documented which couldn't yet be implemented.

Recap Pull

This work flow is initiated by an external BAS agent and will transfer actual booking information of requested booking from Davinci database to BAS application.
BAS User requests booking information
booking informationspecific booking
specific bookingis available
on local BAS system


16

2
BAS


G7-Recap-Request G7-Recap-Response



5
DaVinci
Web-Server
BAS PROX SERVER
3



G1-Display-Request G1-Display-Response


GenVas
business logic4


BAS user can 'upload' actual booking information of specific - own - booking from DaVinci database into BAS system via entering booking number and button <Ophalen> in BAS from end after booking was created in DaVinci.

Booking is available now in BAS booking list and can be displayed.

Recap Push

This work flow is initiated by DaVinci booking actions (B*, U*, S*) and will transfer actual booking information of affected booking from Davinci database to BAS application.
That means e.g. imported PNRs are only pushed via Genesis-Import and rebooking action!
It can be steered if transmit should automatically done or has to be enabled by DaVinci user (see 1.3.1).
DaVinci user enters
new booking,
booking modification or
booking cancellation
within Genesis
or Internet client

1
4
GenVas
2 business logic

queue entry G1-Display-Request


G1-Display-Response

3
DaVinci
5 Web-Server
BAS PROX SERVER

G7-Recap-Response G7-Recap-Request



BAS
Booking information 6
is available
on local BAS system

In case booking is created, modified or cancelled for BAS agent in Davinci (e.g. via Genesis) queue entries are created depending on system settings ('Blocked' or 'Ready to process').


In case queue entry is on blocked it can be send to BAS via menu entry 'Send to CRS'.

If more than one booking action is processed while booking is not yet transferred (e.g. status 'Blocked') only last queue entry referring to last booking sequence will be available.
After execution queue entry will be shifted to 'Archive' with status 'Processed'.

Invoice Push

This work flow is initiated by DaVinci invoicing logic and will transfer actual invoice information of affected booking from Davinci database to BAS application.
It can be steered if transmit should automatically done or has to be enabled by DaVinci user (see 1.3.1).
Booking is invoiced
within DaVinci

1

4 GenVas
Business logic
2

queue entry
G1-Display-Request
G1-Display-Response


3
DaVinci
Web-Server
BAS PROX SERVER
7

5

G7-Invoice-Response G7-Recap-Request

BAS 6
G7-Recap ResponseBooking information
is available
on local BAS system



In case booking is invoiced for BAS agent in Davinci queue entries are created depending on system settings ('Blocked' or 'Ready to process'). According to Recap-Push-logic invoice information will be send automatically or after enabling to external system.

Booking in BAS

This chapter describes DaVinci requirements and transferred data.

General booking information

First area within BAS contains participants.

Name, initials, age/date of birth and gender are transferred from DaVinci booking
Second area contains booking related information like tour operator, reservation number and status.

As reservation number internal DaVinci booking number is send.
Additionally to displayed entries e.g. booking date, booking owner ('Berater') and prints for documents are transferred from DaVinci booking.

Flight transports

Within next area all relevant flight transports are displayed. For each transmitted flight segment also one segment is shown within BAS.

Requirement types F, F*, C, C* and NF are considered and send as transport.
In case PNR data is available each PNR flight segment is send.
Since booking DaVinci 'Book Class' might not be translatable to internal BAS (mapping is not possible) field 'Klasse' it is empty.
As text field service related text modules are sent.

Accommodations

Within next area all relevant accommodations (hotel, round trips, cruises and package services) are displayed. For each transmitted hotel- or package service also one segment is shown within BAS.

Requirement types H, H*, R, K, SP and P are considered and send as accommodation.
As 'Land' statistic code 'Land' is send. In case value can't be interpreted asnISO-3-letter code 'Land' within BAS will be shown empty.
In case 'Land' is a valid 3-letter-code value from first accommodation will be overtaken in booking header information.
Since booking DaVinci service type might not be translatable to internal BAS (mapping is not possible) field 'Type' field is empty. Default meal plan will only be transferred in case it is taken over from booking code definition into Genesis.
As text field service related text modules are sent.

Prices

Within next area all participant related prices are sown and total are shown.

Only bookings in local currency EUR (sales) can be sent to BAS. Bookings with foreign sales currency can't be passed.

Additional products

Within next area all other transferred services like rental cars, insurances, transfers, busses and miscellaneous services and buses are shown in form of text segments.

Requirement types MW, WM, T, BU, BA, TA, SO and V are considered and send as accommodation.

Rental cars (requirement MW) will be shown inclusive pick-up and drop-off information.

Appendix

Overview Approval Conditions

Work package 1.1 System preparation

Work package 1.2 Basic functional implementations

Work package 1.3 Pull/Push booking information 'Recap-String'

Work package 1.4 Push invoice information 'Invoice-String'