# Analyzing the Corporate Business Intelligence Impact: A Case Study in the Financial Sector
## 3 Results  
The work steps in each stage of the \"three-stage transition process for reporting\" aimed at in the study are shown in Figure 13.  
When the reports obtained using the PL/SQL tool were examined, the following findings were obtained:  
* The report is pulled using the PL/SQL tool via the datamart. However, the flexibility to select a column other than the columns written in the code was not provided. * Since the report queries over the last 12 months, when data are to be pulled for older dates, it is necessary to raise a request for change to the business intelligence team each time for the code block that creates the datamart. * Since the reporting process is via the database, the output is taken from the PL/SQL panel and presented by transferring it to Excel. Here, new work was needed to bring it back to the presentation format in Excel. * Since the reporting tool is PL/SQL, only personnel with database authorization and usage authority could use it. This did not save the report from personal dependency. * During the report extraction via PL/SQL, end users experienced bottlenecks in two stages while waiting. The first is the report query running time, and the second is the waiting period while transferring it to Excel and making final adjustments. * Adding a graphic while getting the report from the panel screen on PL/SQL and the lack of visually satisfying reporting caused feedback from end users. * Using the PL/SQL database, the CRB Cheque Report was reached in 13.5 min. Figure 12: Query run summary. With integration into the business intelligence solution, the following findings were obtained:  
Figure 13: Work steps for the intended three-stage process. * Without entering into a coding complexity such as PL/SQL, the report could be easily provided by the relevant teams by simply dragging and dropping the columns to the relevant fields. * With the business intelligence solution, end users were able to change the report content in a short time by stretching it according to their needs. * With the business intelligence solution, it was observed that visual colorings and graphics were added to the report within the same interface. * With the business intelligence solution, the report could be recorded under a common record by authorizing the desired records, and its latest status could be presented to authorized persons. * It was observed that the report obtained with the business intelligence solution can be obtained in 90 s and is in a format that can be used in presentation without the need for any intermediate program. The time-cost graph Figure 14 clearly shows a comparison of reporting processes performed manually with those performed using PL/SQL and SAP BO. When the graph is examined, it is observed that each reporting tool shows significant differences in terms of weekly, monthly, and annual costs. In the manual reporting process, 240 min are spent weekly, 960 min monthly, and 11,520 min annually. This clearly shows that manual methods are inefficient, and reporting processes are carried out in a time-consuming manner. The high time cost of manual processes leads to a significant loss of productivity, especially in organizations working with large data sets. In the reporting process performed using PL/SQL, 13.31 min are spent weekly, 53.24 min monthly, and 638.88 min annually. This indicates a significant improvement compared to manual methods. PL/SQL makes the reporting process faster by automating database queries. However, a significant portion of time is still spent on manual interventions and database management. In the reporting process using SAP BO (Business Objects), 90 s are spent weekly, 6 min monthly, and 72 min annually. SAP BO minimizes manual interventions and significantly speeds up processes by providing automatic reporting and data analysis. This shows that SAP BO is the most effective solution, especially in terms of saving time.