Automated HANA Reports

This wiki documentation provides a step-by-step guide for scheduling and automating HANA SQL reports within IT-Conductor. It outlines the process for creating schedules, defining report templates, and assigning schedules to ensure that HANA reports run at specified times.

Pre-requisites

Before scheduling any reports, please make sure you've completed the following tasks below.

• Configure your HANA Systems for monitoring in IT-Conductor. See SAP HANA System Monitoring for more details

How to Schedule a HANA Report on IT-Conductor?

Create a Schedule

1. Visit service.itconductor.com and enter your login credentials.

2. In the main menu, navigate to Management → Automation → Schedules.

3. On the Schedules screen, click the button to create a new item.

Figure 1: List of Schedules in IT-Conductor

1. Fill out all the necessary information in the Create Process Schedule screen.

   1. Name - refers to the schedule name.

   2. Description - Enter a description for the schedule.

   3. Organization: refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it.

   4. Work Days - refers to the specific days of the week on which the schedule is active.

   5. Observe Holidays - if checked, it indicates whether the schedule should skip execution on defined holidays.

   6. Time Windows: Specific time ranges during which the schedule will be active. To add a time window, click on the Add New Row button and select a time to start and end.
   7. Formulae - refers to the frequency of the scheduling (e.g., daily, monthly). To add a frequency, click on the Add New Row button. This option allows you to be very specific about the frequency of the scheduling. You may specify the frequency by position (e.g., first day of the month, last day of the month, etc), day of the week, week (e.g., first week of the month, second week of the month, etc), month, or quarter.
   8. Instance Removal Age - defines how long completed report instances are retained before automatic deletion.

   9. Instance Owner - refers to the owner of the report instance when it is generated at the scheduled time.

   10. Context Mode - determines the method for applying context. The options are Single, Object Group, and Enumerate. In most cases, select Single; this will activate the following two options.

   11. Context Class - refers to the system or environment type relevant to the report (e.g., SAP system, HANA System, Windows System, etc.). For this purpose, we’ll select the HANA System.

   12. Context Object - select the system where the report will be scheduled to run

Figure 2a: Create a New Schedule

Figure 2b: Create a New Schedule

1. Once it’s completed, click on the button to save.

Create a Report Definition for the HANA system

1. On the main grid, navigate to the HANA system that you selected in the previous step and click on SQL Jobs.

Figure 3: SQL Jobs in HANA System

1. You may choose to create a report from a template by clicking on the Templates button or from zero by clicking on the button. In this case, we’ll create a new report template.

Figure 4: List of Existing SQL Jobs

1. To create a new template, click on the button and fill out all the necessary information in the New SQL Script Template screen.

   1. Name - refers to the name of the HANA SQL report.

   2. Description - refers to the description of the report.

   3. Database - refers to the target database where the SQL query will be executed. This will be substituted when the report is instantiated.

   4. Schedule - don’t assign the schedule yet.

   5. Planned Start Time - defines the intended time of day the report is set to begin execution (Optional if you’re already assigning a schedule to the report).

   6. Time Windows Begin - defines the start of the allowed time range for report execution (Optional if you’re already assigning a schedule to the report).

   7. Time Windows End - defines the end of the allowed time range for report execution (Optional if you’re already assigning a schedule to the report).

   8. Repeat - this option is not applicable in this scenario.

   9. Complete Monitoring - this enables the triggering of a recovery action using thresholds.

   10. Deliver Log - if checked, it sends execution logs to designated recipients.

       1. Deliver On - specifies the conditions under which the log should be sent. The options are: Any, Failure, and Success.

       2. Deliver Log To - refers to the primary recipient of the report execution log.

       3. Deliver CC - refers to an optional secondary email address to receive a copy of the log.

       4. Deliver Log As - defines how the log is delivered—either as an email attachment or inline in the message body.

       5. Delivery Message - refers to the subject line or message included in the log delivery email.

   11. SQL - refers to the core query logic written in SQL that retrieves report data.

   12. Echo - if checked, the option will print the SQL statement in the report output.

   13. Output Type - refers to the format of the report output (e.g., CSV, HTML, TEXT).

   14. Preserve Formatting - if checked, it maintains original layout/structure in the output file.

   15. Wrapped - if checked, it controls whether long lines in the output are wrapped or truncated.

   16. Query Timeout - refers to the maximum execution time allowed for the SQL query before it’s terminated. By default, it’s set to 180 seconds.

Figure 5a: Create new SQL Template

Figure 5b: Create new SQL Template

1. Click on the button to save, and you will be returned to the SQL Script Templates screen.
2. To assign a schedule to your new SQL report template, click the Schedule icon in the Tools column.

Figure 6: List of SQL Templates in IT-Conductor

1. Check the schedule you wish to add and click on the Save button.

Figure 7: Assign a Schedule to a Report

Related Information

• Scheduling Reports