When a flowgraph is built (activated/deployed) in SAP HANA, the system generates different runtime objects based on its configuration. For a flowgraph designed for batch processing, a stored procedure is generated. This procedure can then be called to execute the data transformation logic. For flowgraphs designed for continuous, real-time data movement, a real-time task is generated. This task can be started and stopped to manage the ongoing data flow. A replication task is a specific and common implementation of a real-time task, created to handle near real-time data replication between a source and SAP HANA.

A. Batch Task: The runtime object generated for a batch-mode flowgraph is a stored procedure. "Batch Task" describes the execution type, not the generated database object itself.

C. Function: Flowgraphs are designed for data movement and transformation (ETL/ELT processes) and generate procedures or tasks, not scalar or table functions which are used for calculations within queries.

1. SAP HANA Smart Data Integration and SAP HANA Smart Data Quality Documentation:

Reference for Procedure and Real-time Task: In the section "Flowgraphs

" under "Executing Flowgraphs

" the documentation states: "When you activate a flowgraph

the system generates a stored procedure (for batch data flows) or a task (for real-time data flows)." This directly supports answers B and D.

Reference for Replication Task: The section "Creating a Replication Task" explains that these tasks are used for real-time data replication and can be based on a flowgraph definition. This supports answer E.

2. SAP HANA SQL and System Views Reference:

Reference for Procedure: The CREATE PROCEDURE statement documentation describes the object generated for batch flowgraphs. The generated procedure is located in the SYSDI schema and its name is derived from the flowgraph name.

Reference for Task: The CREATE TASK statement documentation details the runtime object created for real-time flowgraphs

which is managed using START TASK

SUSPEND TASK

and DROP TASK commands. This confirms the nature of the objects in answers D and E.