KPI Report
Learn how to call KPI reports.
There are two different types of KPI reports.
- CP based view - For SalesRX
- FI based view - For SalesOTC User
Callable from
As a RX user (with the TE_LSI_RxSales configuration): The KPI Report is called via menu entry ID_NET_QUERIES_AND_STATISTICS -> TE_ID_NET_REPORT_KPI_CP.
As an OTC user (with the TE_LSI_OTCSALES configuration): The KPI Report is called via menu entry ID_NET_QUERIES_AND_STATISTICS -> TE_ID_NET_REPORT_KPI_FI.
In the TE_LSI configuration both menu actions are defined and set to “invisible”. In the particular user configuration one of the context menu is set to “visible”.
Background info
In contrast to the old KPI report in u7 there are some basic and important changes. The report is based on U007 records. KPI records are valid for a certain period and are responsible for classification of the CP record. Only valid (this mean that the current date is in the period of the KPI records) are used in the report. Furthermore the report only use MA records which have a “Start date” within the “Start date” and “End date” of the KPI record.
Data modell (XML Structure)
Javascript
This entry calls the javascript function u8.TeLSI.Reports.doKpiReport($) uses an action template (JavaScript) that calls the javascript file \web\web\scripts\te.lsi\lsireports.js.
Queries
TE_Report_WPR_Expenses
This query is responsible for the expenses data in the report.
TE_Report_WPR_HolidayCalendar
This query is responsible for the holiday and workday data in the report.
TE_Report_UserDependentInformation
This query is responsible for user data in the report.
UI Overview
KPI Report for Ron Referent (9101)
Totals View
| Index | Description |
|---|---|
| 1 |
This value shows the sum of all work days from currently logged in rep within the current year. Weekends and public holidays are not used in this calculation. Therefore in the example above there are only 206 workdays. It is necessary to add a calendar (ID/120) to the rep. |
| 2 |
This value shows the workdays where the user entered “Administration” in his/her occupation report. Only record for the actual year is used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation. |
| 3 |
This value shows the workdays where the user entered “Conference” in his/her occupation report. Only record for the actual year is used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation. |
| 4 |
This value shows the workdays where the user entered “Holiday” in his/her occupation report. Only record for the actual year is used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation. |
| 5 |
This value shows the workdays where the user entered “Meeting/Education” in his/her occupation report. Only record for the actual year is used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation. |
| 6 |
This value shows the workdays where the user entered “Others” in his/her occupation report. Only record for the actual year ise used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation. |
| 7 | This value shows the workdays where the user entered “Stick leave” in his/her occupation report. Only record for the actual year is used for calculation! |
| 8 |
This value shows the workdays where the user entered “Visits” in his/her occupation report. Only record for the actual year is used for calculation! Values are used from the occupation management from B2 records. One day is split into 4 parts. It doesn’t matter if the occupation approval status from B2 is approved or not. Each records is used for calculation |
Activity View
| Index | Description |
| 1 |
This value shows the total number of activities linked to a CP record (split by Classification – ABC field – of CP record) The report only use MA records which have a “Start date” within the “Start date” and “End date” of the KPI record. Note: Only if an activity is completed (manually or via Call Documentation
procces) it is used for calculation)
|
| 2 |
This value shows the total number of activities linked to a CP record where the flag “Samples” is true. This flag is set by the trigger “TE_MA_UPD_Samples available”. This trigger set the flag to true if at least one sample was added to the activity via the Call Documentation process. Note: Only if an activity is completed (manually or via Call Documentation
Process) is used for calculation)
|
| 3 | This value shows the total number of activities linked to a CP record where
the flag “Sample- Document” is true. This flag is set by the trigger
“TE_MA_UPD_Set Sample Document Flag” (This trigger is implemented in TE_SR
Template Main – LSI right in info area MA under triggers). This trigger set the
flag to true, if at least one document record was added to the MA record. If a
Document is added the field MA/38 is filled with “A-D1_StaNo-D1_SerNo” by the
trigger “TE_MA_UPD_Fill Sample Document Field”. (This trigger is implemented in
TE_SR Template Main – LSI right in info area D3 under triggers). Note: Only if an activity is completed (manually or via Call Documentation
procces) is used for calculation)
|
| 4 |
This value shows the total number of activities linked to a CP record where the flag “Product Detailing” is true. This flag is set by the trigger “TE_MA_UPD_Product Detailing available”. This trigger set the flag to true if at least one product detailing record was added to the activity via the Call Documentation process. Note: Only if an activity is completed (manually or via Call Documentation
Process) is used for calculation)
|
| 5 |
This value shows the total number of activities linked to a CP record where the flag “Product Detailing” is true. This flag is set by the trigger “TE_MA_UPD_Set Medical Request Flag” (This trigger is implemented in TE_SR Template Main – LSI right in info area KM under triggers). This trigger set the flag to true if at least one KM record was added to the activity via the Call Documentation process! Note: Only if an activity is completed (manually or via Call Documentation
Process) is used for calculation)
|
| 6 | This value shows the total number of activities linked to a CP record where the flag “Tandem activity” is true. This flag is set manually if a new MA record is created. |
| 7 | Classification from CP. |
| 8 | Total sum line |
Activities / Workday View
| Index | Description |
| 1 | Classification from CP. |
| 2 | This value shows the relation between completed activities and workdays from actual year. In the example above the rep has average 0,05 activities per workday. To bring this value to 1 or higher the rep needs at least equal amount of completed activities as workdays. |
| 3 |
Drilled down by Classification. |
Targeted Doctors View
XSLT
\web\web\data\reports\te.lsi\xslt\kpi_cp.xslt \web\web\data\reports\te.lsi\xslt\kpi_fi.xslt
The following other XSLT is referred for consistent formatting of output variables: \web\web\data\reports\te.lsi\xslt\TE_library.xslt.
The created html includes javascript code that refers the jquery library (../scripts/lib/jquery.min.js) and a utility javascript file (\web\web\scripts\te.lsi\utils.js).
In the XSLT, three info areas are expected in the XPath expressions: CD, PE and B2.
The new XSLT variable concept is used within this XSLT. The following variables have to be defined via WIN module in order to run this report properly and the proper texts have to be administrated in the – language dependent - description field:
TE_Reporttext_KPI.F5016
TE_Reporttext_KPI.F5017
TE_Reporttext_KPI.F5018
TE_Reporttext_KPI.F5019
TE_Reporttext_KPI.F5020
TE_Reporttext_KPI.F5021
TE_Reporttext_KPI.F5022
TE_Reporttext_KPI.F5023
TE_Reporttext_KPI.F5024
TE_Reporttext_KPI.F5025
TE_Reporttext_KPI.F5032
TE_Reporttext_KPI.F5033
TE_Reporttext_KPI.F5034
To open linked records, the utils.js javascript function openroot() is embedded. This function opens the default header for the given record and info area in a separate tab, if the function is called.
Order Summary
The new XSLT variable concept is used within this XSLT. The following variables have to be defined via WIN module in order to run this report properly and the proper texts have to be administrated in the – language dependent - description field:
TE_Reporttext_KPI.F5016
TE_Reporttext_KPI.F5017
TE_Reporttext_KPI.F5018
TE_Reporttext_KPI.F5019
TE_Reporttext_KPI.F5020
TE_Reporttext_KPI.F5021
Call Summary
Basically there is one big designer query which is used for createing the xml for the XSLT report.
TE_MA_CallSummary
The new XSLT variable concept is used within this XSLT. The following variables have to be defined via WIN module in order to run this report properly and the proper texts have to be administrated in the – language dependent - description field:
TE_Reporttext_KPI.F5016
TE_Reporttext_KPI.F5017