How To Fix /PF1/MSG_FH_GUI628 - Recall &1 has been deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_FH_GUI -

• Message number: 628

• Message text: Recall &1 has been deleted

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 /PF1/MSG_FH_GUI628 - Recall &1 has been deleted ?

  The SAP error message /PF1/MSG_FH_GUI628 Recall &1 has been deleted typically indicates that a recall request or a specific item (denoted by &1) has been deleted from the system. This can occur in various contexts, such as when dealing with document management, workflow processes, or specific applications within SAP.
  Cause:
  
  Deletion of Recall Request: The recall request or item may have been intentionally deleted by a user or through a process in the system.
  Data Integrity Issues: There may be issues with data integrity, where the system is unable to find the requested recall due to inconsistencies in the database.
  User Permissions: The user may not have the necessary permissions to view or access the recall request, leading to the perception that it has been deleted.
  System Configuration: There may be configuration settings or business rules that automatically delete certain recall requests after a specific period or under certain conditions.
  
  Solution:
  
  Verify Deletion: Check the system logs or the relevant transaction to confirm whether the recall request has indeed been deleted. This can often be done through transaction codes like SLG1 (Application Log) or by checking the relevant tables.
  Check User Permissions: Ensure that the user has the appropriate permissions to access the recall request. If not, adjust the user roles or permissions accordingly.
  Recreate the Recall Request: If the recall request was deleted and needs to be reinstated, you may need to recreate it manually, if possible.
  Consult with IT Support: If the issue persists or if you suspect a system error, consult with your IT support team or SAP Basis team to investigate further. They can check for any underlying issues in the system or database.
  Review Configuration Settings: If the deletion is part of a business process, review the configuration settings to understand the rules governing recall requests and make adjustments if necessary.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as SE11 (Data Dictionary), SE16 (Data Browser), or SM37 (Job Monitoring).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional context.
  Documentation: Review the documentation for the specific module or application you are working with to understand how recall requests are managed and any related processes.
  
  If you continue to experience issues or if the error message is impacting business operations, it may be beneficial to escalate the matter to SAP support for further assistance.