At midnight, a programmed task is executed, responsible for the construction of a data cube by means of the procedure PRC_AFLS_ORDER_STATISTICS which it must be validated that it exists in the database.
Reports in Aranda FIELD SERVICE AFLS are executed through stored procedures. These are constructed when invoked through Aranda’s FIELD SERVICE AFLS reporting module.
You can also put together reports from Aranda QUERY MANAGER AQM using the AFLS database as a source; It is advisable to check the periodicity of the execution and the tables involved (i.e. if they are high operation tables) to avoid blockages in operation.
The list of stored procedures that AFLS handles for the generation of reports and dashboard is as follows; You should always make sure that they are created in the database for the correct functioning of the application:
| PRC_AFLS_34001_REPORT_DATASET_COMPILANCE | PRC_AFLS_34011_REPORT_SURVEY_DATASET1 |
| PRC_AFLS_34001_REPORT_DATASET_ORDERS | PRC_AFLS_34011_REPORT_SURVEY_DATASET2 |
| PRC_AFLS_34001_REPORT_DATASET_ORDERS_STATE | PRC_AFLS_34011_REPORT_SURVEY_DATASET3 |
| PRC_AFLS_34002_REPORT_DATASET_ORDERS | PRC_AFLS_34011_REPORT_SURVEY_DATASET4 |
| PRC_AFLS_34002_REPORT_DATASET_ORDERS_BY_SPECIALIST | PRC_AFLS_34011_REPORT_SURVEY_DATASET5 |
| PRC_AFLS_34002_REPORT_DATASET_ORDERS_TIME_BY_SPECIALIST | PRC_AFLS_34011_REPORT_SURVEY_DATASET6 |
| PRC_AFLS_34003_REPORT_DATASET_ORDERS | PRC_AFLS_34011_REPORT_SURVEY_DATASET7 |
| PRC_AFLS_34003_REPORT_DATASET_ORDERS_BY_SERVICE | PRC_AFLS_34012_REPORT_SURVEY_DATASET1 |
| PRC_AFLS_34003_REPORT_ORDER_STATE | PRC_AFLS_34012_REPORT_SURVEY_DATASET2 |
| PRC_AFLS_34004_REPORT_DATASET_SERVICES | PRC_AFLS_34012_REPORT_SURVEY_DATASET3 |
| PRC_AFLS_34004_REPORT_TREND_BY_COMPILANCE | PRC_AFLS_34012_REPORT_SURVEY_DATASET4 |
| PRC_AFLS_34004_REPORT_TREND_BY_SOLUTION | PRC_AFLS_34012_REPORT_SURVEY_DATASET5 |
| PRC_AFLS_34004_REPORT_TREND_BY_STATUS | PRC_AFLS_34012_REPORT_SURVEY_DATASET6 |
| PRC_AFLS_34005_REPORT_SOLUTION_TIME | PRC_AFLS_34012_REPORT_SURVEY_DATASET7 |
| PRC_AFLS_34005_REPORT_WORKORDER_LIST | PRC_AFLS_34014_REPORT_INFO_LOCATIONS |
| PRC_AFLS_34006_REPORT_DATASET_COMPANIES | PRC_AFLS_34015_REPORT_INFO_SPECIALISTS |
| PRC_AFLS_34006_REPORT_DATASET_SERVICES | PRC_AFLS_34016_REPORT_INFO_PRODUCTS |
| PRC_AFLS_34006_REPORT_DATASET_TOTALS | PRC_AFLS_DASH_DEMAND_FOR_LABOR |
| PRC_AFLS_34006_REPORT_DATASET_WORKORDER_LIST | PRC_AFLS_DASH_STATUS |
| PRC_AFLS_34006_REPORT_DATASET_WORKORDER_PROM_COST | PRC_AFLS_DASH_SUMMARY_SPECIALISTS |
| PRC_AFLS_34006_REPORT_DATASET_WORKORDER_TOTAL_COST | PRC_AFLS_ORDER_COST |
| PRC_AFLS_34007_REPORT_GENERAL_INVENTORY | PRC_AFLS_ORDER_STATISTICS |
| PRC_AFLS_34007_REPORT_TOP_PRODUCT_FINAL_INVENTORY | PRC_AFLS_PROVIDERS_CALCULATE_SCORE |
| PRC_AFLS_34007_REPORT_TOP_PRODUCT_OUTPUTS | PRC_AFLS_REASSIGN_WO_SPECIALIST |
| PRC_AFLS_34008_REPORT_MOST_USED_LASTMONTH | PRC_AFLS_REPORT_DATASET_COMPANY |
| PRC_AFLS_34008_REPORT_SUMMARY_INVENTORY_BY_LOCATION | PRC_AFLS_REPORT_DATASET_LOCATION |
| PRC_AFLS_34008_REPORT_TOP5_LOWEST_STOCK | PRC_AFLS_REPORT_DATASET_PROVIDERS |
| PRC_AFLS_34009_REPORT_DATASET_SPECIALISTS | PRC_AFLS_REPORT_DATASET_SERVICE |
| PRC_AFLS_34009_REPORT_MOST_USED_LAST_MONTH | PRC_AFLS_REPORT_DATASET_SURVEY_NAME |
| PRC_AFLS_34009_REPORT_SUMMARY_INVENTORY_BY_LOCATION | PRC_AFLS_REPORT_DATASET_SURVEYS |
| PRC_AFLS_34009_REPORT_TOP5_LOWEST_STOCK | PRC_AFLS_TRANSFER_INFO_LOCATION_HISTORY |
| PRC_AFLS_34010_REPORT_TOP5_MOST_USED_PRODUCT | PRC_AFLS_WORFLOW_ACTION_CHRONOMETER |
| PRC_AFLS_34010_REPORT_USED_PRODUCT_BY_SERVICE | PRC_AFLS_WORFLOW_ACTION_COST |
⚐ Note: It is recommended to check the latency between the application server and the database server, check the network hops to get the data.