How To Fix EZ587 - &1 spool IDs saved under ID &2

EZ587 - Overview

• Message type: E = Error

• Message class: EZ - Print workbench

• Message number: 587

• Message text: &1 spool IDs saved under ID &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message EZ587 - &1 spool IDs saved under ID &2 ?

  The SAP error message EZ587 indicates that spool requests have been saved under a specific ID. This message typically occurs when there are issues related to spool requests in the SAP system. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Spool Request Management: The error message EZ587 is often related to the management of spool requests in SAP. It indicates that the system has saved spool IDs for a particular job or process.
  Job Execution: This can happen when a background job is executed, and the spool requests generated during that job are saved under a specific identifier.
  System Configuration: There may be configuration issues in the spool administration settings or the output device settings.
  
  
  Solution:
  
  
  Check Spool Requests: 
  
  Go to transaction code SP01 to view the spool requests. You can check the status of the spool requests saved under the specified ID.
  Look for any errors or issues with the spool requests