📋

Description

This error signifies that a variable used within an SQLScript exception handling block, such as `RAISE EXCEPTION` or `CATCH`, is not correctly defined or recognized as a condition variable. It typically occurs during the compilation or execution of SAP HANA stored procedures, functions, or anonymous blocks containing SQLScript logic, preventing proper custom exception management.

💬

Error Message

ERR_SQLSCRIPT_ID_EXCEPTION_TYPE

🔍

Known Causes

3 known causes

⚠️

Undefined Condition Variable

A variable intended for use as an SQLScript condition was not explicitly declared using `DECLARE <variable_name> CONDITION FOR <SQL_error_code>`.

⚠️

Incorrect Variable Type Usage

An ordinary variable or a variable not declared as a condition was used in a context where an SQLScript condition variable was expected (e.g., in `RAISE EXCEPTION` or `CATCH` statements).

⚠️

Typographical Error or Scope Mismatch

A typo in the condition variable's name or an issue with its scope prevents the SQLScript engine from correctly identifying it within the current code block.

🛠️

Solutions

3 solutions available

1. Validate and Correct SQLScript Variable Usage medium

Review the SQLScript code for incorrect variable declarations or usage that might be causing the error.

1

Identify the SQLScript object (e.g., stored procedure, function, or CDS view with procedural logic) that is triggering error 1293. This can often be found in the ST05 trace or ST22 dump.

2

Examine the declaration of variables within the SQLScript. Ensure that data types are correctly specified and that variables are declared before they are used.

DECLARE my_variable VARCHAR(100);
-- Incorrect example: USING an undeclared variable
my_variable := 'some_value';

-- Correct example: Declaring before use
my_variable VARCHAR(100);
my_variable := 'some_value';

3

Check for any typos or case sensitivity issues in variable names. SQLScript is generally case-sensitive for identifiers.

DECLARE my_VAR VARCHAR(50);
-- Incorrect: Referencing with different case
my_VAR := 'test';
my_var := 'test2';

4

Verify that no attempts are made to assign values to read-only variables or to variables declared with specific constraints (e.g., NOT NULL) without providing a valid value.

DECLARE my_count INTEGER NOT NULL DEFAULT 0;
-- Incorrect: Attempting to assign NULL
my_count := NULL;

-- Correct: Assigning a valid value
my_count := 5;

5

If the error occurs within a complex SQLScript, consider simplifying the logic or breaking it down into smaller, more manageable units to isolate the problematic variable.

2. Analyze and Re-declare CDS View with Procedural Logic medium

If the error originates from a CDS view that incorporates procedural logic, re-examine and potentially re-declare its structure.

1

Pinpoint the specific CDS view causing the error. This might be visible in the application logs or debug traces.

2

Open the CDS view definition in ADT (ABAP Development Tools).

3

If the CDS view contains any embedded SQLScript (e.g., within annotations or custom logic), carefully review the variable declarations and assignments within that script. Pay close attention to the `VAR` keyword and its usage.

define view MyCDSView as select from my_table {
  key field1,
  field2,
  @SQL_SCRIPT: 'BEGIN
    DECLARE my_temp_var INTEGER;
    my_temp_var := field2 * 2;
    RETURN my_temp_var;
  END.' as calculated_field
}

4

Ensure that all variables used within the embedded SQLScript are correctly declared with appropriate data types and that their scope is valid. Re-declare any variables that appear to have issues.

define view MyCDSView as select from my_table {
  key field1,
  field2,
  @SQL_SCRIPT: 'BEGIN
    DECLARE my_calculated_value INTEGER;
    my_calculated_value := field2 * 2;
    RETURN my_calculated_value;
  END.' as calculated_field
}

5

Redeploy the CDS view to apply the corrections.

3. Investigate and Recreate Database Procedures/Functions advanced

For errors in custom database procedures or functions, thoroughly check and recreate them to resolve variable issues.

1

Identify the specific database procedure or function that is failing. This can be determined from the ST22 dump or by analyzing the execution flow.

2

Access the procedure or function definition using a database client or transaction like SE38/SE80 (if ABAP managed) or a dedicated SQL client (if native HANA object).

3

Carefully review the `DECLARE` statements for all variables. Verify that their data types are compatible with the values they are intended to hold and that there are no naming conflicts or undeclared variables being used in assignments or comparisons.

CREATE PROCEDURE my_procedure(IN input_param VARCHAR(50))
LANGUAGE SQLSCRIPT
SQL SECURITY INVOKER
AS
BEGIN
  DECLARE processed_value VARCHAR(100);
  -- Check for correct assignment and usage
  processed_value := input_param || '_processed';
  -- Other logic...
END;

4

Pay close attention to input and output parameters of the procedure/function. Ensure they are correctly declared and that their types match the intended usage within the script.

CREATE FUNCTION my_function(in_val INTEGER) RETURNS INTEGER
LANGUAGE SQLSCRIPT
SQL SECURITY INVOKER
AS
BEGIN
  DECLARE result_val INTEGER;
  result_val := in_val * 10;
  RETURN result_val;
END;

5

If the issue is difficult to pinpoint, try commenting out sections of the procedure/function logic to isolate the problematic variable usage. Once identified, recreate the procedure or function with the corrected variable declarations and assignments.

🔗

Related Errors

5 related errors

SAP S/4HANA Error 1293: Invalid SQLScript Condition Variable