MarkUp_Absolut_Software_Documentation_3 0



Software Documentation
Absolute Mark-Up Calculation














Author: Dirk Baschleben











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.




















Version

Datum

Version

Beschreibung

Name

24.08.2015

1.0

Document Created

D. Baschleben

26.10.2015

2.0

Document Updated

K. Freiß

25.11.2015

3.0

Document Updated

K. Freiß

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 





Table of Content
1. Requirement
2. Functional Description
2.1 Bookingcode Set-Up
2.2 Mark-Up Set-Up
3. Agency Set-Up
4. Package options
5. Archive
6. Examples
6.1 Mark-up per bookingcode
6.2 Mark-up per bookingcode and participant type











Requirement


This document describes the new concept of the absolute markup calculation for the dynamic production of services stored in DaVinci.
The mark-up is an absolute amount per night and pax according to the current yield management requirement.
Further mark-up dimensions are:

  • Product (booking code)
  • External interface
  • Product type
  • Date of travel
  • Type of pax, e.g. child or baby
  • Sales channel (i.e. the used agency represents one sales channel during the booking process)
  • Room type
  • Requirement
  • Destination



For mark-up functionality it is important to take into consideration:

  • Parallel operation of dynamic production and (traditional) package-based production, i.e., it is possible to use the same inventory both for packages and dynamic products
  • Include transfers and handling-fees in the dynamic product




Functional Description



Bookingcode Set-Up



If the user activates the checkbox „Use Mark-Up" in the bookingcode then the mark-up calculation will be used instead of a conventional sales price chart.
It will be still possible to link a normal sales price chart that can be used if this bookingcode is e.g. part of a package.

If there is valid purchase price then this purchase price will be calculated within the booking process and then copied to the sales side (1:1 if sales and purchase price currency is equal).
In the booking process the absolute Mark-Up will be added as a new price row in sales prices.
The name of this price row is per default "Markup".


Mark-Up Set-Up



The new frame can be opened from "Leistungen" ribbon.

The mark-up definition levels are available as following:
Level 1 Calculation parameter

  • Product (booking code) and Room type
  • External interface
  • Product type


Level 2 Details

  • Sales channel (i.e. the used agency represents one sales channel during the booking process)
  • Date of travel


Level 3

  • Type of pax, e.g. child or baby
  • Requirement
  • Duration
  • Destination


The combinability depends on the selected level 1 (product, external interface or product type).
Before the user can define or modify the calculation entries it is necessary to "check out" the current settings with the following check-out icon:

Level 1 Calculation parameter

On level 1 the user can here add and delete booking codes, external interfaces or product types.
Buchungscode: Name of the booking code
Schnittstelle: Name of the defined interface profile (system settings)
Produkttyp:Name of the product type (statistic code)
Leistungscode: Service type filter, if empty the valid for all service types of a booking code

  • Is only available in case of booking code mark-ups


Grundlage: Basis of calculation Night, Day or Once.
Art: Kind of calculation; participant, unit or booking
Produktart: Product type for price rows
Steuer: VAT for price row
Gruppencode: Group text for documents
Kostenart: Cost type for accounting purposes

Klicking on green "+" copies an existing entry

All existing details depending on the current entry will be copied as well.
Klicking on red "X" deletes entries.

All existing details depending on the current entry will be deleted as well.
Level 2 Details

In the detail section the user can enter service date ranges and an absolute markup.
It is possible to have different mark-ups per day.
The filter agency can be used to steer different mark-ups per brands/markets if one agency number reflect this.

Level 3
Type of pax

In this section an existing date range can be modified by a mark-up per participant type.
Babies, Children and Adults are possible entries.
In this example a further reduction of -3 will be considered for children.




Type of Duration

In this section the user is able to define a mark-up for a specific duration.
In this example it will decrease the mark-up by 1 for each night within the defined date-range when 14 nights are requested. The duration does not necessarily need to cover 100% the defined date range.
Example.
Requested service date range: 15.09.-29.09.

The mark-up between 15.09. and 25.09. is 9 not 10 because in total 14 nights are booked

Requirement

In this section an existing date range can be modified by a mark-up per requirement type (hotel, flight, …).
In this example a further supplement of 2 will be considered for hotels and 7 for flights.


Destination

In this section an existing date range can be modified by a mark-up per destination.
In this example a further supplement of 4 will be considered for HRG.


Save changes and new entries:


New Mark-Up definitions will be stored with the <Save> icon or when leaving the frame with a message box and clicking on "Yes".
Changes will be considered after a GenVas Cache Update. If a single product was not used in booking process before that means the cache was empty for that specific product then it will work without a GenVas Cache Update because the cache will be filled with actual data in this case.

PLEASE NOTE that all defined and matching mark-up rules will fire in addition. The system won't only consider the highest level and stop matching.


Agency Set-Up



The user can exclude an agency from mark-up calculation when activating checkbox "Kein Markup berechnen"




Package options



The flag "Verkaufspreise und Markup vom Buchungscode ignorieren" can be set to ignore all sales price cahrts and mark-ups for the specific booking code.

Archive


The system archives all markup entries after checking out and storing the definitions under a unique consecutive number (1,2,3 …). The current version is version 0.
The files additionally contain the timestamp plus the user of the change.
For technical analysis the user can

  1. either look directly into the database tables
  2. or compare the versions with the help of the stored procedure "COMPARE_MARKUP_ABSOLUTE_VERSIONS".


The affected database tables are:

The procedure compares the two via parameter requested versions based on XML.
The compare version is set to 0 (the current version) in case only one version parameter is passed.
Samples:
COMPARE_MARKUP_ABSOLUTE_VERSIONS 2 0
This command compares version 2 with the current version 0.
COMPARE_MARKUP_ABSOLUTE_VERSIONS 2
This command also compares version 2 with the current version 0.
COMPARE_MARKUP_ABSOLUTE_VERSIONS 2 3
This command compares version 2 with version 3.

The output is a technical view and represents the result of the XML comparison executed by the procedure.
The list contains the modified levels (correspond to database tables) and entries based on the affected XML nodes.
Sample
The user reduced the general markup from 11,- to 10,- and additionally increases the supplement for the travel duration of 3 days from 5,- to 6,-:

Procedure output

Line 1
Indicates a change of the third node MARKUP_ABSOLUTE_BASE (corresponds to the identically named database table). The XMLs are displayed in OldValue and NewValue.
Line 2
Indicates a change of the first sub node MARKUP_ABSOLUTE_DETAIL (corresponds to the identically named database table). The XMLs are displayed in OldValue and NewValue.
Line 3
Indicates that the entry RATE was changed from 11 to 10 within the first sub node MARKUP_ABSOLUTE_DETAIL (corresponds to the identically named database table).
Line 4
Indicates a change of the first sub node MARKUP_ABSOLUTE_DURATIONS (corresponds to the identically named database table). The XMLs are displayed in OldValue and NewValue.
Line 5
Indicates that the entry RATE was changed from 5 to 6 within the first sub node MARKUP_ABSOLUTE_DURATIONS (corresponds to the identically named database table).

Examples


Mark-up per bookingcode


Definition of an absolute mark-up for a specific bookingcode and date ranges.



The system calculates two mark-up price rows.
8 nights for date range 25.09.-03.10., in total 6*2*8 = 96
2 nights for date range 03.10.-05.10., in total 2*2*7 = 14

Mark-up per bookingcode and participant type



This set-up decreases the mark up for children by 2 in this date range.