Error
Error Code:
1314
SAP S/4HANA Error 1314: Invalid SQLScript Variable Name
Description
Error 1314, ERR_SQLSCRIPT_INVALID_VARIABLE_NAME, indicates that a variable name used in a SQLScript statement is either syntactically incorrect, uses a reserved keyword, or is not allowed in the current context. This error typically arises during the development, compilation, or execution of custom SQLScript procedures, functions, or views within SAP S/4HANA's underlying database.
Error Message
ERR_SQLSCRIPT_INVALID_VARIABLE_NAME
Known Causes
4 known causesUsing Reserved Keywords
Attempting to use a SQLScript or SQL keyword (e.g., SELECT, FROM, WHERE, IF) as a variable name, which is prohibited.
Invalid Characters or Syntax
The variable name contains special characters, spaces, or starts with a number, violating standard SQLScript naming conventions.
Duplicate Variable Declaration
Declaring a variable with the same name multiple times within the same scope, leading to a naming conflict.
Exceeding Name Length Limits
The provided variable name exceeds the maximum allowed character length for identifiers in SQLScript.
Solutions
3 solutions available1. Review and Correct Variable Names in SQLScript easy
Inspect the SQLScript code for any variables that violate naming conventions and correct them.
1
Identify the SQLScript object (e.g., stored procedure, function, CDS view) that is triggering the error. This can often be found in the application logs or error messages preceding the 1314 error.
2
Access the definition of the identified SQLScript object using SAP HANA Studio, SAP Business Application Studio, or the SAP HANA Cockpit.
3
Carefully examine all declared variables within the SQLScript. Variable names in SAP HANA SQLScript have specific naming rules:
4
Ensure variable names do not start with a number. They must begin with a letter or an underscore.
5
Verify that variable names do not contain special characters (e.g., !, @, #, $, %, ^, &, *, (, ), -, +, =, {, }, [, ], |, \, :, ;, ", ', <, >, ,, ., ?, /). Allowed characters are typically alphanumeric and underscore.
6
Check for excessively long variable names. While there are limits, extremely long names can sometimes lead to unexpected issues.
7
Ensure variable names are not reserved keywords in SAP HANA SQLScript. Examples of reserved keywords include SELECT, FROM, WHERE, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, TABLE, VIEW, PROCEDURE, FUNCTION, BEGIN, END, IF, ELSE, LOOP, FOR, WHILE, RETURN, NULL, TRUE, FALSE, AS, IS, LIKE, BETWEEN, IN, EXISTS, DISTINCT, GROUP, ORDER, UNION, EXCEPT, INTERSECT, etc.
8
Correct any variable names that violate these rules. For example, change `1st_variable` to `var_1st` or `my-variable` to `my_variable`.
DECLARE my_variable INT;
-- Incorrect: DECLARE 1st_variable INT;9
Reactivate or recompile the SQLScript object after making the corrections.
2. Validate Input Parameters in SQLScript medium
Ensure that any input parameters used as variables within the SQLScript adhere to naming conventions.
1
Identify the SQLScript object and specifically look for input parameters that are being used or assigned to internal variables.
2
Examine the definition of the SQLScript object, paying close attention to the parameter list.
3
Apply the same naming convention rules as for internal variables to these input parameters. Parameter names also cannot start with a number, contain special characters, or be reserved keywords.
4
If an input parameter violates the naming rules, rename it to a valid identifier. For instance, rename `in_param_1` to `in_param_01` or `in_param_one`.
CREATE PROCEDURE my_proc (IN in_param_01 INT)
LANGUAGE SQLSCRIPT
AS
BEGIN
-- Use in_param_01 internally
END;5
When calling this SQLScript object from other applications or procedures, ensure the caller is updated to use the new parameter name if it was changed.
6
Reactivate or recompile the SQLScript object.
3. Inspect and Correct Variable Declarations in CDS Views medium
If the error originates from a CDS view, verify the syntax of any variables or parameters defined within it.
1
Locate the specific CDS view definition that is causing the ERR_SQLSCRIPT_INVALID_VARIABLE_NAME error. This is usually identified by the application context or the error traceback.
2
Open the CDS view definition in SAP Business Application Studio or a compatible IDE.
3
Look for any declared variables or parameters within the CDS view's SQLScript or annotations that might be treated as variables by the underlying engine.
4
Apply the standard SQLScript variable naming rules: no leading numbers, no special characters (except underscore), and avoid reserved keywords.
5
Correct any invalid variable or parameter names. For example, if a parameter is named `_1st_value`, rename it to `_value_1st` or `value_01st`.
define view my_cds_view with parameters (
param_01 : Integer
) as select from my_table {
key id,
param_01 -- Using the valid parameter name
};
-- Incorrect example: define view my_cds_view with parameters (
-- 1st_param : Integer
-- ) as select from my_table {...};6
Redeploy or activate the CDS view.