Once your flow is configured and deployed, you can run it.
To run your flow, you can:
Click Run to start an immediate run.
Click Schedule to run at a regular specified time.
Add it to a task chain. For more information, see Creating a Task Chain .
Once completed, the Run Status section in the property panel is updated. From the Flows monitor, you can check details of your runs, and perform other actions on your flows. For more information, see Monitoring Flows .
Note
In the Data Integration Monitor , you can:
Cancel a running transformation flow. For more information, see Cancel a Transformation Flow Run .
Simulate a run that doesn't save changes in the target table by clicking Simulate Run . Simulating allows you to test a transformation flow and see if you get the desired outcome. Based on the result, you can decide to deploy the flow, resolve errors, or to optimize the flow to improve performances. For more information, see Explore Transformation Flows .
Download a PLV file of a visual map of the operators and their relationships and hierarchies by clicking Generate a SQL Analyzer Plan File. The plan file contains detailed information about your data model that you can download for further analysis. Analyzing this file allows you to resolve errors and enhance transformation flow performances. For more information, see Explore Transformation Flows .
Run your transformation flow in batches. A batch is a subset of data identified in an SAP HANA runtime transformation flow to optimize memory usage by processing data in manageable chunks. Each batch is defined based on a "batch column", selected in the View Transform, and a "batch size", specifying the number of distinct values from the batch column included in each batch. Loading data in batches is not supported in a File space.
If a source view or an underlying view of the source view has data access controls applied to it, then the transformation aborts with an error. For more information, see Securing Data with Data Access Controls
The runtime is different if you are running a transformation flow in an SAP HANA space or a transformation flow in a file space. Indeed, with file spaces, space administrators enable the object store to enhance storage capabilities, supporting business scenarios with the storage of large amounts of data at a lower cost.
A transformation flow that uses a local table (file) with Delta Capture enabled as a source may fail after 30 days. By default, the Delta Capture log becomes outdated after 30 days. Resetting the watermark is necessary to fully reload the logs and avoid any transformation flow run failures. See Watermarks .
A transformation flow run fails if it lasts for over 48 hours.
Create Schedule to Run Your Transformation Flow
You can also create a schedule to run your flow on a regular basis. Click Schedule and define your schedule. For more information, see Scheduling Data Integration Tasks .
Note
For optimal performance, it is recommended that you consider staggering the scheduled run time of tasks such as data flows or task chains that may contain these tasks. Make sure to distribute your work, such as scheduling and running tasks. There isn't a specific numerical limit on how many tasks can be scheduled. There could be a resource distribution issue caused by too many tasks running at once. Check your system monitor to look at your workload distribution. For more information, see Monitoring SAP Datasphere or Persisted Views and Memory Consumption .
Run Your Flow Using a Task Chain
You can run a flow using a task chain. For more information, see Creating a Task Chain .
Alternatively, you can also run your flows from the Data Integration Monitor .
From the Flows monitor, you can check details of your runs, and perform other actions on your flows. For more information, see Monitoring Flows .