Error
Error Code:
602
SAP S/4HANA Error 602: Read-Only Session Variable
Description
Error 602, `ERR_API_READONLY_SESSION_VARIABLE`, indicates an attempt to modify a session variable that is designated as read-only within the SAP S/4HANA environment. This typically occurs when an application, custom script, or API call tries to write data to a system-controlled or protected session parameter.
Error Message
Cannot set read-only session variable
Known Causes
3 known causesModification of System Variables
An application or user attempted to change the value of a session variable that is explicitly marked as read-only by the SAP S/4HANA system to maintain integrity.
Custom Code Conflict
Custom ABAP code, Fiori extensions, or external scripts are trying to write to a session variable that is not intended for user modification during runtime.
Improper API Usage
An API call or integration attempted to pass a value to a parameter that corresponds to a read-only session variable, violating system constraints.
Solutions
3 solutions available1. Identify and Correct Application Code Setting Read-Only Variables advanced
The most common cause is application code attempting to modify a session variable that is intended to be read-only. This requires debugging the application.
1
Identify the application or component that is triggering the error. This usually involves reviewing application logs or using SAP's debugging tools (e.g., transaction ST05 for SQL trace, ST22 for ABAP dumps) to pinpoint the exact code execution path leading to the error.
N/A2
Examine the application code for any attempts to set or modify session variables using commands like `SET SESSION` or similar database-specific commands. Pay close attention to variables that might be inherently read-only or protected by the database system.
Example of problematic SQL (hypothetical, actual syntax may vary):
sql
SET SESSION READ_ONLY_MODE = 1;
Or within ABAP:
abap
SET PARAMETER ID 'READ_ONLY_FLAG' FIELD 'X'.
3
Modify the application code to remove or conditionally execute the statements that attempt to set read-only session variables. If the variable is meant to be set, ensure it's not marked as read-only in the database schema or configuration.
N/A4
Test the application thoroughly after making code changes to ensure the error is resolved and no new issues are introduced.
N/A2. Review Database Configuration for Read-Only Settings medium
Certain database configurations or user roles might enforce read-only modes for specific session variables or the entire session.
1
Connect to the SAP HANA database using a privileged user (e.g., SYSTEM).
N/A2
Query system views to check for any active read-only settings or configurations that might be affecting session variables. The specific views depend on the SAP HANA version and configuration.
Example query to check for system-wide read-only settings (may vary):
sql
SELECT * FROM SYS.SESSION_SETTINGS WHERE PROPERTY_NAME LIKE '%READ_ONLY%';
Or query for user-specific privileges that might restrict modifications.3
If a read-only setting is identified that is unintentionally applied, consider adjusting the database configuration. This might involve altering system parameters or modifying user privileges. **Caution:** Modifying global database settings can have wide-ranging impacts. Proceed with extreme care and consult SAP documentation.
Example of altering a system parameter (hypothetical, actual parameter name and syntax will differ):
sql
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('session_settings.read_only_mode') = 'OFF' WITH RECONFIGURE;
4
Restart the relevant SAP HANA services (e.g., indexserver) if configuration changes require it. Test the application to confirm the error is resolved.
N/A3. Verify SAP System User Permissions and Roles medium
Incorrectly assigned roles or permissions for the SAP system user connecting to the database can lead to this error if they lack the necessary rights to modify session variables.
1
Identify the database user that the SAP S/4HANA system uses to connect to the SAP HANA database. This is typically configured in the SAP system's connection settings (e.g., in transaction SM59 for RFC destinations, or relevant connection parameters in application configuration).
N/A2
Connect to the SAP HANA database with a privileged user and check the granted roles and privileges for the identified SAP system user.
Example query to check user privileges:
sql
SELECT * FROM SYS.GRANTED_ROLES WHERE GRANTEE = '<SAP_SYSTEM_USER>';
SELECT * FROM SYS.GRANTED_PRIVILEGES WHERE GRANTEE = '<SAP_SYSTEM_USER>';
Replace `<SAP_SYSTEM_USER>` with the actual SAP system database username.3
Ensure the SAP system user has the necessary privileges to set session variables. This might involve granting specific system privileges or assigning roles that include these permissions. Consult SAP HANA security documentation for the exact privileges required.
Example of granting a privilege (hypothetical):
sql
GRANT SET ANY VARIABLE TO <SAP_SYSTEM_USER>;
4
If privileges were modified, restart the SAP application server instances or relevant services to ensure the changes are picked up. Test the SAP S/4HANA application.
N/A