📋

Description

This error indicates an attempt to define a SQLScript function as parallelizable while it contains `OUT` or `IN OUT` parameters. Parallelizable functions are designed to be stateless and cannot modify or return data through mutable parameters, as this conflicts with their concurrent execution model.

💬

Error Message

Parallelizable function cannot have OUT or IN OUT parameter

🔍

Known Causes

3 known causes

⚠️

Invalid Function Parameter Type

A SQLScript function intended for parallel execution was defined with `OUT` or `IN OUT` parameters, which are not permitted for stateless parallel functions.

⚠️

Parallel Function Misconception

Developers may not be aware that functions declared as `PARALLELIZABLE` in SAP HANA SQLScript cannot have parameters that modify external state.

⚠️

Code Migration Issues

Existing SQLScript functions from older versions or different contexts, not originally designed for parallel execution, were marked as `PARALLELIZABLE` without parameter review.

🛠️

Solutions

3 solutions available

1. Refactor Stored Procedure to Avoid OUT/IN OUT Parameters advanced

Modify the stored procedure to return data via a SELECT statement instead of OUT/IN OUT parameters.

1

Identify the stored procedure causing the error. This often requires debugging the calling ABAP code or checking the trace logs of the function module that is attempting to parallelize.

2

Analyze the stored procedure's logic. Determine which OUT or IN OUT parameters are critical for returning data to the calling program.

3

Rewrite the stored procedure. Instead of using OUT or IN OUT parameters, modify the procedure to return the required data through a standard SELECT statement. If the procedure needs to return multiple result sets, you can use multiple SELECT statements.

Example of refactoring:

-- Original procedure with OUT parameter:
CREATE PROCEDURE my_proc_out (IN p_input INT, OUT p_output VARCHAR(100))
BEGIN
  SELECT column_data INTO p_output FROM my_table WHERE id = p_input;
END;

-- Refactored procedure returning via SELECT:
CREATE PROCEDURE my_proc_select (IN p_input INT)
BEGIN
  SELECT column_data FROM my_table WHERE id = p_input;
END;

4

Update the calling ABAP program (or the function module that invokes the stored procedure) to retrieve the results from the SELECT statement instead of reading the OUT/IN OUT parameters. This might involve using `CALL FUNCTION` with appropriate importing and exporting parameters that capture the table results.

2. Disable Parallelization for the Specific Function Module medium

Prevent the function module from being executed in parallel if refactoring is not feasible.

1

Identify the function module that is attempting to call the problematic stored procedure and is configured for parallel execution.

2

Access the function module definition in SAP using transaction SE37.

3

Navigate to the 'Attributes' tab of the function module.

4

Locate the 'Processing Type' field. If it's set to 'Remote-Enabled Module' or another parallelizable type, change it to 'Normal Function Module'.

5

Save the changes. This will prevent the function module from being considered for parallel execution, thereby avoiding the error.

3. Utilize a Table Type for Output Parameters advanced

If the procedure must return multiple rows, define a table type in ABAP and use it for the output.

1

Identify the stored procedure and its OUT/IN OUT parameters that are intended to return multiple rows.

2

In ABAP, define a table type that matches the structure of the data to be returned. Use transaction SE11 for this.

Example ABAP Table Type:

Data Element: ZMY_OUTPUT_DATA
Structure:
  FIELD1 TYPE VARCHAR(50)
  FIELD2 TYPE INT

Table Type:
  TYPE: STANDARD TABLE OF ZMY_OUTPUT_DATA WITH DEFAULT KEY.

3

Modify the stored procedure. Instead of using OUT parameters for individual values, design it to return a dataset that can be mapped to the defined ABAP table type. This might still involve returning data via SELECT statements, but the ABAP caller will expect a table.

4

In the calling ABAP program, declare a variable of the defined table type. When calling the stored procedure (or the function module that wraps it), ensure that the results are populated into this table variable. This often involves using RFC-enabled function modules that can handle table parameters.

Example ABAP Call (conceptual):

DATA: lt_output_data TYPE STANDARD TABLE OF ZMY_OUTPUT_DATA.

CALL FUNCTION 'YOUR_RFC_ENABLED_FM'
  EXPORTING
    iv_input_param = lv_input
  IMPORTING
    et_output_data = lt_output_data.

" Process lt_output_data

🔗

Related Errors

5 related errors

SAP S/4HANA Error 1302: Parallel Function Parameter