Differences

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

Link to this comparison view

Next revision
Previous revision
userdocs:travelwise:reporting:bsp:bsp_report [2014/06/03 03:44]
dokuwiki_sync created
userdocs:travelwise:reporting:bsp:bsp_report [2015/09/22 00:07] (current)
dokuwiki_sync
Line 42: Line 42:
   * Tickets are merged in case its number is the same, but different //'​TWDocType'//​. ​   * Tickets are merged in case its number is the same, but different //'​TWDocType'//​. ​
   * Totals of //PNR tickets// and //manual tickets// with the same number is summarized. For such records //'​Mixed'​ type ('​TWDocType'​)//​ is set, //issue date// and //PNR// are taken from PNR ticket, Order No, values are separated with comma.   * Totals of //PNR tickets// and //manual tickets// with the same number is summarized. For such records //'​Mixed'​ type ('​TWDocType'​)//​ is set, //issue date// and //PNR// are taken from PNR ticket, Order No, values are separated with comma.
 +  * It is possible that a ticket exists in Application (TW) database, but not invoiced. To see to which PNR or to which Order such tickets are related to: in //'​Exist in BSP only'//​ sheet check //'TW PNRs'//​ column where all PNR numbers (comma separated) related to the tickets are shown (only for non-locked PNRs). In '​Orders'​ column there are all Orders'​ numbers (comma separated) related to the ticket. Relation may be either via //​Order->​PNR->​Ticket//​ or via //​Order->​Offer/​Invoice->​InvoiceLine->​Ticket//​. In case there are no relations, the PNRs/Orders fields are blank.
 +
 +===== Multicurrency =====
 +It is allowed to import BSP files in currencies which differ from the host company default currency and to compare incoming foreign currency values with local currency values on related invoices.
 +
 +{{:​userdocs:​travelwise:​reporting:​bsp:​bsp_report_n.png?​nolink|}}
 +The column //'​Currency'//​ contains ISO currency code taken from the BSP file lines (can be located manually between //'​File name'//​ and //'​Locked'//​ columns, by default it is placed in the end of the grid) .
 +  * In case the file includes the data in different currencies then //'???'//​ is shown.
 +  * Whenever file is selected then //Diff// currency is changed to the BSP file's currency.
 +  * In case the BSP file contains data in different currencies then //Diff// currency is changed to //???// as well.
 +
 +When report data is processed there could be three main scenarios:
 +  - File's currency is matching HC currency. Report is run the same way as it used to be.
 +  - File's currency is not matching HC currency. Report is run comparing tickets fares with local sell values on related invoices where file currency is matching local sell currency. In case there is related invoice line, but the local currency value is missing then //TWNet=0// is set.
 +  - File contains values in different currencies. Report is run comparing tickets fares with local sell values on related invoices where file currency is matching local sell currency. In case there is related invoice line, but the local currency or issues in another currency are missing then //TWNet=0// is set.
 +
 +===== RULES =====
 +  * If ticket exists in TW and it is voided and it is not invoiced and there is matching cancelled (CANX) ticket in BSP exists then these tickets should not appear in the report.
 +  * If there is a ticket in TW linked to an Invoice/​creditnote then this ticket should be always compared against matching BSP ticket (no matter if they are voided/​cancelled or not).
 +  * In case there is ticket in TW linked to several invoices/​credit notes, but some of them are outside the period then such credit notes/​invoices which are outside the period should not ne calculated when making the report.