Error
Error Code:
587
SAP S/4HANA Error 587: Invalid API Result Set
Description
Error 587, ERR_API_INV_RESULTSET, indicates that an API call within SAP S/4HANA failed to return a valid or expected data set. This often occurs when an application attempts to retrieve or process data, but the returned information is malformed, incomplete, or doesn't conform to the expected structure.
Error Message
ERR_API_INV_RESULTSET: Result set is currently invalid
Known Causes
4 known causesMalformed API Response
The API endpoint returned data that was not in the expected format or was corrupted during transmission, preventing proper parsing.
Underlying Data Inconsistency
The data being queried in the SAP S/4HANA system is inconsistent or corrupt, leading to an invalid result set when retrieved.
Incorrect API Parameters
The application or integration made an API call with invalid or missing parameters, causing the system to generate an empty or malformed result set.
Transient Network or System Issue
Temporary network problems, system overload, or a timeout prevented the API from fully processing the request and delivering a complete result set.
Solutions
3 solutions available1. Restarting the Affected SAP Application Server easy
A simple restart can often resolve transient issues with application server processes holding invalid result sets.
1
Identify the SAP application server instance that is experiencing the error. You can usually find this information in the SAP system logs (SM21) or by checking the status of your application servers in transaction SM51.
2
Log in to the operating system of the identified application server. You will need administrative privileges.
3
Gracefully stop the SAP instance. The command to do this depends on your operating system and SAP installation. For example, on Linux, you might use `stopsap` or `sapcontrol -nr <instance_number> -function Stop`.
stopsap
# or
sapcontrol -nr <instance_number> -function Stop4
Wait for the instance to completely shut down. Monitor the process list to ensure all SAP processes have terminated.
5
Start the SAP instance. Again, the command depends on your setup. For example, on Linux, you might use `startsap` or `sapcontrol -nr <instance_number> -function Start`.
startsap
# or
sapcontrol -nr <instance_number> -function Start6
Monitor the SAP system logs (SM21) and trace files to confirm the instance has started successfully and the error 587 is no longer occurring.
2. Refreshing the RFC Destination Cache medium
Invalid or stale RFC destination configurations can lead to issues with remote function calls, including invalid result sets.
1
Access transaction SM59 in your SAP S/4HANA system.
2
Navigate to the RFC destinations that are being used by the application or process that is generating the error. This might involve looking for TCP/IP connections or other types of destinations.
3
For each relevant RFC destination, select it and then click the 'Connection Test' button. This will force a re-evaluation of the destination's connectivity and configuration.
4
If the connection test fails or indicates an issue, review the RFC destination's configuration (e.g., target host, program ID, gateway host/service). Make any necessary corrections.
5
After testing and potentially correcting, try to re-run the operation that was causing the error 587.
3. Investigating and Correcting Underlying Data or Logic Issues advanced
This is a more thorough approach, addressing potential corruption or incorrect data that the API is trying to process.
1
Identify the specific API or function module that is returning the error 587. This can often be found by analyzing the SAP system logs (SM21), ST22 (dumps), or by debugging the application flow.
2
Examine the input parameters being passed to the API or function module. Are there any unexpected values, missing data, or data types that don't match the expected structure?
3
If the API is interacting with database tables, consider executing SQL queries directly against the relevant tables to check for data integrity issues. Look for duplicate entries, inconsistent states, or missing mandatory fields.
SELECT * FROM <table_name> WHERE <condition_indicating_potential_issue>;
-- Example: Checking for duplicate key entries
SELECT key_field, COUNT(*) FROM <table_name> GROUP BY key_field HAVING COUNT(*) > 1;4
Use SAP debugging tools (e.g., `/h` in the command field) to step through the execution of the API or function module. Observe the data flow and identify where the result set becomes invalid.
5
If inconsistencies are found in the database, plan and execute data correction steps. This might involve manual updates, running SAP correction programs, or engaging with the functional team to resolve master data issues.
6
If the issue is in the logic of the API or function module itself, consider creating a support message with SAP (OSS message) to report the bug or request a correction/enhancement.