How To Fix FZ582 - Items locked due to the check result in SAP GTS

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 582

• Message text: Items locked due to the check result in SAP GTS

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 FZ582 - Items locked due to the check result in SAP GTS ?

  The SAP error message FZ582 indicates that items are locked due to the check result in SAP Global Trade Services (GTS). This typically occurs when a compliance check (such as a screening against denied party lists, embargo checks, or other regulatory checks) has flagged certain items during the processing of a transaction, such as a sales order or shipment.
  Cause:
  
  
  Compliance Check Failure: The most common cause of this error is that one or more items in the transaction have failed a compliance check. This could be due to:
  
  The presence of a denied party in the transaction.
  The items being subject to export control regulations.
  The items being flagged for other compliance-related issues.
  
  
  
  System Configuration: Incorrect configuration of the compliance checks in SAP GTS can also lead to unnecessary locking of items.
  
  
  Incomplete Data: Missing or incorrect data in the master data (e.g., customer, vendor, material) can lead to compliance checks failing.
  
  
  Solution:
  
  
  Review Compliance Check Results: 
  
  Go to the GTS compliance management workbench and review the results of the compliance checks for the affected items. This will provide insights into why the items are locked.
  Check the specific reasons for the lock, such as which regulations or lists were triggered.
  
  
  
  Correct Data Issues: 
  
  If the issue is due to incorrect or incomplete data, update the relevant master data (e.g., customer or material data) to ensure compliance checks can be passed.
  
  
  
  Adjust Configuration: 
  
  If the compliance checks are too strict or incorrectly configured, work with your SAP GTS administrator to adjust the settings. This may involve modifying the rules for compliance checks or the lists against which checks are performed.
  
  
  
  Release the Lock: 
  
  Once the issues are resolved, you may need to manually release the lock on the items. This can typically be done through the GTS interface or by reprocessing the transaction.
  
  
  
  Consult Documentation: 
  
  Refer to SAP documentation or support notes related to error FZ582 for specific guidance and troubleshooting steps.
  
  
  
  Related Information:
  
  SAP GTS Documentation: Review the official SAP GTS documentation for detailed information on compliance checks and error handling.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to error FZ582.
  Training and Support: Consider training for users involved in compliance checks to ensure they understand how to interpret results and resolve issues effectively.
  
  By following these steps, you should be able to identify the cause of the FZ582 error and implement a solution to resolve it.