📋

Description

This error occurs in SAP S/4HANA when an SQLScript built-in function or procedure expects a direct attribute name as a parameter but receives a value that includes an alias. It typically indicates a syntax mismatch in how parameters are passed to SQLScript functions, preventing the operation from executing correctly.

💬

Error Message

Parameter must be an attribute name without an alias

🔍

Known Causes

3 known causes

⚠️

Alias Used in Direct Parameter

Passing a column or expression that has been aliased directly as a parameter to an SQLScript function or procedure that strictly requires the original, unaliased attribute name.

⚠️

Incorrect SQLScript Syntax

A syntactical error in the SQLScript code where an alias is mistakenly introduced or referenced for a parameter type that expects a raw attribute name, leading to a parsing failure.

⚠️

Implicit Alias Creation

Using an expression, subquery, or derived column that implicitly creates an alias, and then attempting to pass this aliased result as a parameter requiring an unaliased attribute name.

🛠️

Solutions

3 solutions available

1. Remove Parameter Aliases in SQLScript easy

Identify and remove any aliases used for parameters within your SAP S/4HANA SQLScript procedures or functions.

1

Locate the SQLScript object (e.g., stored procedure, table function) that is causing the error. This can typically be done by examining the application logs or the trace of the failing transaction.

2

Open the SQLScript object in the SAP HANA Development Tools (e.g., SAP Business Application Studio, Eclipse with ADT plugin).

3

Review the parameter declarations within the SQLScript. Look for instances where a parameter name is followed by an alias (e.g., `IN param_name AS param_alias`).

Example of incorrect syntax:
CREATE PROCEDURE MY_PROC (
  IN input_value AS my_input
) LANGUAGE SQLSCRIPT AS
BEGIN
  -- procedure logic
END;

4

Remove the alias. The parameter should be declared directly without an `AS` clause for its name.

Example of correct syntax:
CREATE PROCEDURE MY_PROC (
  IN input_value
) LANGUAGE SQLSCRIPT AS
BEGIN
  -- procedure logic
END;

5

Save and activate the modified SQLScript object.

6

Re-execute the operation that previously failed to confirm the error is resolved.

2. Verify Parameter Usage in Calling Statements medium

Ensure that when calling an SQLScript object, you are referencing parameters by their actual names, not by any aliases that might have been mistakenly defined.

1

Identify the calling statement or application code that invokes the problematic SQLScript object. This might be within another SQLScript, a CDS view, or application code making a direct SQL call.

2

Examine how parameters are passed to the SQLScript. If you are using named parameter passing, ensure the name used in the call matches the actual parameter name defined in the SQLScript, not an alias.

Example of incorrect parameter passing (if procedure has `IN input_value`):
CALL MY_PROC(my_input => 123);

3

Correct the parameter passing to use the direct parameter name.

Example of correct parameter passing:
CALL MY_PROC(input_value => 123);

4

If the call is within application code (e.g., ABAP, Java), ensure that the parameter binding uses the correct internal parameter name as defined in the SQLScript.

5

Deploy or re-run the application/code that makes the call and verify the error is resolved.

3. Review SQLScript Definitions in SAP HANA Studio/BAS medium

Perform a comprehensive review of all SQLScript objects in your S/4HANA system that are involved in the failing process, focusing on parameter definitions.

1

Use the SAP HANA Development Tools (e.g., SAP Business Application Studio, SAP HANA Studio) to navigate to the relevant package or schema where the SQLScript objects reside.

2

Systematically open each SQLScript object (procedures, functions, etc.) that might be related to the error.

3

For each object, carefully examine the `IN`, `OUT`, and `INOUT` parameter declarations. Pay close attention to any `AS` keywords following parameter names.

Example of common mistake:
CREATE FUNCTION calculate_sum (
  param1 INTEGER AS p1,
  param2 INTEGER AS p2
) RETURNS INTEGER
LANGUAGE SQLSCRIPT
AS
BEGIN
  RETURN :p1 + :p2;
END;

4

Remove any aliases associated with parameter names. The parameter declaration should simply be `[IN|OUT|INOUT] parameter_name data_type`.

Corrected example:
CREATE FUNCTION calculate_sum (
  param1 INTEGER,
  param2 INTEGER
) RETURNS INTEGER
LANGUAGE SQLSCRIPT
AS
BEGIN
  RETURN :param1 + :param2;
END;

5

Save and activate all modified SQLScript objects.

6

Test the functionality that triggered the error to ensure it now executes without the 1321 error.

🔗

Related Errors

5 related errors

SAP S/4HANA Error 1321: Invalid SQLScript Parameter Alias