📋

Description

This error occurs in SAP S/4HANA's SQLScript environment when a parameter attribute is incorrectly referenced with a table or schema name prefix. It indicates that the attribute should be specified as a simple name without any qualification, typically within built-in functions or procedures.

💬

Error Message

Parameter must be an attribute name without a table name upfront

🔍

Known Causes

3 known causes

⚠️

Incorrect Attribute Qualification

The SQLScript parameter attribute is specified with an unnecessary table name or schema prefix (e.g., `SCHEMA.TABLE.ATTRIBUTE`), violating the required simple name format.

⚠️

Misunderstood SQLScript Syntax

Developers might misunderstand or misapply SQLScript syntax rules for parameter attributes in specific contexts, such as built-in functions or procedures.

⚠️

Unadapted Code Reuse

Reusing SQLScript code snippets from environments where fully qualified attribute names are permitted, without adjusting them for the current context's requirements.

🛠️

Solutions

3 solutions available

1. Correct SQLScript Parameter Declaration easy

Ensure SQLScript parameters are declared with only the attribute name, not prefixed with a table name.

1

Identify the SQLScript (e.g., stored procedure, function) causing error 1320.

2

Examine the parameter declarations within the SQLScript. Look for parameters that are prefixed with a table name, like `TABLE_NAME.ATTRIBUTE_NAME`.

3

Modify the parameter declaration to use only the attribute name. For example, change `TABLE_NAME.ATTRIBUTE_NAME` to `ATTRIBUTE_NAME`.

ALTER PROCEDURE MY_PROCEDURE ( IN ATTRIBUTE_NAME VARCHAR(100) ) AS ...

4

Reactivate or re-deploy the corrected SQLScript.

2. Review Table Type Declarations medium

Verify that table types used in SQLScript parameter declarations are correctly defined.

1

Locate the SQLScript that is throwing error 1320.

2

Check the data type of the parameters. If a table type is being used, ensure that the table type definition itself is correct and does not imply a table prefix for its attributes.

CREATE TYPE MY_TABLE_TYPE AS TABLE (
    ATTRIBUTE1 VARCHAR(50),
    ATTRIBUTE2 INTEGER
);

3

If the parameter is declared as a table type, the attributes within the SQLScript's body should be referenced without any table name prefix (e.g., `attribute1`, not `my_table_type.attribute1`). The error often arises when trying to treat a table type parameter as if it were a direct table reference within the parameter list itself.

4

Re-activate the SQLScript after ensuring the table type and its usage are consistent.

3. Analyze SQLScript Calling Context medium

Investigate how the SQLScript is being called and ensure the arguments match the corrected parameter definitions.

1

Identify the SQLScript that is failing.

2

Determine which program or process is calling this SQLScript.

3

After correcting the SQLScript's parameter declarations as per Solution 1, review the calling code. The arguments passed to the SQLScript must now correspond to the simplified attribute names.

CALL MY_PROCEDURE(attribute_value); -- Corrected call

4

If the calling code is part of an ABAP program, ensure that the corresponding ABAP data structures or variables passed as parameters are correctly mapped to the SQLScript's expected attribute names.

5

Re-run the calling program or process to confirm the error is resolved.

🔗

Related Errors

5 related errors

SAP S/4HANA Error 1320: Invalid SQLScript Parameter Attribute